-
Notifications
You must be signed in to change notification settings - Fork 0
Initial setup #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…ith repository usage
…ild, deleting docker compose as this is too convoluted to run in docker without oa lot of work
… plugins. Commented out awesome-plugins as it was interfering with nav section
* Move docs to github folder * Update requirements.txt to include glightbox * Add docker compose for local dev * Update readme to use docker compose * Move to actions folder * Enable action to use local defaults * Update readme to use action as recommendation * Add override option
README.md
Outdated
│ └── workflows/publish-docs.yml | ||
├── docs/> └──Example.md | ||
``` | ||
Once you have added your documentation you need to add it to the navigation on the `.github/actions/mkdocs/mkdocs.yml`. Open the file and add your page in the nav section: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment above
|
||
extra_css: | ||
- css/custom.css | ||
hooks: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for this first implementation, I would remove the hook, it is a bit scicatlive specific
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we probably need an explanation of the action here, including inputs
8fb0683
to
0012901
Compare
…y mkdocs. Included instructions in the repo's README.md
README.md
Outdated
|
||
### Use a docs directory | ||
|
||
Make a `docs` directory in the root directory of your repository and add markdown files to it. To use add your new files to the docs you will need to copy the file [./.github/actions/mkdocs-pages/mkdocs.yml](./.github/actions/mkdocs-pages/mkdocs.yml) to your repository in a `.github/actions/mkdocs` directory. From here add to the `nav` panel to add your new docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this section is wrong, if I understand right there is no need to copy the file, but only do what explained in the example
README.md
Outdated
site_name: my-site-name | ||
``` | ||
|
||
If your pages setup requires additional Python packages, you can specify them in [.github/mkdocs/requirements.txt](.github/mkdocs/requirements.txt) The action will install these dependencies automatically. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the requirements.txt will replace the one in the action, so maybe it's worth adding a note that this does not add
but rather replaces
README.md
Outdated
| Input Name | Description | Required | Type | Default | | ||
| ---------- |----------| -------| ------| ------| | ||
| GITHUB_TOKEN | GitHub token used for authentication when pushing changes. | true | string | N/A | | ||
| TAG | Commit, tag, or branch to use for generating GitHub links. | false | string | ${{ github.ref_name }} | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this PR:
docs
folder