3 ms·

I use Markdown and HTML, CSS, and Python (just stdlib, no packages) to generate static files. I think that will last just about the same length of time. http:

by chubot 6y ago

I use Markdown and HTML, CSS, and Python (just stdlib, no packages) to generate static files. I think that will last just about the same length of time. http://www.oilshell.org/blog/ http://www.oilshell.org/blog/ Markdown is a significant win, and CommonMark made it a lot better. CommonMark is a Useful, High-Quality Project http://www.oilshell.org/blog/2018/02/14.html http://www.oilshell.org/blog/2018/02/14.html Admittedly I need a Makefile, and Make is pretty impoverished for this use, and I want to replace it with something else. Shell isn't quite good enough because I don't want to rebuild the entire site on every edit, and I don't want to remember which files to rebuild. http://www.oilshell.org/site.html http://www.oilshell.org/site.html

kkoncevicius 6y ago
I use something very similar on my website, except with a few twists - MultiMarkdown (instead of Markdown) for HTML, Perl for piping MultiMarkdown produced HTMLs through some regex changes, and redo instead of Make for rebuilds. If you are looking for Make replacement - I cannot sing enough praises for redo: https://github.com/apenwarr/redo https://github.com/apenwarr/redo
- chubot 6y ago
  I've seen redo (and talked with apenwarr about it) although I think my brain is still stuck on static/declared dependencies. That doesn't apply to every problem but it definitely applies to a blog. Is your build parallel? That's one of my main requirements. I'd be interested in seeing the redo files if they're public.
  - kkoncevicius 6y ago
    I made the files public temporarily: https://github.com/karoliskoncevicius/website https://github.com/karoliskoncevicius/website My website is probably a lot simpler than yours. All the "do" files are at the root level. But I have to state that there is no "redo" syntax really. You just take the scripts that do things and save them to files with a "do" extension.

by chubot 6y ago

kkoncevicius 6y ago

I use something very similar on my website, except with a few twists - MultiMarkdown (instead of Markdown) for HTML, Perl for piping MultiMarkdown produced HTMLs through some regex changes, and redo instead of Make for rebuilds. If you are looking for Make replacement - I cannot sing enough praises for redo: https://github.com/apenwarr/redo https://github.com/apenwarr/redo

chubot 6y ago
I've seen redo (and talked with apenwarr about it) although I think my brain is still stuck on static/declared dependencies. That doesn't apply to every problem but it definitely applies to a blog. Is your build parallel? That's one of my main requirements. I'd be interested in seeing the redo files if they're public.
- kkoncevicius 6y ago
  I made the files public temporarily: https://github.com/karoliskoncevicius/website https://github.com/karoliskoncevicius/website My website is probably a lot simpler than yours. All the "do" files are at the root level. But I have to state that there is no "redo" syntax really. You just take the scripts that do things and save them to files with a "do" extension.