Welcome to Decentraland technical documentation, the goal of this repository is to have a single point of access for all necessary information to use, create and contribute to Decentraland.
The repository will scrap a configurable list of directories and render the content of their docs folder. Sidebar stucture can be completely configured in each repository.
Technical documentation is divided in three major areas:
In this repository:
In your repository:
Create a docs folder at root level
Push your documents as .md files
Create a summary.json file with the sidebar wanted structure:
Example:
```jsx/*This structure renders the following sidebar inside the contributor docsSDK- Diagrams-- Metaverse runtime*/{"contributor": [{"name": "SDK","children": [{"name": "Diagrams","children": [{"name": "Metaverse runtime","slug": "/contributor/sdk/diagrams/metaverse-runtime"}]}]}]}```COPY CODE
See sample summary
// TO - DO
Repository to test the health and integration of static pipelines
Implements all the pipeline stages of this document:
https://docs.google.com/drawings/d/1hDa0mOk4Fb0rwzDKR8AVzLQeINlPmKqEIABeEyS_LNE/edit
Every push to master generates an NPM package, it is published with the @next
dist-tag
Every semver release creates and publishes a @latest
dist tag
Every time a package is published, the gitlab pipeline pipelines/static-sites-pipeline is triggered. That pipeline uploads the content of the published package to https://cdn.decentraland.org
The then pipeline starts a rollout pipeline. Which is out of scope of this documentation.