Sensedia Docs provides a streamlined process for publishing documentation.
Publishing documentation is a crucial step in the documentation lifecycle. Sensedia Docs offers a variety of tools and features to help you publish your documentation efficiently and effectively. In this guide, we will walk you through the process of publishing your documentation using Sensedia Docs.
Before you can publish your documentation, you need to set up your project. This involves creating a new project in Sensedia Docs and configuring it to suit your needs.
Inside the cloned repository, you will find an example
directory. This directory contains a sample project that you can use as a starting point for your documentation.
Open the bitbucket-pipelines.yml
file and configure it according to your project's requirements. This file defines the publishing pipeline and specifies how your documentation will be deployed.
Ensure that your Bitbucket repository is set up correctly to trigger the pipeline when changes are pushed. This includes setting up environment variables STRAPI_URL
, STRAPI_TOKEN
.
You need to access Strapi to generate these tokens, which are used to authenticate and authorize your documentation updates.
Once your project is set up, you can start creating your documentation. Sensedia Docs provides a user-friendly interface for authoring and organizing your content. You can create different types of documents, such as guides, API references, and tutorials, using Markdown + visualizer (Sensedia Docs VSCode Extension).
The publishing process is managed by Bitbucket Pipelines, which automatically builds and deploys your documentation when you push changes to the repository. The pipeline defined in the bitbucket-pipelines.yml
file will handle the build and deployment process.
The pipeline is automatically triggered when you push changes to the repository. Ensure that your bitbucket-pipelines.yml
file is correctly configured to main
branch.
Make sure you have pushed your changes to the correct branch and that the pipeline has completed successfully. Check the pipeline logs for any errors.
Simply make changes to your Markdown files and push them to the repository. The pipeline will automatically rebuild and redeploy your documentation.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more