On: Ask HN: What problem are you close to solving and ...

[cxr]

> (sh), and obviously HTML, CSS, Js

Cut out the sh dependency and just use the "obvious" tech; make the site capable of generating itself, without reliance on any other tools.

[adriangrigore → cxr]

What do you suggest for templating?

[cxr → adriangrigore]

ES6 backtick strings.

[adriangrigore → cxr]

I believe you misunderstand, I'd rather distance myself from the NodeJs ecosystem and use standard UNIX tools for developing web sites. I believe sh is great as a templating language.

[cxr → adriangrigore]

I didn't say anything about NodeJS. (In fact, that would be adding a different dependency, not reducing the count by one.)

[adriangrigore → cxr]

So how would you interpret the ES6 backtick strings?

[cxr → adriangrigore]

The "obvious" way. (The same runtime that you're planning to use for the JS you mentioned in your original comment. <https://news.ycombinator.com/item?id=28349504>)

[adriangrigore → cxr]

And do the generation on the client side?

[cxr → adriangrigore]

If by "client side" you mean in the web browser of you, the author of a new piece of content, then yes—a site that is "capable of generating itself". (If you mean templates that are evaluated in the browser of every site visitor every time they refresh the page, then no.)

[adriangrigore → cxr]

Ah, yeah, finally got your "capable of generating itself" idea. Pretty cool, interesting to experiment on it. I guess it would be something like a site that downloads itself also.

[adriangrigore → adriangrigore]

But then you would have a Js dependency.