The documentation service exposes both the user and the developper documentation to the public. The content is managed by Sekoia.io teams but the community is invited to participate in its improvements.
You can click the Fork button in the upper-right area of the screen to create a copy of this repository in your GitHub account. This copy is called a fork. Make any changes you want in your fork, and when you are ready to send those changes to us, go to your fork and create a new pull request to let us know about it.
Once your pull request is created, a Sekoia.io reviewer will take responsibility for providing clear, actionable feedback.
This project is managed by mise-en-place. Please refer to the Getting Started to install this tool.
After having installed mise-en-place, set up the project:
$ mise run installThe service relies on the MkDocs Python framework helped by MkDocs-Material. To serve the documentation on the port 8000 of your computer, you should trigger the execution of the MkDocs server:
$ mise run doc:serveThe front end is placed in ./lib/openapi-viewer. To serve the doc locally, you need to load the back end service upper.
Start the back:
$ mise run doc:serveIn another shell, Launch the front
$ mise run openapi:devGo to http://127.0.0.1:8080/developer/api/
- You may use absolute links and images such as
[caption](/folder/page.md#anchor)or, they will be interpreted as relative to thedocs/folder. So the example link would point todocs/folder/page.mdwhich must exist in the repo.mkdocs serve --strictwill help you catching any broken link - When you want to point to the developer documentation, please use full URLs, such as
[delete_playbook_endpoint](https://docs.sekoia.com/xdr/develop/rest_api/playbooks/#tag/Playbooks/operation/delete_playbook_resource), because the API documentation is rendered client-side via ReDoc out of OpenAPI specs retrieved from app.sekoia.io platform's API - Always include the
.mdextension when linking to markdown files in the repo:[link](/integration/example/index.md)is okay, whereas[link](/integration/example/)or[link](/integration/example/index)won't work. - All links to internal pages and anchors are strictly validated by the CI (via
mkdocs build --strict) to spot any broken link. Therefore, please refrain as much as possible from using full URLs to point to internal pages, as they won't be covered by automated broken link verification.