You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry if this is not a proper place but there is no type of contact anywhere listed on the wiki or in the README
I have a plan for static website that needs custom build steps. Statik seems good for such thing because ORM-style data and assets would make it very easy to manipulate (great design IMO, havent found any generator with similar thing). However, I don't see any way of embedding custom build steps in the process besides jinja2 tags and linked Python code that would do the work. This arises few questions for me
Is there a way to call/reference custom build steps from Markdown (or other data) files? I would like to embed some additional data into final content (eg LaTeX, specific dynamically pre-rendered HTML content) - the best thing would be some custom tags that I can put in Markdown files that will call external tools to preprocess it. Jinja2 templates do not seem to be viable for this as I would need a separate template for each post.
Is it possible to have advanced, multiple, independent paginations? Something like a website that contains multiple different "books" where each has own pagination and page numbers and each article/chapter in each book has a link to next/prev
The text was updated successfully, but these errors were encountered:
Sorry if this is not a proper place but there is no type of contact anywhere listed on the wiki or in the README
I have a plan for static website that needs custom build steps. Statik seems good for such thing because ORM-style data and assets would make it very easy to manipulate (great design IMO, havent found any generator with similar thing). However, I don't see any way of embedding custom build steps in the process besides jinja2 tags and linked Python code that would do the work. This arises few questions for me
The text was updated successfully, but these errors were encountered: