Skip to content

Conversation

@mrshll1001
Copy link
Contributor

Following on from #426, this commit removes the non-normative content files from the documentation folder.

mrshll1001 and others added 2 commits December 10, 2025 11:06
Following on from #426, this commit removes the non-normative content files
from the documentation folder.
Noticed that we weren't including the guidance to individuals in the
toctree, so this indicated that it should be deleted along with the
contents of `/guidance`.
mrshll1001 added a commit that referenced this pull request Jan 15, 2026
Updated the eval_rst syntax to myst-parser syntax: ```{eval-rst}

Did not update anything in the guidance section, as this would create a
conflict with #428
mrshll1001 added a commit that referenced this pull request Jan 15, 2026
Files under documenation/guidance are removed in #428, but this is
awaiting merge.

This commit updates the eval_rst syntax in these files similar to the
previous commit to ensure that the docs can build properly on this
branch in the interim.

This commit is designed to be dropped in an interactive rebase, after
the merge of #428 into main
@mariongalley
Copy link
Contributor

@mrshll1001 Once we remove the files, are they archived/saved anywhere?

@mrshll1001
Copy link
Contributor Author

@mariongalley

Once we remove the files, are they archived/saved anywhere?

Yes, as part of the git history of the repository.

If we remove them from the main branch via merging/rebasing on this commit; we can go back in time to a commit before they were removed, to retrieve them. This involves checking out a specific commit locally, and then the files will be there. From there, someone can copy/save them elsewhere to preserve them or re-integrate them into the repository by creating a commit which adds them back in or reverts the commit which removed them specific commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants