3 ms·
For a simple blog the hard parts are: * having something to blog about * having/arranging time to write and (if needed) edit If you have a CI/CD pipeline of
by dspillett 4y ago
For a simple blog the hard parts are:
* having something to blog about
* having/arranging time to write and (if needed) edit
If you have a CI/CD pipeline of any complexity at all for a blog, then either you are sharing infrastructure with other projects¹ or you are overcomplicating things!²
--
[1] perhaps your blog is largely related to dev so shares your dev/documentation resources
[2] no judgement: I'm capable of overcomplicating everything!
- revskill 4y agoOK, think about one use case. What if you want introduce some diagramming or Latex rendering in your blog ? In this case, if your original tooling doesn't support, you need to re-invent somehow .
- idontpost 4y ago[dead]
- dspillett 4y ago> What if you want introduce some diagramming or Latex rendering in your blog ? Then you are starting to step beyond what I was referring to as “a simple blog” (text, formatting, maybe some pictures or SVG). Though there are options that don't require a CI/CD pipeline. Depending on what Latext you need MathJax may do the trick (just include the JS in your standard page header, and drop the Latex code straight in inline where needed as per their standard example: https://jsbin.com/?html,output https://jsbin.com/?html,output. There are similar charting options like mermaid too. I don't know of inline charting options off the top of my head but I expect several exist.
- revskill 4y agoI see. My point is, the "hard" part, is mostly master your tooling right ? Because you want simplicity in customizing your output .
- WolfOliver 4y agohave a look at https://www.monsterwriter.app/ https://www.monsterwriter.app/ ... it is build for complex content (citations, cross refences, captions, inline and block equations, ...) and it supports publishing to ghost.