Skip to content

Conversation

chrisdavidmills
Copy link
Contributor

Description

There are still several Learn articles not linked from the learnsidebar. The ones we want to keep should really be linked in some way. This PR provides an experimental suggestion of what we could do in each case — an "Additional tutorials" subsection at the end of each module sidebar subsection.

Motivation

Additional details

Related issues and pull requests

@chrisdavidmills chrisdavidmills requested a review from a team as a code owner September 18, 2025 09:42
@chrisdavidmills chrisdavidmills requested review from Josh-Cena, bsmth and pepelsbey and removed request for a team and pepelsbey September 18, 2025 09:42
@github-actions github-actions bot added the size/s [PR only] 6-50 LoC changed label Sep 18, 2025
@Josh-Cena
Copy link
Member

There isn't a chance we could just incorporate them into the normal flow instead of stashing them away? No strong opinions, this does solve the reported problem.

@chrisdavidmills
Copy link
Contributor Author

There isn't a chance we could just incorporate them into the normal flow instead of stashing them away? No strong opinions, this does solve the reported problem.

They were in the normal flow, but during my big audit and restructuring of the Learn area, these were the articles that I deemed potentially useful, but not suitable for the normal flow. CSS multi-col is not an essential layout technique that you should advise all beginners to learn, in the same way that flexbox or grid is, for example.

details: closed
children:
- /Learn_web_development/Core/CSS_layout/Multiple-column_Layout
- /Learn_web_development/Core/CSS_layout/Practical_positioning_examples
Copy link
Member

Choose a reason for hiding this comment

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

Positioning one is still okay for "normal flow", IMO. Would you consider the others "legacy" techniques instead of "additional"?

Overall, I think it's alright to have them on the same level as the other guides, but maybe down lower in the sidebar (more niche) with their status / context in the article intro.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Positioning one is still okay for "normal flow", IMO. Would you consider the others "legacy" techniques instead of "additional"?

I'm not sure what you mean by "Positioning one is still okay for "normal flow"". Can you rephrase?

They are not all legacy techniques.

Overall, I think it's alright to have them on the same level as the other guides, but maybe down lower in the sidebar (more niche) with their status / context in the article intro.

I disagree. I think having them at the same level in the nav will make people think they are part of the normal flow, and surprise them when they don't get to them via prev/next.

Copy link
Member

Choose a reason for hiding this comment

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

I disagree. I think having them at the same level in the nav will make people think they are part of the normal flow, and surprise them when they don't get to them via prev/next.

I forgot about prev/next continuity expectation -> you have the best feel for that in terms of the pathway, so deferring to you on that.

Positioning one is still okay for "normal flow" Can you rephrase?

I thought this guide has some good info, it could be useful to have it up with the others, IMO, but up to you 👍🏻

Copy link
Member

@bsmth bsmth left a comment

Choose a reason for hiding this comment

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

+1 for adding these docs into the sidebars, tnx

@Josh-Cena
Copy link
Member

Yeah also a +1 for me

@chrisdavidmills chrisdavidmills merged commit 56b4d3a into mdn:main Sep 22, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/s [PR only] 6-50 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants