Grow your CSS skills. Land your dream job.

#119: Let’s Answer Forum Posts! Vol. 2

In this screencast we live answer more forums posts with no planning whatsoever. I don't think we hit a homerun on any of the threads we look at, but that's the lesson. You don't have to have the answers to everything to be a useful forum member. Just a few thoughts and your related experience can be helpful in nudging the original person in the right direction.


  1. Thanks, Chris. I love this type of post and I hope you keep doing them.

    It’s also awesome that this was recorded just after my first forum post!

  2. Xunei
    Permalink to comment#

    Nice Screencast :)

  3. Greg
    Permalink to comment#

    This is a great series. I’m one of those people who spends too long composing forum posts, the starts over, then hits cancel. It’s very motivating to watch someone else write quick, useful posts.

    Perhaps the key is to keep it short and not try to address every aspect of the problem.

  4. Alex
    Permalink to comment#

    Hello, Chris.
    Thank you for your good works.
    Pls I sent you a message, but you are yet to reply.
    Pls kindly reply me, because I need your response.
    I am waiting.
    Thank u.

  5. skube
    Permalink to comment#

    Love the idea of this. Please keep doing them.

  6. Nitin
    Permalink to comment#

    You are the best.

Leave a Comment

Posting Code

Markdown is supported in the comment area, so you can write inline code in backticks like `this` or multiline blocks of code in in triple backtick fences like ```this```. You don't need to escape code in backticks, Markdown does that for you.

Sadly, it's kind of broken. WordPress only accepts a subset of HTML in comments, which makes sense, because certainly some HTML can't be allowed, like <script> tags. But this stripping happens before the comment is processed by Markdown (via Jetpack). It seems to me that would be reversed, because after Markdown processes code in backticks, it's escaped, thus safe. If you think you can fix this issue, get in touch!

If you need to make sure the code (typically HTML) you post absolutely posts correctly, escape it and put it within <pre><code> tags.

Current ye@r *

*May or may not contain any actual "CSS" or "Tricks".