Don't Be Stupid

Dear Coders,
We are happy that you enjoy coding for ZetaBoards. We worked hard to improve the markup, integrate jQuery, and make the board easier to modify through sensible use of CSS and JavaScript. However, the keyword is not JavaScript; it is sensible.

We are happy that you are confident in your ability to code. So take it from us: if we trash your code, it probably isn't anything personal. But having let our ZetaBoards out into the world, we feel this vague sense of responsibility for their wellbeing. And well, let's face it--it's much too easy to create chaos with a poorly-made code. As such, we will trash a code if we deem it of poor quality or harmful to a board. This includes codes that use outdated or deprecated HTML. No font tags please!

Here's some tips for making good codes:

• Don't go overboard. We do not need a code that will modify your board so it serves you tea every morning. Before you create a code, ask yourself if people really need it taking up space in their board wrappers, possibly causing complications for their users, etc.
  
• Can you do it with CSS? If so, why are you using JavaScript? Some people turn it off, either for security reasons or accessibility issues. Obviously there are certain functions that only JavaScript can perform--and that's swell, really. If your code will perform one of those functions, then go code it. But if you are doing something that you could accomplish using only CSS, then it is probably better to use CSS.
  
• Please think of your audience. If you give a mouse a cookie, he will ask for a glass of milk. Creating a code is just the first step. Once you decide to release it to an unsuspecting public, they will expect you to give them fixes for bugs, support, etc. Remember that most users are not coders. Consider creating installation instructions that are as simple as possible, and be kind to those having trouble.

We don't mean to sound discouraging. This is just the warning note of caution. Code carefully, and you'll end up creating wonderful things.

Dear Users,
We are happy that you enjoy using codes for ZetaBoards. We worked hard to improve the markup, integrate jQuery, and make the board easier to modify through sensible use of CSS and JavaScript. However, the keyword is not JavaScript; it is sensible.

We are happy that you are confident in your ability to run the board. So take it from us: when we tell you to remove codes because they're causing problems, it probably isn't anything personal. Having let our ZetaBoards out into the world, we feel this vague sense of responsibility for their wellbeing--but we still don't offer support for codes. Yes, we might be able to see what's wrong and fix it, but that is not a guarantee. Sometimes, unless you can get the code creator or another knowledgeable coder to pinpoint the problem, you will have to part with your code.

Please be sensible when adding codes. Perhaps the code creates a super-awesome-omg-homestarrunner-effect that will awe your board members. On the other hand, perhaps it's really annoying, slows down your board, and makes it hard for members to use the board. Just because the code is in this section doesn't mean it is a good code, or it's useful. You need to use your own critical skills to determine if the code belongs on your board. If you're unsure, ask questions, read the feedback. Try it out, and if it doesn't work, or you don't like it, remove it.

We don't mean to sound discouraging. This is just the warning note of caution. Add codes carefully, and you'll end up with a happier, healthier board.