Skip to content

Conversation

LAShemilt
Copy link
Collaborator

In this PR:

  • set up of structure of documentation template with mkdocs.
  • Introduction of consistent styling and branding
  • versioning docs with mike
  • switch between nested README.md or having a docs folder
  • local environment set up for testing
  • README.md describing how to use the docs in your set up

LAShemilt and others added 12 commits September 19, 2025 12:22
…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
@LAShemilt LAShemilt changed the title WIP: Initial setup Initial setup Sep 23, 2025
@LAShemilt LAShemilt requested a review from minottic September 23, 2025 15:02
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:
Copy link
Member

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:
Copy link
Member

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

Copy link
Member

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

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.
Copy link
Member

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.
Copy link
Member

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 }} |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the TAG has the effect also to generate versions dropdown in the doc page

see here:

Image

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.

2 participants