Starting to rebuild my site to get off of Jekyll/GitHub pages. I think I have a static site generator that is simple and flexible. Here's how it works: by default it just recurses through a source directory, rendering markdown files into HTML and copying everything else verbatim. If it encounters a static site generation script while recursing though it invokes it instead, allowing for arbitrary custom logic.
For example, certain subpages require custom indexing, like my portfolio projects or my blog. Some subpages should actually clone a totally different repository and run some commands, EG in the case of generated documentation for projects. Coming up with a generic system to cover all these cases is a quagmire, so I'm thinking it's just simple default behavior plus software for customization.
@gaeel oh interesting! can you elaborate on that? what do you mean by a refactor in the context of a website/blog?
@gaeel hmm thats a level of granularity i never considered, honestly. i feel like i am OK with those? i like the idea of using git to get a "created" date which is fixed to the repository. if you wanted i suppose you could filter the commits based on commit message to filter out insignificant changes. ie commits with [typo] in the message do not contribute to the public "history"
@nasser yeah, that could work
i think i'm focusing more on a files-only system though, having part of the data encoded in files and another part encoded in the vcs complicates things