Project Overview Contributor Stackable Documentation

Project Overview Contributor Stackable Documentation Project overview the stackable data platform is made up of many different components, with code and tools spread across multiple repositories, and artifacts stored in multiple locations. this page gives you a high level overview of all the technical bits in the stackable organization. The stackable contributor’s guide containing more info on how to contribute to the documentation.

Project Overview Contributor Stackable Documentation Welcome to the stackable documentation. stackable allows you to model content for websites & apps easily and have this available through a secure modern api. all data is returned in json including errors. The main repository for the documentation is the documentation repository and each operator and other tools have a docs directory from which content is pulled in. have a look at the project overview to learn about the repositories that are involved in providing the documentation. If you want to contribute documentation, follow the contributing to documentation guideline, as well as the general pull request guidelines below. please see the project overview page to get an overview of the most important git repositories in the stackable organization. This repository hosts the antora playbook file as well as platform documentation. other stackable repos contain docs directories which are pulled in by this repo.

Project Overview Contributor Stackable Documentation If you want to contribute documentation, follow the contributing to documentation guideline, as well as the general pull request guidelines below. please see the project overview page to get an overview of the most important git repositories in the stackable organization. This repository hosts the antora playbook file as well as platform documentation. other stackable repos contain docs directories which are pulled in by this repo. This guide covers the steps for internal and external contributors. differences will be outlined. depending on the project, not all steps make sense. for instance, if the documentation was changed then the integration tests need not to be adapted. please skip the steps which are not applicable. To understand the repositories involved in building the documentation, see project overview. for an overview of the content structure and the tools involved, see the documentation overview. to contribute, follow the pull request flow outlined in the contributor’s guide. Glossary duration format contributor’s guide project overview contributing code understanding the integration testing infrastructure testing your code on kubernetes. If it is useful for the users of the project to know about the change then it must be added to the changelog. for instance, if only the dependencies in an operator are upgraded but nothing changes for the user then the upgrade should not be added to the changelog.