Options for Path-Based Trailing Slash

Describe the problem

• /posts seems to represent a top-level directory for viewing all posts.
  • /posts/ would be more appropriate.
• /posts/category-a also represents a directory concept.
  • /posts/category-a/ would be more fitting.
• /posts/category-a/hello-world is a document.
  • /posts/category-a/hello-world is appropriate.

Now, let's discuss navigation formats.

• posts

  • When there is no trailing slash, use "/posts"

    • Upward Navigation
      • Absolute path: <a href="/">
      • Relative path: <a href="./"> (Is using ./ for upward navigation a bit strange?)
    • Downward Navigation
      • Absolute path: <a href="/posts/category-a">
      • Relative path: <a href="./posts/category-a"> (Does this seem a bit unusual?)

  • When using a trailing slash, use "/posts/"

    • Upward Navigation
      • Absolute path: <a href="/posts">
      • Relative path: <a href="../"> (This is the correct upward navigation concept.)
    • Downward Navigation
      • Absolute path: <a href="/posts/category-a/">
      • Relative path: <a href="./category-a/">

Going a bit deeper:

• posts/category-a
  • When there is no trailing slash, use "/posts/category-a"
    • Upward Navigation
      • Absolute path: <a href="/posts">
      • Relative path: <a href="./">
    • Downward Navigation
      • Absolute path: <a href="/posts/category-a/hello-world">
      • Relative path: <a href="./category-a/hello-world"/>
  • When using a trailing slash, use "/posts/category-a/"
    • Upward Navigation
      • Absolute path: <a href="/posts/">
      • Relative path: <a href="../">
    • Downward Navigation
      • Absolute path: <a href="/posts/category-a/hello-world">
      • Relative path: <a href="./hello-world">

When you want to control screen tree access with relative paths, routes composed of slugs might not allow for precise trailing slashes and may require using ignore (which could potentially cause issues in the future).

Describe the proposed solution

export function trailingSlash({ page }) {
  const isDirectory = isDirectory(page.url);
  // or
  // const isCategoryPage ~~
  
  return isDirectory ? 'always' : 'never';
}

Importance

would make my life easier

Start by tracing the existing trailing-slash handling and the proposed trailingSlash({ page }) entry point, including page.url and the suggested isDirectory check. Done means the issue's directory-style and document-style routes can apply different trailing-slash behavior without relying on imprecise slug-based routing.