Follow-up from "Update Navigation docs to say don't replace parent nav items"
The following discussion from !2504 (merged) should be addressed:
-
@rayana started a discussion: (+6 comments) Rayana Verissimo
@mle @mvanremmerden Nit-pick: why are we calling it
nav
andnavigation
? Is there any different about those terms? If they are essentially the same, I'd suggest we keep the language consistent in the documentation. If there's a difference (navigation being the concept, and nav being the clickable menu item), I'd suggest we clarify that language with a disclaimer before using the term.Michael Le
@rayana @mvanremmerden I am using the word
nav
here because that was the current language used in Pajamas.In the last few months I haven't heard/called these elements as
product landing pages
orsub nav group
. Instead I have been calling the first level itemsparent menu items
and thesub-menu items
orsub menu items
.I am happy to update this language as part of the merge request as well.
Rayana Verissimo
parent menu items and the sub-menu items or sub menu items.
This terminology makes more sense to me - it is less abstract than
nav
. I’d consider following up with an update it to something more accessible such as parent/child items. Cc @tauriedavisFor reference, we use the trunk, branch, leaf terminology for the Tree component, but there’s an explanation about that structure in the docs.
Taurie Davis
I agree with using
parent menu items
and thesub-menu items
orsub menu items
. I find product landing page confusing terminology because I expect some sort of overview landing page. I believe this is something being used by the Growth team so @jackib might have more insight if I remember correctly.Jacki Bauer
@tauriedavis I think we should have the friendliest possible name for so-called landing pages. I don't like things like "parent menu items" etc.
We have pages that summarize a product area with aggregation of data and things to pay attention to.
We will have a page/s that summarize the devops platform with aggregation of data and things to pay attention to.
@mle What's a straight forward name? I've heard home page for the latter. Section pages maybe for a top-level nav item?
Marcel van Remmerden
@jackib In an ideal scenario in the future they might indeed be section pages, but often times that's not the case with our current Information Architecture. As an example, the page that opens when you click on "Deployments" is "Feature flags", which is not a section page but one of three different areas under Deployments (Feature Flags, Environments, Releases) that are all on the same level, which makes it a bit tougher.
Rayana Verissimo
I find product landing page confusing terminology because I expect some sort of overview landing page.
Same, @tauriedavis @mvanremmerden. @jackib For views such as milestones, operations, environments, or the dashboards that don't aggregate sub-areas, the "landing page" construct makes sense, but we generally don't direct users to section pages (as stated by Marcel in the comment above).
I'll open a follow up issue so we keep the scope of this MR succinct. AKA Disagree, commit, and disagree.