Documentation for Kestra — an event-driven, language-agnostic orchestration and scheduling platform to manage millions of workflows declaratively in code.
We want to add section headers that will serve as categories for the documentation to make finding the right information easier. Instead of further nesting the docs, the headers will make it easier to highlight the right sections of the docs for any stage of the adoption (getting started, building with kestra, managing kestra, scaling, etc...)
We want to add section headers that will serve as categories for the documentation to make finding the right information easier. Instead of further nesting the docs, the headers will make it easier to highlight the right sections of the docs for any stage of the adoption (getting started, building with kestra, managing kestra, scaling, etc...)
Figma: https://www.figma.com/design/g8Di3M1gbajOjOqp0ZrzXO/02_Kestra.io?node-id=12960-13588&t=Ue3jxy4m9dwBEuud-4
To determine which section will be shown under which category, we can extend this part https://github.com/kestra-io/docs/blob/9aa471873e7d369aa9ff55051f7035abffe73d84/nuxt.config.ts#L131-L136
with the specification of sections:
(credits to @wrussell1999 for all the work below, I'm only opening an issue for tracking)