Skip to content

RHIDP-12203: CQA 2.1 compliance for About Red Hat Developer Hub title#1872

Open
themr0c wants to merge 1 commit intoredhat-developer:mainfrom
themr0c:RHIDP-12203
Open

RHIDP-12203: CQA 2.1 compliance for About Red Hat Developer Hub title#1872
themr0c wants to merge 1 commit intoredhat-developer:mainfrom
themr0c:RHIDP-12203

Conversation

@themr0c
Copy link
Member

@themr0c themr0c commented Mar 5, 2026

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s): main

Issue: https://issues.redhat.com/browse/RHIDP-12203

Preview: To be added

Summary

This PR enhances the "About Red Hat Developer Hub" title for CQA 2.1 compliance and Adobe Experience Manager (AEM) migration readiness:

  • Added short descriptions: All modules now include [role="_abstract"] with 50-300 character descriptions
  • Fixed DITA compatibility: Converted 7 block titles (.Title format) to section headings (== Title format)
  • Improved module titles: Changed concept module title from imperative verb ("Achieve high availability...") to noun phrase ("High availability...")
  • Grammar fixes: Corrected parallel structure ("helps simplify and accelerate" vs "helps simplify and accelerates")
  • Assembly compliance: Added context restoration to assembly file, removed commented-out content
  • Validation: All changes pass Vale DITA validation with 0 errors, 0 warnings, 0 suggestions

Files Changed

  • assemblies/assembly-about-rhdh.adoc
  • modules/about/con-achieve-high-availability-with-database-and-cache-layers.adoc
  • modules/about/con-integrations-in-rhdh.adoc
  • modules/about/con-system-architecture-for-deployment-planning.adoc
  • modules/about/con_understanding-internal-developer-platforms.adoc
  • modules/about/ref-customer-support-info.adoc
  • modules/about/ref-rhdh-sizing.adoc
  • modules/about/ref-supported-platforms.adoc

All CQA 2.1 acceptance criteria are met, making this content ready for AEM migration.

Enhance About title for Adobe Experience Manager migration compliance:
- Add short descriptions with [role="_abstract"] to all modules
- Convert DITA-incompatible block titles to section headings
- Fix grammar and parallel structure issues
- Improve concept module title from imperative to noun phrase
- Add context restoration to assembly file
- Remove commented-out content

All changes pass Vale DITA validation with 0 errors, 0 warnings.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 5, 2026

@themr0c themr0c deployed to internal March 5, 2026 17:42 — with GitHub Actions Active
@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Mar 5, 2026

Copy link
Member

@lhite8041 lhite8041 left a comment

Choose a reason for hiding this comment

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

Claude seems prone to generate overly complex single sentences for short descriptions. We'll all need to be on the lookout for that.


An internal developer platform (IDP) is a curated set of tools and services that supports developer self-service. Instead of navigating multiple systems, developers use a unified interface to provision environments, deploy code, and access APIs.
[role="_abstract"]
Internal developer platforms enable developer self-service through a unified interface for provisioning environments, deploying code, and accessing APIs, reducing complexity across development workflows.
Copy link
Member

Choose a reason for hiding this comment

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

To improve readability, I'd split this into two sentences:

Internal developer platforms (IDPs) provide a unified interface that enables developer self-service for provisioning environments, deploying code, and accessing APIs. By centralizing these tools, IDPs reduce complexity across development workflows.


To achieve high availability (HA) in {product}, you must implement redundancy and failover for the backend service and its external data dependencies. This configuration uses horizontal scaling, database replication, and a shared logical cache to make sure {product-very-short} remains operational during component failures.
[role="_abstract"]
High availability in {product} requires redundancy and failover for the backend service and data dependencies by using horizontal scaling, database replication, and shared caching to ensure continuous operation during failures.
Copy link
Member

Choose a reason for hiding this comment

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

To improve readability, split into two sentences:

Achieving high availability in {product} requires implementing redundancy and failover for both the backend service and its data dependencies. This is accomplished through horizontal scaling, database replication, and shared caching to ensure continuous operation during component failures.

= {product} support

[role="_abstract"]
{company-name} provides support resources through the Customer Portal, including technical support articles and the ability to create support cases for Global Support Services.
Copy link
Member

Choose a reason for hiding this comment

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

The short description repeats what is already in the module body. I think you can just separate the first sentence from the body and make it the short des: "If you experience difficulty with a procedure described in this documentation, visit the {company-name} Customer Portal for more resources."


Learn about sizing requirements for {product}.
[role="_abstract"]
Plan infrastructure resources for {product} deployments using sizing requirements for the application, database, and Operator based on deployment scale.
Copy link
Member

Choose a reason for hiding this comment

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

The last four words of the sentence are redundant, so I'd delete them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants