Skip to content

Conversation

@OrsellGit
Copy link
Contributor

Improved the contribution documentation to include some more information on how one can contribute to the Wiki, as well as instructions on getting started with the Wiki software.

Changes:

  • Moved the structures.md article from the Advanced to the Basic topic. There is nothing really advanced about it, except for Categories, which now has its own article under advanced.
  • Added how to make articles as well as making links between them and headers since editing articles was the only thing exaplained at the time. Also added some links to how Markdown styling is done for those who have not touched Markdown before.
  • Changed the _meta.json file to meta.json under the Testing Suite section. Not sure if that was done on purpose or not.
  • Added article for getting started with the Wiki software. Includes several VSCode extensions to help with devlelopment and explains the key folders used by the software.
  • Added a article for adding a category to the Home page of the Wiki.

@OrsellGit OrsellGit added the documentation Improvements or additions to documentation label Jan 9, 2026
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Jan 9, 2026

Deploying wiki with  Cloudflare Pages  Cloudflare Pages

Latest commit: 0b16a2e
Status:🚫  Build failed.

View logs

@OrsellGit OrsellGit requested review from JJL772 and ozxybox January 9, 2026 20:09
@ozxybox
Copy link
Member

ozxybox commented Jan 11, 2026

The test category should probably be left hidden for now, otherwise it'll show up in search results.

Copy link
Member

Choose a reason for hiding this comment

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

probably dont need to put adv- in the file name, as it'll already be prefixed with advanced


This Wiki topic assumes that you understand how to work with TypeScript, SCSS, HTML, Svelte, as well as Git submodules. The Wiki software is a submodule separate from the documentation.

If you followed the instructions from [Getting Started](../basics/getting-started), then the Wiki software should already be setup correctly. However, if you wish to contribute to the Wiki software, you will need to make a fork of the repository so an Pull Request can be created. If you remove the current `site` folder in the `Wiki` repository and replace it with your own fork under the same name, then the Wiki will use your version of the software.
Copy link
Member

Choose a reason for hiding this comment

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

Rather than removing the site folder, the correct thing to do would be to repoint the git remote at the url of your fork. deleting and pasting in a new git repo may screw up the submodule

@OrsellGit
Copy link
Contributor Author

OrsellGit commented Jan 11, 2026

The test category should probably be left hidden for now, otherwise it'll show up in search results.

The Test Suite is programmed in the software to not show up, I believe, not base on the meta.json file existing, let me check again just in case.

@ozxybox
Copy link
Member

ozxybox commented Jan 11, 2026

If you try searching for text from there it'll still appear. we'd probably also need to exclude it in the robots.txt file


# Making A New Category

Making a category requires that the Markdown documentation files for the category are provided. At minimum, a Markdown file and a `meta.json` file is needed to make an category work. Check out the [Category section](../basics/structure#categories) of the `Wiki Structure` article to know how to set up the `meta.json` file.
Copy link
Member

Choose a reason for hiding this comment

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

I would maybe merge the first two sentences. The first sentence sounds a bit off

Comment on lines +6 to +7
# Making A New Category

Copy link
Member

Choose a reason for hiding this comment

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

I would describe what these are a bit more. Maybe refer to it as a "top level category", and explain that it appears on the main page of the wiki. Took me a second to realize what this was lol

Comment on lines +10 to +12
Articles on the Strata Source Wiki consist of Markdown files that work with the [standard set of syntax](https://www.markdownguide.org/basic-syntax/).

The Wiki also follows some, but not all, of [GitHub's Markdown styling formats](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) (Ex. Alerts/Notices).
Copy link
Member

Choose a reason for hiding this comment

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

I would combine these sentences perhaps. Could also note the auto docs

Articles on the Strata Source Wiki consist of a mix of Markdown files and autogenerated docs from JSON dumps. The markdown docs follow mostly standard syntax with some of GitHub's syntax

or something vaguely similar (but maybe fancier words as you had prior)


The Wiki also follows some, but not all, of [GitHub's Markdown styling formats](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) (Ex. Alerts/Notices).

All the Markdown files on the Wiki are inside topics. Topics are the folders that make up certain sections of categories. Example of `Category/Topic/Article`: `Audio/Overview/Sound System`. These Markdown files are placed into where they should displayed in the Wiki.
Copy link
Member

Choose a reason for hiding this comment

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

we dont use it much, but you can make folders nested within topics as well. such as category/topic/subtopic/subtopic2/article

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

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants