perfectmotherfuckingwebsite VS building_websites_for_beginners

>However, the expectations for a statically generated site have drastically gotten higher over the years. Readers want (rich) content served fast

No, readers just want content served fast. Nothing beyond simple markdown or static html with some images or video embeds inside.

>Writers want dead simple (but expressive) writing and publishing. They want control over how their writing looks.

Who are those "writers"? If you're making a "static site as a service" perhaps that's a concern.

If you're making your own static site, you can use the simplest Markdown or whatever else you prefer, writing it manually, with or without a generator. You could even use the Motherfucking Website standard (https://motherfuckingwebsite.com/) or the Better Motherfucking Website RFC (http://bettermotherfuckingwebsite.com/) or the Best Motherfucking Website recommendations (https://thebestmotherfucking.website/) or go fancy and use the cutting edge Perfect Motherfucking Website ones (https://perfectmotherfuckingwebsite.com/).

Well in that case you may want to see this then this

⁠https://perfectmotherfuckingwebsite.com/

This is the better version and this is the perfect version

Now that the contact form has been added, the HTML for our basic portfolio page is complete. If you run into any issues, or just want to see what my version looks like, you can get the page's source code on github.

Now that we know how to add hyperlinks to documents, and understand that that can only be the parents of certain elements, we can add the employer website hyperlinks to our table. As this is such a minor change, I will not show you what to do and will ask you to have a go at doing it yourselves. Remember that you can look at this chapter's source code if you get stuck.

Now that our page is starting to get a little longer, instead of showing the complete code for the page, I will just provide a link to the final index.html for this chapter.

If your page doesn't look right, or you think you've made a mistake somewhere, don't worry! As the examples get more complex, it will get increasingly easy to miss out a line when copying, or to accidentally paste it into the wrong place. Take a few minutes and see whether you can figure out what's gone wrong yourself and fix it. If you can't, or would just like to check against my own version you can find the original files I worked from in the book's source code. There are also files for all the other chapters there as well if you would like to study them. It's also possible I have made a mistake with one of the examples; if you do spot this please let me know at [email protected] so I can fix it.

I'm writing this book in the open, and all the source files used to create it can be found on github. If you spot a spelling mistake, typo, or gross technical inaccuracy and would like to correct it please feel free to open a pull request with a correction and admonishment appropriate to the level of my transgression.