7 ms·

For ease of maintenance and portability I think markdown is really the king of formats for blog content. Are you writing the posts in HTML? Why are you intermit

For ease of maintenance and portability I think markdown is really the king of formats for blog content. Are you writing the posts in HTML? Why are you intermittently using for paragraphs and to wrap other elements?

Dionakra 6y ago
Yep, I am writing the posts in HTML. The reason to avoid Markdown (which I love) and other things is to avoid any kind of building tools. I tried to install Gatsby on a Windows machine and I had several errors. I wanted to remove any dependency on external software. I wanted it to be modifiable with just a text editor and nothing else. Regarding the use of is because the tag with the chosen CSS leaves too much space after <h*> tags, while doesn't, and as I wanted to just use HTML tags and not create my own version of the CSS, I found the easiest way to achieve that.
- muspimerol 6y ago
 I definitely understand the desire to avoid a build-time tool. Especially Gatsby is way harder than it should be to get up and running. But for me, portability and data integrity trumps ease-of-publishing. If you want to move your blog to a new system in 5 years, you'll have to migrate a bunch of HTML. If you had the posts in markdown, chances are it would be a plug-and-play with the new system. That's the reason I pointed out the usage - your source of truth for your data is HTML, but in this case it's already getting mixed up with design-related oddities. Not bashing your choice for your blog, I think it's reasonable. I just wonder if HTML is the most resilient way to store blog data. It's something I considered a lot when redoing my blog last year.
- d3nj4l 6y ago
 You can use Jekyll for a JS-less markdown to static site generator.
 - asaaki 6y ago
 Also zola, hugo, and other pretty light weight generators are quite okay. I'm using zola which runs nicely on Win/Mac/Linux. All you need to get started is some theme/template and your blog posts in Markdown. Then enrich it with whatever floats your boat.

Dionakra 6y ago

Yep, I am writing the posts in HTML. The reason to avoid Markdown (which I love) and other things is to avoid any kind of building tools. I tried to install Gatsby on a Windows machine and I had several errors. I wanted to remove any dependency on external software. I wanted it to be modifiable with just a text editor and nothing else. Regarding the use of is because the tag with the chosen CSS leaves too much space after <h*> tags, while doesn't, and as I wanted to just use HTML tags and not create my own version of the CSS, I found the easiest way to achieve that.

muspimerol 6y ago
I definitely understand the desire to avoid a build-time tool. Especially Gatsby is way harder than it should be to get up and running. But for me, portability and data integrity trumps ease-of-publishing. If you want to move your blog to a new system in 5 years, you'll have to migrate a bunch of HTML. If you had the posts in markdown, chances are it would be a plug-and-play with the new system. That's the reason I pointed out the usage - your source of truth for your data is HTML, but in this case it's already getting mixed up with design-related oddities. Not bashing your choice for your blog, I think it's reasonable. I just wonder if HTML is the most resilient way to store blog data. It's something I considered a lot when redoing my blog last year.
d3nj4l 6y ago
You can use Jekyll for a JS-less markdown to static site generator.
- asaaki 6y ago
  Also zola, hugo, and other pretty light weight generators are quite okay. I'm using zola which runs nicely on Win/Mac/Linux. All you need to get started is some theme/template and your blog posts in Markdown. Then enrich it with whatever floats your boat.