jlem / webdevchallenge Goto Github PK

What do you guys think about adding in some solutions or maybe tutorials to the tasks listed here. It may be beneficial to provide people with assistance if they're stuck with anything.

I understand there is never a 'right way' to do something, but it may be beneficial to add something in the way of possible solutions?

Maybe switch out the list items for checkboxes so that when people fork it they can tick the tutorials they've completed?

What do you think about creating separate documents for front end vs. back end challenges?

I think it would make it easier for users interested in either to quickly filter out challenges they don't want to do.

It would also allow inclusion of global best-practices; for example, making sure front end code validates. http://w3c.github.io/developers/tools/#tools

Challenges should have a very specific, measurable target that can be aimed for. While the challenge shouldn't impose a technology per-se (unless it's entire purpose is to challenge someone to do something in a specific technology), it should at least have some some boundaries/specifications.

Example:

• "Try a preprocessor like LESS, SASS or Stylus." might be converted to "Replicate the CSS of Digg.com by using Sass, Less, and Stylus". This gives you an exact target to aim for, and three specific tasks. Even then, it's easy to write pure CSS, in Sass, so an even more specific challenge that requires the use of Sass/Less/Stylus features would be better.

Many of the ones I initially added also need some more specific target context.

Not sure if it makes sense to discuss each one in its own issue, or just talk about them here.