The build should collect various meta data to assist or inform the user when building the site.
all content files, mtime, maybe some kind of fast hash (BLAKE3?)
the urls the content is rendered at
all used tags
all used sections
This data can later be used to implement incremental builds, to warn the user when they add a new tag or section (perhaps it's a typo), to create redirects for SEO when content is moved, ...
There is still the question as to when the meta data should be updated, for example if you build the current content with a typo in the section and receive a warning, we obviously don't want that committed to the valid sections metadata. Something to consider, perhaps it should be a separate command that you decide to run, or that you are prompted for after the build is complete.
The build should collect various meta data to assist or inform the user when building the site.
- all content files, mtime, maybe some kind of fast hash (BLAKE3?)
- the urls the content is rendered at
- all used tags
- all used sections
This data can later be used to implement incremental builds, to warn the user when they add a new tag or section (perhaps it's a typo), to create redirects for SEO when content is moved, ...
There is still the question as to when the meta data should be updated, for example if you build the current content with a typo in the section and receive a warning, we obviously don't want that committed to the valid sections metadata. Something to consider, perhaps it should be a separate command that you decide to run, or that you are prompted for after the build is complete.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The build should collect various meta data to assist or inform the user when building the site.
This data can later be used to implement incremental builds, to warn the user when they add a new tag or section (perhaps it's a typo), to create redirects for SEO when content is moved, ...
There is still the question as to when the meta data should be updated, for example if you build the current content with a typo in the section and receive a warning, we obviously don't want that committed to the valid sections metadata. Something to consider, perhaps it should be a separate command that you decide to run, or that you are prompted for after the build is complete.