Setup the repository
Here's the link to the example repo: https://github.com/dragosbulugean/slate
If Archbee finds a .archbee.yaml file in the root of the repo like this one https://github.com/dragosbulugean/slate/blob/master/.archbee.yaml, then we use that to organize the content, or if we don't, we just set some defaults.
Create a .archbee.yaml file with the following variable structure. The file must be located at the root of your repository.
root: ./docs property defines where's the directory containing the docs(can be replaced with docsPath: ./docs)
- summary: summary.md reconstructs the document tree in the left navigation panel in Archbee. If there is none, we consider the folders to be the categories and mimic the file structure inside.
- readme: Introduction.md We currently use it for the root of the collection when you publish it. For example, you can use this file if you want something at the bare domain or subdomain (without any pathing).
- assets: assets the assets folder is relative to docsPath. Archbee will upload all files found from that folder.
- shadowDocs define the code files/folders to be included as Shadow Docs
Example of an archbee.yaml config file:
Example of an archbee.json config file:
The summary.md reconstructs the document tree in the left navigation panel in Archbee. It is recommended to have a summary, as it can help you organise your content nicely. See an example of a summary.md below:
Some of the blocks Archbee's editor support can be rendered if you are using specific syntax.
Check the Editor Markdown Shortcuts to use the shortcuts.