hlxsites / hlxsites/prisma-cloud-docs-website
[AsciiDoc conversion] Admonitions (notes) in list items not rendered properly
- Dominant language
- CSS
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Admonitions (notes) in procedure steps (list items) are being rendered as paras, not admonitions
See this page on Franklin (search for "The process of submitting a PR to fix the issue directly"):
https://main--prisma-cloud-docs-website--hlxsites.hlx.page/en/enterprise-edition/content-collections/alerts/view-respond-to-prisma-cloud-alerts?branch=fix-in-code
Adoc source:
https://github.com/hlxsites/prisma-cloud-docs/blob/a3c2e711b2a004bda2e12d5f9b535657c8ab42dc/docs/en/enterprise-edition/content-collections/alerts/view-respond-to-prisma-cloud-alerts.adoc?plain=1#L164-L173
```
.. Fix the problem.
* Use *Send To Jira* to file a ticket for the application team, if you do not have the authority to fix the issue.
* Use *Fix in Cloud* to prevent an incident from occurring in runtime. Prisma Cloud can automatically execute the CLI command provided in the policy recommendations to resolve the misconfiguration.
* Use *Fix in Code* if you have access to the IaC resource and can submit a PR to the Version Control System.
+
When the issue is addressed, the alert is moved to a Pending Resolution or Resolved state, and the risk is addressed.
+
NOTE: The process of submitting a PR to fix the issue directly in code is an offline process. When the process completes and the PR is submitted, the button will update to *View Details* and you can access the link to view the PR in your VCS.
```
Notes should be rendered like this:
Contributor guide
Research direction
Start with the linked .adoc source, especially lines 164–173, and compare it with the rendered Franklin page at the reported location. Trace how list continuations and the NOTE block are handled during conversion. Done means the note in the procedure step renders as an admonition rather than a paragraph.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100