• Zarobi@aussie.zoneEnglish
    1·
    3 hours ago

    The process looks like this:

    1. Author your web content on your hard drive.
    2. Preview it in your web browser.
    3. When you’re happy with what you have, upload it to your web host. Repeat as often as you’d like.

    That was a lot of words to say “just use static HTML and assets”… There’s one huge glaring unfixable issue with static HTML though. There’s no templating at all. That might seem obvious or a good thing, but are you really going to copy paste the same <head>, <header><nav> and <footer> across 300 blog posts? Then what happens if you ever change layout? Are you going to modify 300 html files by hand? Hell naw.

    I often lament that there is no HTML <import> feature yet to solve this problem. IFrame is ok, but also kind of shit and it’s not the intended purpose at all. It’s pretty much the only missing feature keeping me from recommending static HTML.

    The answer is just use PHP as a build step. It’s a tiny bit more complicated, but not by much. It’s still extremely flexible, you can write it to do whatever you want since it’s your own build step, and you won’t be fighting it. But you also get the benefits of not dealing with the ramifications of copy pasting.