Skip to content

Conversation

@alourie
Copy link
Contributor

@alourie alourie commented Nov 27, 2025

Description

This change refactors how we build documentation:

  • Introduce a new workflow, build-docs that calls docusaurus-action and builds the docs.
  • It can also optionally "version tag" the docs
  • It can also "deploy" the docs (ie build the zipped archive for later deployment).
  • It introduces the use of a new environment parameter called PRODUCT (to deploy evolve and ednar).

Other workflows were adapted to use this new flow.

The benefit of this refactoring is that all aspects of the documentation building are now controlled centrally via 1 flow.

Testing

Currently testing the following flows:

  • Maven (build, snapshot, release)
  • Python (build, snapshot, release)
  • NPM
  • C#

Dependency

This will also require zepben/docusaurus-action#18 PR to be merged.

Breaking Changes

  • I have considered if this is a breaking change and will communicate it with other team members by posting it on the Slack breaking-changes channel.

This is quite a big change and I might have missed something somewhere, so will have to be diligent and fix fast.

@ryanjcoleman
Copy link
Member

@alourie alourie force-pushed the OPS-510-support-ednar branch from ddb26f9 to 5e40acf Compare November 28, 2025 02:12
This change refactors how we build the documentation:

- Introduce a new workflow, build-docs that calls docusaurus-action and builds the docs.
  - It can also optionally "version tag" the docs
  - It can also "deploy" the docs (ie build the zipped archive for later deployment).
- It introduces the use of a new environment parameter called PRODUCT (to differentiate the deployment of evolve and ednar).

Other workflows were adapted to use this new flow.

The benefit of this refactoring is that all aspects of the documentation building are now controlled centrally via 1 flow.
Additionally, it allows to easily create separate, stand-alone docs-deployment flows.

Signed-off-by: Alex Lourie <[email protected]>
@alourie alourie force-pushed the OPS-510-support-ednar branch from 5e40acf to 44257ab Compare November 28, 2025 02:16
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
@alourie alourie marked this pull request as ready for review November 28, 2025 02:36
@alourie alourie requested a review from kgreav November 28, 2025 02:36
kgreav
kgreav previously approved these changes Nov 28, 2025
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Signed-off-by: Alex Lourie <[email protected]>
Copy link
Member

@charlta charlta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved so you can merge if you don't need to address anything with my question.

@alourie alourie merged commit a52e05c into main Dec 1, 2025
1 check passed
@alourie alourie deleted the OPS-510-support-ednar branch December 1, 2025 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants