Documentation - Docusaurus port #586
Merged
Conversation
This file contains 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
Documentation docusaurus port
Start iterating over config to show in downloads
…nStickCommunity/GP2040-CE into documentation-docusaurus-port
arntsonl
reviewed
Oct 24, 2023
arntsonl
reviewed
Oct 24, 2023
…into documentation-docusaurus-port
…into documentation-docusaurus-port
|
Looks great! |
arntsonl
added a commit
that referenced
this pull request
Nov 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This port should contain all of the current documentation that is live on the documentation site as of the time of this PR.
I have a test version of this site running one https://infraredaces.github.io/docusaurus-test/ , if you would like to see it live and test.
There are only a few things left to do before and after this PR is merged to allow the workflow to deploy the site, but they are only performable by maintainers of the repo.
Read and Writeaccess to the Contents of the repo, name it "ACTION_SECRET", and then place it in Repository Secrets. The name can be changed, however the deploy.yml contents will need to be updated as well.gh-pagesbranch that thedeployaction creates.This action will create a branch of that consists of only the static files generated during the build process and result in the pages seen in the test site linked above.