[spurlock]

For a start, don't overthink this. There's a wealth of tools[1] you can use that have all the functionality you're looking for baked in. If you're concerned about copying others work, don't be. Everyone does it. Why re-invent the wheel? Just be careful copying things like images and copy, as you will have to be original there[2]. There's actually not much skill required for this stuff, and this is why basic coding skills should be taught in school, because there's little 'grit' to this. Make something bold, do this: <strong>bold</strong>. Not so hard. The hard part is doing this at scale and this is why you need to simply accept that coding sites is a lot of repetition.

So to answer your question - I started by calmly accepting that as a developer, I would be typing out a lot of the same bits of code over and over, often creating <table> soup in the early days, and have since moved onto <div> soup and then styling accordingly with CSS. Sadly there is this trend of designing sites in reverse and people doing all the CSS and JavaScript first, and only when they're ready they start adding actual content.

[1]: https://adventurega.me/bootstrap/

[2]: http://bettermotherfuckingwebsite.com

[fanpuns]

Both bettermotherfuckingwebsite and motherfuckingwebsite have seriously brightened my day, thank you for that :)

>>Sadly there is this trend of designing sites in reverse and people doing all the CSS and JavaScript first, and only when they're ready they start adding actual content.

So, I find this to be really true. Maybe because it's easier to present a code solution to a design problem than it is to present a design solution to an extrinsic problem? But, this is exactly the problem I want to solve. I want to watch a screen cast of a designer solving a design problem the same way I can watch a screen cast of Ryan Bates solving a Rails problem.