[SOLVED] Slackware in Business

upnort · 07-24-2017, 10:46 PM

I long have liked the concept of focusing on document structure and letting a backend processor handle final format. Just not a user friendly process for most people.

Quote:

If the tools you use fit your hands well, there's no reason for me to try to snatch those tools out of your hands.

For the moment, yes. I have been around computers long enough to know that what I want today might not be what I want or need three years from now.

a4z · 07-25-2017, 03:08 AM

Quote:

Originally Posted by upnort

I'm not. Wordpress works great for millions of people. Just not me.

Before traveling my current path with my blog, I evaluated and tested several static site generators and blog engines. All of them depend upon some kind of markdown/markup language.

Then these generators use complex perl and python wizardry to convert the markdown/markup to...

[drum roll]

HTML.

Wikis suffer the same design challenge. All kinds of energy expended to help people avoid HTML. Then all kinds of energy expended to convert the file to HTML.

My custom script is somewhat similar to all of these backend engines, but I do not have to convert from an obtuse markup language into the common markup language of HTML.

I figured writing directly in HTML in the first place was more efficient and simpler.

I use a template to insert the header portion of each page I create. Nothing fancy.

for - not just technical - writers, HTML is the obtuse markup language
markdown and asciidoctor can eve be used to write books,
in developer jobs, but I see them also for writing techical documentations since some time, they are quasi standard.
for me, asciidoctor is best