4 ms·
I have some static sites I build with Nanoc. The source content is mostly HTML with a sprinkling of ERB. I could do all of it by hand, but using a SSG lets me
by jacques_chester 13y ago
I have some static sites I build with Nanoc. The source content is mostly HTML with a sprinkling of ERB.
I could do all of it by hand, but using a SSG lets me factor out a lot of repetitive scut work. For example, I have a function that takes a hash and builds the HTML for a collection of references. Doing it by hand would be time consuming and error-prone.
More obviously, when I update my page layouts, it happens across the whole site. I don't have to go around copying and pasting, again introducing more busy work with room for error.
"What about grep and sed?", I hear you ask. By the time I'm building ad hoc build pipelines each time I fiddle with the site, I once again introduce new opportunities for error. Why not just automate the whole pile of wax and be done with it?
- chris_mahan 13y agoAbout updates to the site layout, I've come to the realization that the site doesn't need to have a uniform look and feel for the whole site, or sections of the site. I came to the understanding that each page can do, can be, what it needs to be. Plain html5 (no css, no js) is enough for my needs, and each page is customized for its own purpose. I have a crumbs navigation at top, that may go away too. most people (99.9% i think) navigate forward, then use the back key in the browser to go back, so I may get rid of the crumbs someday. each page on the site is accessible from the whole internet. If Joe the poet links to a page on my site, essentially, my page becomes part of the web experience Joe is building. I want to show respect to Joe, and not suck in his readers into my own site. if people want to get to the root of my site, they already know how to edit the uri down to the domain name. (sorry for philisophizing! )