site: improve page organization / add a browseable sitemap

Description

Split from

  • do we want a browseable site map?

:

I was thinking that we could have One page which was both the site map +
gave us control over which things were parents of which other things and
what the order of the children was. We can ensure with a test that the List
is complete. And that makes it really easy to move pages around: change
parents, change order, etc

A generated (browseable) site map would let us see what the page hierarchy is.

I’m concerned that a manually edited single page that lists all pages would make it painful to update the site.

Step 3:

  • Add some data so that we can control the sitemap structure: that is, the children of each parent, and exactly what their order should be when listed.

    • Why? The folder structure is in many cases very weird and accidental. (the fake /index/ level, etc.) Yet we don’t want to change the ULS to get to pages, because that would invalidate old links. Moreover, we must to be able to control the order of the children of a given parent anyway.

    • We’d have to explore how we encapsulate this data. Could just be an index .md file with different levels of bullets. That would be easy to see the overall structure, and have a test that it contains all the .md files. It could also serve as a global sitemap.

Step 4

Consider designs for a UI to show sibling pages

  1. Some thoughts on these are in

Attachments

2

is blocked by

Activity

Steven R. Loomis September 11, 2024 at 10:22 PM

Ok, I’ve generated the .tsv as an output, preparing to use it as an input.

Format here (root index for consistency)

Annemarie Apple 🍎 September 11, 2024 at 2:21 AM

Either looks fine to me.

Mark Davis September 11, 2024 at 12:01 AM

We should never skip levels anyway!

Mark Davis September 10, 2024 at 11:59 PM

It is unnecessary if it is always there.

Steven R. Loomis September 10, 2024 at 11:02 PM
Edited

ok- do you prefer not to have the leading slash then in the paths? I think TSV might be better, markdown has rules about jumping levels. “TOP” would be just index I think, since the index page is index.md

Fixed

Details

Priority

Assignee

Reporter

Reviewer

Fix versions

Components

Created September 9, 2024 at 9:49 PM
Updated October 6, 2024 at 3:21 PM
Resolved October 6, 2024 at 3:21 PM