docs: move the documentation site to craftbot-live - #428
Merged
Merged
Conversation
The mkdocs source moves to CraftOS-dev/craftbot-live, where the rest of the product's web presence lives. Nothing in this repo referenced mkdocs/: no workflow built it, no script or spec pulled from it, and no file outside the directory linked into it, so the removal is self-contained. The one coupling ran the other way. mkdocs.yml generated its default-actions page by parsing the @action(...) decorators in app/data/action/. That generator moved with the docs and now runs on demand against a checkout of this repo, so the catalogue still comes from these decorators and stays refreshable after actions change here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The mkdocs source moves to CraftOS-dev/craftbot-live, where the rest of the product's web presence lives. Nothing in this repo referenced mkdocs/: no workflow built it, no script or spec pulled from it, and no file outside the directory linked into it, so the removal is self-contained.
The one coupling ran the other way. mkdocs.yml generated its default-actions page by parsing the @action(...) decorators in app/data/action/. That generator moved with the docs and now runs on demand against a checkout of this repo, so the catalogue still comes from these decorators and stays refreshable after actions change here.