federicoponzi / genereto Goto Github PK

View Code? Open in Web Editor NEW

1.0 1.0 0.0 366 KB

A static site generator for blogs.

Rust 75.63% Shell 0.49% HTML 23.88%

genereto's People

Contributors

Stargazers

Watchers

genereto's Issues

Add a cli option to generate a project

genereto --new <project-path>

will either generate the files or fetch a base template and unzip it.

Add a sample template

that uses all the variables and features.

Verify broken links

an idea for later - right now genereto is handling all internal links.

Treat .html as .md, but add some macros/metasomething to disallow template parsing.

Potential idea: support template_base_filename in metadata

not necessarily template_base_filename, but the idea would be to allow to use different template source file for different files.
for example, use index.html for index.md and page.html as source for mycoolpage.md and myproject.html for genereto.md and so on. Not sure if it's worth having though.

Add last update date

Can be derived from git

Host documentation online

it would be nice to have it hosted somewhere.

Add build release

Add support for comments and TODOS.

as oppposed to variables which are embedded in templates, these are embedded in articles:

$GENERETO{this is a comment and it will be removed from the final output.}

This allow support for TODOs:
$GENERETO{TODO:} <- if it has todo, it won't be published. A line is printed to tell that it's not gonna get published even if is_draft is false.

provide git hooks to validate pages are valid

Add support for non-blog websites

It should support creations of blog and custom websites. I'm planning to use it for fponzi.me and blog.fponzi.me for example. They will share the same template.

In my case, both will need to generate an index.html because they're on different domains. For this reason, I'll need to add support of a config entry to specify if we want to use the template to generate a blog or an index page.

it's a bit annoying because I would like to support both cases of:

two projects, one template used to generate a blog and a website
one project, one template used to generate a blog and a website

I'd like to achieve this with the minimum additional config. This is the plan:

all blog entries are inside the content/blog folder. If there is a blog folder, then assume user wants to generate a blog.
the config will specify the index page to use to hold the blog index.

blog:
    base_template: index.html # default 
    index_destination: index.html # default

if there is an index.md file, it means the user wants to generate a custom website. If there is an index.md file, then the user needs to change the index_destination value for the blog in the config.

myCoolkey = 1234
----
## hello world! 
my article

template:

<html>
<title>my page id $GENERETO[1234]</title>
<body>
<!-- start_content -->
<!-- end_content -->
</body>

federicoponzi / genereto Goto Github PK

genereto's People

Contributors

Stargazers

Watchers

genereto's Issues

Recommend Projects

Recommend Topics

Recommend Org