A few months ago I tried my hand at this because it had some better defaults. Also, I didn't like camel case variables everywhere in Hugo. Then, I gave up when I realised that Zola does not even allow YAML config files. Nit picks everywhere..
Zola: A fast static site generator in a single binary
91–100 of 177 posts
Re: Zola: A fast static site generator in a single binary
#92What is stopping someone writing an offline GUI for a static site generator? I think that would help a bit with non-technical adoption.
Nothing is actively stopping it. In fact a lot of people would strongly appreciate it, maybe even contribute. I would really love to see something like that: - local-first CMS with a strong emphasis on folders/files - multiple DVCS integrations (git, mercurial, pijul) with commit signatures (PGP) - support for forge APIs and email-based workflow to simplify the cooperative PR/MR/patch process - strong translations su…
I think it would be cool if it had all that stuff, but also hid the complexity from the users. i.e. wizards to talk them through using an external host via SFTP, or github pages, or wherever.
Re: Zola: A fast static site generator in a single binary
#93Earlier quoted context omitted.
I think I’m just going to write a HTTP server for my website in Go, download the entire website with wget and host that statically. At least that way I can have any feature I want.
Why not varnish then?
Simply because a lot easier to host static files than it is to host a web server binary that has to be executed. I can just upload to GitHub Pages or AWS S3 and let them worry about the HTTP caching, TLS certs, upgrade to HTTP/3, etc.
Re: Zola: A fast static site generator in a single binary
#94I though this was about the wedding registry site at first. Anyway, I liked this line from the Github: > Hugo gets ehh for the template engine because while it is probably the most powerful template engine in the list (after Jinja2) it personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased. This seems to be the life cycle of static site generat…
If you really want to focus on writing, why don't you just use WordPress? My feeling is that SSG is a toy to play with.
I had a SSG blog before. After stop using it for half year and came back, I found I had to relearn the whole thing to be able to make it work again. Add any function is a PITA. Totally wasting of time.
Re: Zola: A fast static site generator in a single binary
#95I run a few (well, one published, one in the works, a couple one-offs for student showcases) websites built with Zola. It's a great, little, simple piece of software. What I like: * Already supports the tooling I enjoy → SCSS out of the box, django/jade-like template engine (Terra, its sister project), markdown w/ TOML frontmatter * Fast → build times are almost instant, dev server builds to memory and does live-relo…
> a way to build from an API endpoint instead of markdown Sounds like remote content[0] might work for that? 0: https://www.getzola.org/documentation/templates/overview/#re...
Yeah, that’s the start. And I think what I’m after is eventually on the way. I’m not sure this would quite work the way I’d like; I guess variables could be passed into the template based on path and it could request different remote content based on that— I’d prefer to be able to use remote resources just like markdown instead of a different workflow.
Again, maybe I haven’t thought about this enough yet.
Re: Zola: A fast static site generator in a single binary
#96I though this was about the wedding registry site at first. Anyway, I liked this line from the Github: > Hugo gets ehh for the template engine because while it is probably the most powerful template engine in the list (after Jinja2) it personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased. This seems to be the life cycle of static site generat…
> I though this was about the wedding registry site at first.
I didn't even know what a wedding registry was until after the rename. It is named after https://fr.wikipedia.org/wiki/%C3%89mile_Zola
> I did this exact thing when I got frustrated with Hugo. I made my own custom SSG in order to create my blog. > The other thing that tends to happen with SSGs is that it can be a lot more fun to play around with the tech than actually writing blog posts!
Exactly that. A great way to learn a language too.
Re: Zola: A fast static site generator in a single binary
#97What is stopping someone writing an offline GUI for a static site generator? I think that would help a bit with non-technical adoption.
https://getpublii.com/, though it would be nicer if it were built on one of the more popular static site generators instead of reinventing that wheel.
Re: Zola: A fast static site generator in a single binary
#98I though this was about the wedding registry site at first. Anyway, I liked this line from the Github: > Hugo gets ehh for the template engine because while it is probably the most powerful template engine in the list (after Jinja2) it personally drives me insane, to the point of writing my own template engine and static site generator. Yes, this is a bit biased. This seems to be the life cycle of static site generat…
Personally, all I want is a full proper programming language in my templating. Every templating language ends up being irritatingly limited, for me at least.
Python has had mako for a long time, which does this.
Re: Zola: A fast static site generator in a single binary
#99My input as a former technologist turned marketing guy over the years - where is a decent SSG (perhaps like Zola) with page building drag and drop tools like a Wix or a Squarespace?
I'd love to move our site off of Wix - and have full control when needed and work offline before publishing pages - but inevitably you dive back into code or the guts of database queries once you leave these WYSIWYG tools.
Between Wix and Zola is an opportunity, in my opinion.
Re: Zola: A fast static site generator in a single binary
#100Earlier quoted context omitted.
I guess Racket’s proposal of language oriented programming isn’t so kooky after all.
Pollen, written in Racket, is arguably a "dsl for specifying ssgs" https://docs.racket-lang.org/pollen/
Pollen seems so incredibly cool and powerful, but every time I have tried to play around with it, I get distracted by small quirks and areas that I wish were documented more clearly, or in a more organized format.
My daydream is to make a _good_ technical documentation system with it that is usable by the everyman, but it's still just a bit too much of a stretch. Markdown + pandoc + LaTeX templates get close, but LaTeX templating is a nightmare, and markdown is far too limiting and lacks expressivity (without ad-hoc DSL's slapped on top).
If anyone has a good pollen tutorial or example repo, I'd _love_ to know of it.