Skip to content

feat(docs): added links to github changelog to migration page headers#3604

Open
duvalale wants to merge 7 commits into
ouds/mainfrom
ouds/main-ad-links-to-guithub-changelog
Open

feat(docs): added links to github changelog to migration page headers#3604
duvalale wants to merge 7 commits into
ouds/mainfrom
ouds/main-ad-links-to-guithub-changelog

Conversation

@duvalale

@duvalale duvalale commented Jun 12, 2026

Copy link
Copy Markdown
Member

Related issues

Closes #3457

Description

Updated migration page headers to add link redirecting to matching changelog.
I chose not to add the v0.2.0 link since there is no changelog nor release associated.

Checklists

Progression (for Core Team only)

Live previews

@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for boosted ready!

Name Link
🔨 Latest commit fcec38d
🔍 Latest deploy log https://app.netlify.com/projects/boosted/deploys/6a3e7949c3bad20008ab9020
😎 Deploy Preview https://deploy-preview-3604--boosted.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@MaxLardenois MaxLardenois left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think it'd be better if the changelog link was on a dedicated link or button below the title (or on its right for wider viewports)
Here the link is not easily visible and it lacks an accessible text.

@boosted-bot boosted-bot moved this from Need Dev Review to Dev Review In Progress in 🟣 [Orange-Boosted-Bootstrap] PRs Board Jun 15, 2026
@duvalale duvalale force-pushed the ouds/main-ad-links-to-guithub-changelog branch from 1c99711 to 0563034 Compare June 19, 2026 12:34
@duvalale

Copy link
Copy Markdown
Member Author

I updated the headers to add a dedicated link.
I had to use a remark and rehype plugins to be able to add the link and position it correctly in the DOM for keyboard navigation, otherwise, the focus order would have been incorrect (anchor-link focused after changelog link).

@MaxLardenois MaxLardenois left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Nice work!
I have some suggestion but nothing blocking so I will approve

Comment thread site/src/libs/utils.ts Outdated
}

export function getVersionLink(version: string): string {
return `<a class="link float-end pt-none align-content-center" href="https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/releases/tag/${version}-ouds-web">Full changelog</a>`

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I would use p-none here to improve alignment.

Also I think we could use a Link with icon (https://web.unified-design-system.orange.com/orange/docs/1.3/components/links/#with-icon) with the "external link" icon from Solaris (https://unified-design-system.orange.com/472794e18/p/03a2da-solaris-icon-finder) to make it clear it's another website (with a target=_blank maybe)

I don't know what will be the result in the TOC though...

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I noticed that version link is not vertically aligned to the heading when using p-none. Only pt-none allows it to be centered.

I added the external link icon.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I feel it's better if it's somewhat bottom aligned as it's inly text but I will let others give their opinion

Comment thread site/src/libs/remark.ts Outdated
// [[comp]]
const compRegExp = /\[\[comp\]\]\s*/
// [[version-link]]
const versionLinkRegExp = /\[\[version-link\]\]\s*/

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'm wondering if we shouldn't use [version-changelog-link] to be more precise

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Done

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Updated to suggested value

Comment thread site/src/libs/rehype.ts Outdated
}

// A rehype plugin to reorder header anchor and version links
export const rehypeHeaderLinksOrder: Plugin<[], Root> = function () {

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Maybe we could simplify this by using the option before on rehypeAutolinkHeadings
This way the anchor-link would always be first (before the actual heading text), this would be that less to do.
But it works as is, just an idea.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I tried to keep the existing headers as is on purpose, but it is indeed simpler to move the anchor-link before the actual heading.
I removed the rehypeHeaderLinksOrder and updated the autolink conf.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I kept the existing header as is on purpose, but if I am allowed to update it, it is indeed better to prepend the anchor link.
It's done, and the rehypeHeaderLinksOrder is removed.

@MaxLardenois MaxLardenois Jun 26, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Sorry I was not clear: we should keep the end result as is (anchor-link after the heading text). But for this script I think it might be helpful if the anchor-link were always first, so that you only need to spilt the heading elements and reorder everytime, no need to find the anchor-link

@duvalale duvalale force-pushed the ouds/main-ad-links-to-guithub-changelog branch from d214b9e to 3a38f39 Compare June 25, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Dev Review In Progress

Development

Successfully merging this pull request may close these issues.

3 participants