Skip to content

Conversation

nginx-jack
Copy link
Collaborator

@nginx-jack nginx-jack commented Aug 20, 2025

Adds basic card with title and description, for index pages with no custom content.
In most cases, the only way to get these pages on mainframe is by clicking on the breadcrumb.
There are some links still going to these pages, so it's safer to having something nicer until we can remove them completely.
Screenshot 2025-08-20 at 14 06 45

@nginx-jack nginx-jack requested a review from a team as a code owner August 20, 2025 10:45
Copy link

Deploy Preview will be available once build job completes!

Name Link
😎 Deploy Preview https://frontdoor-test-docs.nginx.com/previews/nginx-hugo-theme/353/

@ADubhlaoich
Copy link
Contributor

I wouldn't call these landing pages, 'cause that's interchangeably confusing with actual landing pages at the top of the documentation sets, for which there is a discrete Hugo template and archetype.

This is an index page. All landing pages are indexes, but this could be more precisely described as a nested index page.

Both are examples of transition pages in information architecture taxonomy.

@nginx-jack
Copy link
Collaborator Author

I wouldn't call these landing pages, 'cause that's interchangeably confusing with actual landing pages at the top of the documentation sets, for which there is a discrete Hugo template and archetype.

This is an index page. All landing pages are indexes, but this could be more precisely described as a nested index page.

Both are examples of transition pages in information architecture taxonomy.

Makes sense! I'll update the comment in the code, and describe as an index page.

@danielledeleo
Copy link
Contributor

I agree with Alan that they should be distinct from the customized landing pages. Let’s add a subheading to index pages that says something like: “In this section” to gently suggest that it’s autogenerated.

I also think we should stack the cards vertically. So that we don’t get mismatched white space across rows. Keep them half-width though.

Do the contribution links at the bottom of the page always lead somewhere useful on autogenerated landing pages? And no Qualtrics on this page right?

@nginx-jack
Copy link
Collaborator Author

nginx-jack commented Aug 20, 2025

I agree with Alan that they should be distinct from the customized landing pages. Let’s add a subheading to index pages that says something like: “In this section” to gently suggest that it’s autogenerated.

I also think we should stack the cards vertically. So that we don’t get mismatched white space across rows. Keep them half-width though.

Do the contribution links at the bottom of the page always lead somewhere useful on autogenerated landing pages?
And no Qualtrics on this page right?

Will make those changes - the contribution links will lead to the _index.md file of that section. So if they want to customise the section, it's exactly where they'd want to go 👍 . *and I'll make sure qualtrics isn't here

@nginx-jack nginx-jack force-pushed the default-landing-pages branch from ab1c16d to d816328 Compare August 20, 2025 13:07
@nginx-jack nginx-jack changed the title Default landing page Default index pages Aug 20, 2025
Copy link
Contributor

@danielledeleo danielledeleo left a comment

Choose a reason for hiding this comment

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

w

@nginx-jack nginx-jack merged commit 8958fce into mainframe Aug 20, 2025
4 checks passed
@nginx-jack nginx-jack deleted the default-landing-pages branch August 20, 2025 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants