I'd love to have a tool to generate a catalogue, a simple journal, etc.
I'd love to have a tool to generate a catalogue, a simple journal, etc.
The landing page explains the benefits quite well. Also, it has good examples of Lektor being used for a catalogue: https://www.getlektor.com/showcase/architekten-ronacher/ (direct link to the interactive version http://www.architekten-ronacher.at/projects/)
With this setup you can have anything (ANYTHING!) powering the data side. From CSVs to any SQL server local or remote, directories of markdown files, directories of ZIP archives, random (or deterministic) numbers or generable sequences.
Flask gives you so much freedom with the backend implementation you can draw from anywhere. You just need to define the URL patterns and supply the functions that respond with HTML. Flask-Freeze then crawls your site (or a list of pages you specify) and renders the HTML with whatever function you supplied. Couldn't be easier to understand and it is unbelievably flexible.
For sites which are closer to books, gitbook is an option as well. https://www.gitbook.com/
However, if your data is coming from an API/database something like Gatsby (https://www.gatsbyjs.org) would be better.
Here are themes tagged Portfolio: https://themes.gohugo.io/tags/portfolio/
I actually find many themes that are non-blog based in there.
Again, YMMW.
[1]: https://themes.gohugo.io/theme/docdock/content-organisation/
github.com/tmzt/isymtope
Working on a major push/update.
Essentially it's "static" in the sense that it could be used to generate a fully rendered page that is also an interactive (javascript) application.
It can also process actions on the server and generate a new HTML page in response to that that will be hydrated in the client.
It's an attempt to give you the best-of-both-worlds with a SPA, but one that arrives fully-rendered so there are no delays loading content. It's an SSR approach but without using a javascript engine or framework on the server, the server-side component is completely developed in Rust.
As far as "static app", I would say it's closer to something like Disqus being used on a static doc site or Firebase used for storage when github pages are used to host a site. It means it doesn't rely on server-side rendering to function as a PHP or ASP.net site does, but it can use it if available.
Would you please describe the data model you have in mind a bit more?