Skip to content

docs: stop styling page references as blockquotes - #2666

Merged
tonyandrewmeyer merged 6 commits into
canonical:mainfrom
tonyandrewmeyer:rainy/2643-drop-blockquotes-for-links
Aug 20, 2026
Merged

docs: stop styling page references as blockquotes#2666
tonyandrewmeyer merged 6 commits into
canonical:mainfrom
tonyandrewmeyer:rainy/2643-drop-blockquotes-for-links

Conversation

@tonyandrewmeyer

@tonyandrewmeyer tonyandrewmeyer commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Replaces the > See also: / > See more: / > See first: blockquotes throughout docs/ with plain body text.

Also converts the eight > Examples: blocks, which point at charm source and are quote-styled for the same historical reason.

Two related things left alone, each worth a separate decision:

  • The tutorial's breadcrumb and > **See previous:** / > **See next:** blockquotes. Those are navigation rather than references, and the tutorial is being worked on separately at the moment.
  • The two > Added in ops 2.15 / > Added in ops 2.17 version notes in manage-pebble-health-checks.md.

Fixes #2643

tonyandrewmeyer and others added 3 commits July 13, 2026 15:14
…outs

Un-blockquote 'See more:', 'See also:', 'See first:', and 'Read more:'
callouts across docs/howto, docs/explanation, and one tutorial page.
References to other pages aren't quotes, so shouldn't be styled as
quotes (per canonical/charmlibs#493).
charmlibs#493, which the issue cites, sets the rule: two items comma
separated, three or more bulleted. Eight converted lines had three or more
items but stayed on one line, including a five-item ops.ActionEvent list.

Also converts the eight "> Examples:" blockquotes, which are references to
charm source styled as quotes for the same historical reason. The tutorial's
breadcrumb and "See previous"/"See next" blockquotes are navigation rather
than references, and are left alone.
Vale skips blockquote contents, so unquoting these lines is what exposed
"Charmlibs" and "timeframes" -- both were already in the docs.

"Charmlibs" is a product name, so it goes in the custom wordlist alongside
Jubilant's and Borescope. "timeframes" is reworded to "time frames", which is
the form the US spellcheck accepts.

@james-garner-canonical james-garner-canonical left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This looks good to me.

@dwilding dwilding left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for doing this!

Elsewhere we've discussed adopting this style: If there are 2 links, write them inline. If there are 3+ links, use bullets.

I asked my agent to scan the docs and it found 13 instances to change.

Files with an instance of 2 bullets:

  • docs/explanation/security.md
  • docs/howto/debug-your-charm.md
  • docs/howto/make-your-charm-discoverable.md
  • docs/howto/manage-interfaces.md
  • docs/howto/write-integration-tests-for-a-charm.md
  • docs/howto/write-unit-tests-for-a-charm.md

Files with an instance of 1 bullet:

  • docs/howto/manage-charms.md
  • docs/howto/write-integration-tests-for-a-charm.md

I think it's worth changing these instances to inline style. I'd be OK if you do that on this PR. Or I'd be happy to open a separate PR.

Comment thread docs/explanation/versions.md Outdated
tonyandrewmeyer and others added 3 commits August 20, 2026 20:15
Review feedback: the Juju cross-reference still read "Juju support
timeframes", while the Ops one had been reworded to "time frames" to get
past the US spellcheck. "Support commitments" describes both better and
is spelled the same way everywhere.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The same rule that bulleted the three-or-more-item lists puts one and two
items back on a single comma-separated line, which is what the rest of
the docs already do. Eleven blocks across six files.

Two are left as bullets: the lists in debug-your-charm.md and
manage-interfaces.md carry a descriptive clause on each item, so joining
them with commas would run those clauses together.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ckquotes-for-links

# Conflicts:
#	docs/explanation/versions.md
@tonyandrewmeyer

Copy link
Copy Markdown
Collaborator Author

I think it's worth changing these instances to inline style. I'd be OK if you do that on this PR. Or I'd be happy to open a separate PR.

Done in this one.

@tonyandrewmeyer

Copy link
Copy Markdown
Collaborator Author

@dwilding do you want to look over the new changes?

@dwilding dwilding left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Changes look good. I agree with leaving a couple of 2-bullet blocks because the bullets have longer explanations.

@tonyandrewmeyer
tonyandrewmeyer merged commit 0695bd5 into canonical:main Aug 20, 2026
60 checks passed
@tonyandrewmeyer
tonyandrewmeyer deleted the rainy/2643-drop-blockquotes-for-links branch August 20, 2026 22:07
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.

Stop using blockquotes for "see more" blocks

3 participants