Skip to content

docs: move docs to canonical.com/juju/docs/ops#2545

Open
dwilding wants to merge 6 commits into
mainfrom
dotcom-migration
Open

docs: move docs to canonical.com/juju/docs/ops#2545
dwilding wants to merge 6 commits into
mainfrom
dotcom-migration

Conversation

@dwilding

@dwilding dwilding commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

This PR updates our doc config so that all URLs use canonical.com/juju/docs/ops instead of the backend URL from Read the Docs. Our docs are still hosted on Read the Docs, but we'll be proxying them under canonical.com/juju/docs.

Preview docs built from this branch. After this PR merges, I'll switch those docs to build from main and redirect the existing docs.

Main changes

  • Updated Ops doc URLs in docs/conf.py.
  • Updated hardcoded URLs for Ops, excluding CHANGES.md.
  • Added a script docs/_static/overwrite_links.js. This script makes sure that the version switcher from Read the Docs has correct URLs. It's a standard part of the new docs setup at Canonical.

Extra changes

  • Updated the intersphinx URL and hardcoded URLs for Jubilant. To account for jubilant#337.
  • Updated the intersphinx URL and hardcoded URLs for Charmlibs. To account for charmlibs#515
  • Updated the intersphinx URL and hardcoded URLs for Pebble. To account for pebble#882.

Future work (not in this PR)

  • Update URLs for other docs - Juju, Charmcraft, ...
  • Update URLs in comments in the Charmcraft profiles. This PR updates the affected comments in our example charms, bringing them ahead of the latest Charmcraft profiles. I think that's acceptable to reduce busywork later.

@tromai tromai 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.

Thank you for this change.

I saw in the PR description the link to the Preview docs is https://canonical.com/juju/docs/ops/latest/. Does this mean we have publish the docs built from this branch to the new home? Ah nevermind, I saw you mentioned switching back to main after this PR is merged.

@@ -0,0 +1,28 @@
// Our docs are proxied through to canonical.com/juju/docs/ops.

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.

Should we have a copyright notice for this file?

@tromai tromai Jun 18, 2026

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.

As this script is a new Canonical docs standard, I assume that it has been battle-tested upstream. But please let me know if I need to have a closer look 😄.

I had a scan through and it looks good to me.

Comment thread ops/_private/harness.py
warnings.warn(
'Harness is deprecated. For the recommended approach, see: '
'https://documentation.ubuntu.com/ops/latest/howto/write-unit-tests-for-a-charm/',
'https://canonical.com/juju/docs/opslatest/howto/write-unit-tests-for-a-charm/',

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.

Suggested change
'https://canonical.com/juju/docs/opslatest/howto/write-unit-tests-for-a-charm/',
'https://canonical.com/juju/docs/ops/latest/howto/write-unit-tests-for-a-charm/',

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.

2 participants