1. Trying to resist the temptation to use ☺ for unordered list items.

    Thankfully, CSS doesn’t seem to have the concept of list-style-character.

  2. So, after a week of naked HTML, I have applied a basic CSS normaliser and a few little gimmicks of my own.

    I am not (yet) using LESS or SASS or any such thing, but I have started to split my CSS into separate files and load them all together at using Assetic. This small change has immediately made a difference to how I structure and author CSS.

  3. Paul Boag: I have a guest post coming up that includes a table. Spent all evening trying different approaches to getting them working responsively.

    @boagworld they’re damned awkward. I am tempted to wrap them in a div with overflow-x: scroll.

  4. Essentially, my previous design had reached local maximum, so I’m going back to basics.

    I’ve decided it’s important that styling doesn’t fight or contradict markup, so I’m hoping that adding it progressively only where it is needed will make my code more maintainable.

  5. As of today I renounce twitter bootstrap. I will take inspiration from it as I take inspiration from other work, but I will no longer use any of it’s code.

  6. Haven’t heard that one before :

    The site is set to be viewed at 1024x768 minimum resolution. Please press your 'F11' key now if you are using a lesser resolution. Thank you

  7. Designing a poster in HTML (for compatibility). It’s relaxing to not have to deal with fluid design. body { width: 210mm; height: 297mm; }

  8. I am hugely annoyed at @twitter’s API stupidity, but almost as annoyed by their failure to provide a consistent tweet authoring experience across their platform.

    If I see “remaining chars = 0”, I expect the tweet to post, not give me some near-meaningless error message. I also expect URLs to be automatically detected and compensated for consistently across the platform. This is just crap .