Skip to content

Commit d4c5a9a

Browse files
openshift-cherrypick-robotthemr0cdeerskindoll
authored
[release-1.8] RHIDP-2135: README update (redhat-developer#1517)
Co-authored-by: Fabrice Flore-Thébault <[email protected]> Co-authored-by: deerskindoll <[email protected]>
1 parent bfee658 commit d4c5a9a

File tree

1 file changed

+129
-8
lines changed

1 file changed

+129
-8
lines changed

README.adoc

Lines changed: 129 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,147 @@
11
# Red Hat Developer Hub documentation
22

3-
This repo is the upstream mirror of https://gitlab.cee.redhat.com/red-hat-developers-documentation/rhdh
3+
This is a repository for Red Hat Developer (RHDH) documentation.
44

5-
Contribute to this repo and merged changes will be synced to gitlab for build with Pantheon.
5+
## Contributing
6+
7+
Contribute to this repository to add new and edit existing RHDH documentation published on the link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/[Red Hat Documentation page].
8+
9+
Before submitting a pull request (PR), create a Jira issue associated with your contribution to this repository.
10+
11+
There are currently three Jira projects related to RHDH:
12+
13+
* link:https://issues.redhat.com/projects/RHDHBUGS[RHDHBUGS] - For issues related to existing content.
14+
* link:https://issues.redhat.com/projects/RHIDP[RHIDP] - For new features related to the core platform, including security mechanisms.
15+
* https://issues.redhat.com/projects/RHDHPAI[RHDHPAI] - For new features related to plugins and AI.
16+
17+
Choose a Jira project that matches your contribution and create a new issue:
18+
19+
. In the Jira project, click *Create*.
20+
. In the *Description* field, describe your contribution.
21+
. In the *Component/s* field, select *Documentation* from the drop-down list.
22+
. Save the created Jira issue.
23+
24+
[IMPORTANT]
25+
====
26+
RHDH release notes are single-sourced from the *Release Notes Text* field in the Jira Epic.
27+
If you want to make changes to release notes, you must make them in Jira.
28+
Check the link:https://docs.google.com/document/d/1X2CrrU9K3ZqbxN7DXmU6P1mY7inLD32qs3rpOUHz6Vw/edit?tab=t.0#heading=h.yqxd252ryhua[RHDH Release Notes process document] for more information.
29+
====
30+
31+
## Style and formatting
32+
33+
All contributions are in AsciiDoc.
34+
35+
Make sure your writing follows the rules
36+
listed in link:https://www.ibm.com/docs/en/ibm-style[IBM Style] and link:https://redhat-documentation.github.io/supplementary-style-guide/[Red Hat supplementary style guide].
37+
38+
[NOTE]
39+
====
40+
If the IBM Style and the Red Hat supplementary style guide offer conflicting solutions,
41+
the Red Hat supplementary style guide solution overrides IBM Style.
42+
====
43+
44+
Follow the link:https://redhat-documentation.github.io/modular-docs/[Modular documentation reference guide]
45+
to modularize your content.
646

747
## Building locally
848

949
. Install `asciidoctor` - see https://docs.asciidoctor.org/asciidoctor/latest/install/linux-packaging/
10-
. Run `build/scripts/build.sh` to generate html with images in titles-generated/ folders
50+
. Install Podman - see https://podman.io.
51+
. Run the following command to generate html with images in titles-generated/ folders by using `ccutil` in a container.
52+
The `ccutil` CLI tool reproduces the behavior of the production publication chain (Pantheon), including its limitations, and is therefore preferred over using a more recent `asciidoctor` CLI version.
53+
+
54+
[source,terminal]
55+
----
56+
$ build/scripts/build-ccutil.sh
57+
----
58+
59+
[NOTE]
60+
====
61+
* To build with `asciidoctor` rather than `ccutil`, run the following script.
62+
The output will look differently and you might miss issues with content that cannot build in production.
63+
+
64+
[source,terminal]
65+
----
66+
$ build/scripts/build.sh
67+
----
68+
====
69+
70+
## Checking for broken links
71+
72+
You can run `htmltest` locally to check for broken links in your PR.
73+
74+
. Install `htmltest` from https://github.com/wjdp/htmltest
75+
. Run the following command:
76+
+
77+
[source,terminal]
78+
----
79+
$ htmltest
80+
----
81+
82+
You can run `linkchecker` to check for broken links in the published RHDH docs.
83+
84+
. Install `linkchecker` from https://github.com/linkchecker/linkchecker.
85+
. Run the following command to create a .txt file with a list of detected broken links:
86+
+
87+
[code,terminal]
88+
----
89+
$ linkchecker --check-extern --output failures --file-output failures/broken-links.txt https://docs.redhat.com/en/documentation/red_hat_developer_hub/<version>
90+
----
1191

1292
## Previews
1393

14-
Commits to this repo can be seen as GH Page content here:
94+
You can view commits to this repo as GitHub Page content here:
1595

1696
https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/
1797

18-
Pull requests will have a link to the generated HTML attached a comment.
98+
PRs have a link to the generated HTML attached as a comment.
1999

20-
## Contributing
100+
## Reviews
101+
102+
All PRs are reviewed for technical accuracy by an SME and writing quality by another tech writer.
103+
104+
When possible, request a tech review first and implement suggestions from the SME.
105+
After your PR is approved by the tech reviewer, follow it up with a request a peer review.
106+
107+
Check link:https://docs.google.com/spreadsheets/d/1X1KHZx2Kvbotie-sU1g2xNt5vHWtc8Wq9Zb43JycOlA/edit?gid=1375268335#gid=1375268335[this doc] for the current peer review roster.
108+
109+
## Merging PRs
110+
111+
After the peer and tech reviewer approve your PR, the PR is ready for merging and cherry-picking by a gatekeeper.
21112

22-
Submit a pull request against this repo.
113+
Check link:https://docs.google.com/spreadsheets/d/1X1KHZx2Kvbotie-sU1g2xNt5vHWtc8Wq9Zb43JycOlA/edit?gid=0#gid=0[this doc] for the current gatekeeper roster.
23114

115+
## Labels
24116

25-
## Plugins Reference Guide
117+
As you work on your contribution to this repo,
118+
use labels to show the status of your PR and to request reviews:
119+
120+
* draft: `do-not-merge/work-in-progress`
121+
* ready for peer and technical reviews: `do-not-merge/review-in-progress`
122+
* request for a tech review: `technical-review-needed`
123+
* completed tech review: `technical-review-done`
124+
* request for a peer review: `peer-review-needed`
125+
* completed peer review: `peer-review-done`
126+
* ready for merging: `ready-to-merge`
127+
128+
[NOTE]
129+
====
130+
Remember to remove labels as they become outdated.
131+
For example, remove the `do-not-merge/work-in-progress` label when you finalize your draft and your PR is ready for review.
132+
====
133+
134+
## Publishing pipeline
135+
136+
This repo is the upstream mirror of the GitLab RHDH repo https://gitlab.cee.redhat.com/red-hat-developers-documentation/rhdh
137+
138+
Merged PRs are synced to GitLab for build with Pantheon.
139+
140+
## Plugins Reference Guide
26141
For Plugin configuration guide, see upstream content in https://github.com/janus-idp/backstage-plugins/tree/main/plugins
142+
143+
## Additional sources
144+
145+
* link:https://spaces.redhat.com/spaces/RHDEVDOCS/pages/467060194/RHDH+documentation+contributor+guide[RHDH documentation contributor guide]
146+
* link:https://spaces.redhat.com/spaces/RHDEVDOCS/pages/494635174/Content+creation+guidelines [RHDH content creation guidelines]
147+
* link:https://spaces.redhat.com/spaces/RHDEVDOCS/pages/580260123/GitHub+Labels+-+What+When+Who[RHDH GitHub labels]

0 commit comments

Comments
 (0)