Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix links #2614

Merged
merged 35 commits into from
Feb 19, 2025
Merged

Fix links #2614

merged 35 commits into from
Feb 19, 2025

Conversation

adriendupuis
Copy link
Contributor

@adriendupuis adriendupuis commented Feb 14, 2025

Question Answer
JIRA Ticket N/A
Versions master, 4.6
Edition All
  • Fix broken links.
  • Fix missing anchors.
  • Follow redirections.

Checklist

  • Text renders correctly
  • Text has been checked with vale
  • Description metadata is up to date
  • Redirects cover removed/moved pages
  • Code samples are working
  • PHP code samples have been fixed with PHP CS fixer
  • Added link to this PR in relevant JIRA ticket or code PR

"This document has been superseded."
Browser add-ons links are dead.
Not really safe to recommend tools we don't monitor.
Section renamed in #2422 with content not changed.
formatting_date_and_time.md: section was renamed in #2506
@adriendupuis adriendupuis marked this pull request as ready for review February 17, 2025 08:36
@@ -936,7 +936,7 @@ extra:
latest_tag_4_5: '4.5.7'
latest_tag_4_6: '4.6.16'

symfony_doc: 'https://symfony.com/doc/5.4'
symfony_doc: 'https://symfony.com/doc/5.x'
user_doc: 'https://doc.ibexa.co/projects/userguide/en/master'
Copy link
Contributor Author

@adriendupuis adriendupuis Feb 17, 2025

Choose a reason for hiding this comment

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

Side note: since master is hidden, maybe we should make this change:

Suggested change
user_doc: 'https://doc.ibexa.co/projects/userguide/en/master'
user_doc: 'https://doc.ibexa.co/projects/userguide/en/latest'

Copy link
Contributor

Choose a reason for hiding this comment

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

Definitely, nice catch!

Copy link
Contributor

@mnocon mnocon Feb 17, 2025

Choose a reason for hiding this comment

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

Or maybe it should be set per branch?
user_doc: 'https://doc.ibexa.co/projects/userguide/en/4.6' for 4.6
user_doc: 'https://doc.ibexa.co/projects/userguide/en/3.3' for 3.3

This way the links are compatible between versions

Copy link
Contributor

@dabrt dabrt Feb 17, 2025

Choose a reason for hiding this comment

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

We could... but then we'd have to change all links when bumping version and remember about changing them when cherrypicking changes to older branches

Copy link
Contributor

@mnocon mnocon Feb 17, 2025

Choose a reason for hiding this comment

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

We wouldn't have to do this - we could just use the variable, as we currently do.

The value of the variable would change between branches, but the syntax wouldn't.

This example:

[I'm a link]([[= user_doc =]]/personalization/personalization/)

would link to:

So, no changing links when creating the 5.0 branch (and no changes when cherry-picking), we would only make one single change in mkdocs.yaml when creating the 5.0 branch - and the links would become "version-aware"

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm suggesting we do the same thing we already do for the Symfony doc:

which is not causing any issues currently

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mnocon @dabrt I propose to not make decision about this in this PR. Let dev's master targets user's master for now. I'll test and we'll discuss latter what 4.6 targeting 4.6 and 3.3 targeting 3.3 imply.

@adriendupuis adriendupuis requested review from mnocon and dabrt February 17, 2025 16:28
This was referenced Feb 17, 2025
Copy link
Contributor

@mnocon mnocon left a comment

Choose a reason for hiding this comment

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

Thank you!

@adriendupuis adriendupuis merged commit 826c6f7 into master Feb 19, 2025
6 of 7 checks passed
@adriendupuis adriendupuis deleted the fix-links branch February 19, 2025 13:08
adriendupuis added a commit that referenced this pull request Feb 19, 2025
(cherry picked from commit 826c6f7)
@adriendupuis adriendupuis mentioned this pull request Feb 20, 2025
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants