Skip to content

Use distinct URLs for tabs and pagination [RFC] #691

@cirosantilli

Description

@cirosantilli

🚀 feature request

Relevant scope

What is the scope of this request?

  • Frontend specs
  • Backend specs
  • Other... Please describe:

Description

A clear and concise description of the problem or missing capability...

Currently, the following all fall under the same root URL / for example:

  • "Your Feed" vs "Global Feed" tabs
  • Filter by tag
  • Pagination of the above as you go to the next pages

This would be very bad in a real website however because:

  • it likely prevents full crawling of all articles from such indices. The crawler likely sees href="/" and thinks: done that already
  • it's just annoying for users, as it produces pages that you just can't link to, e.g. the global article list page is unlikable to a logged in user

Another disadvantage is that this makes it impossible to have a compliant frontendless implementation that just renders everything on the server like the good old days.

Maybe there is a use case for content transitions without URL changes, and it would be good to demonstrate it if so, but these are not it.

It is worth noting however that there is a case where tabs have distinct URLs:

Describe the solution you'd like

If you have a solution in mind, please describe it.

Maybe:

  • Your Feed: /(unchanged)
  • Global Feed: /all. Also still visible under / to the logged out user.
  • Tags: /tag/[tag]
  • Pagination: /?page=2, /all?page=2, /tag/mytag?page=2

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions