-
Notifications
You must be signed in to change notification settings - Fork 225
Element template restructure #7475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
docs/components/modeler/element-templates/getting-started/using-templates-in-web-modeler.md
Show resolved
Hide resolved
|
👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
|
@YanaSegal there is no rush on review here, but let me know if you have any questions 👍 This covers phases 3 and 4 of https://github.com/camunda/product-hub/issues/2407, effectively completing all of the docs work to close this epic. |
|
The preview environment relating to the commit bcf2f64 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-7475/ |
Description
This PR restructures and modernizes all element template documentation as part of phase 3 and phase 4 of epic https://github.com/camunda/product-hub/issues/2407. The goal is to centralize content, improve discoverability, remove duplication, and align terminology across Web Modeler and Desktop Modeler.
What was done
components/modeler/element-templates/about-templates.md)No information was removed—existing material was:
Why Web Modeler–specific pages were removed
Web Modeler now embeds element template workflows directly into its modeling experience (apply, remove, update, save-as, publish).
Because these workflows are no longer distinct enough to justify stand-alone pages, all Web Modeler content was consolidated into:
getting-started/using-templates-in-web-modeler.mdgetting-started/save-as-element-template.mdindex.mdThis avoids duplication and ensures users learn element templates conceptually first, then see how they behave in Web Modeler within a single, streamlined flow.
Why Desktop Modeler still has a dedicated configuration page
Desktop Modeler handles configuration differently from Web Modeler (file-system–based template discovery, global vs. local templates).
This behavior remains unique and required a single, dedicated page:
desktop/configuring-templates-for-desktop-modeler.mdThis page consolidates all Desktop-specific loading rules in one place without duplicating conceptual content found elsewhere.
Important note
Although many old pages were removed, no content was lost.
All functional material was rewritten, reorganized, or merged into the new structure.
This PR focuses on structure, clarity, and consolidation—not deletion of documentation coverage.
Outcome
Mapping of old → new content
When should this change go live?
bugorsupportlabel)available & undocumentedlabel)holdlabel)low priolabel)PR Checklist
{type}(scope): {description}commit message(s)/docsdirectory (version 8.9)./versioned_docsdirectory.@camunda/tech-writersunless working with an embedded writer.