Skip to content

📂 Pages stranded in their own folders - intentional future expansion organization? #2731

Description

@JFWooten4

In #2450 (comment), we came across a page that repeated its slug in the path, which I proposed changing to a README. Upon review, it was suggested to make the page a standalone entry without a parent folder because there were no other pages in that directory.

There are currently 51 directories with only a README in them. Does anyone need these to be folders rather than a single page in the path?

I see no obvious benefits to keeping them structured like this. And it makes it harder to incorporate page descriptions.

Footnotes

  1. The five directories are docs/data/analytics/hubble/developer-guide/connecting-to-bigquery, docs/data/apis/horizon/api-reference/resources/liquiditypools, docs/platforms/anchor-platform/sep-guide/sep1, docs/platforms/anchor-platform/sep-guide/sep10, and docs/platforms/anchor-platform/sep-guide/sep45.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions