Skip to content

Year specific dedicated files organizational system #3249

Description

@Ruthie-FRC

I have noticed that there are some files/pages in the docs that are only relevant to one game in a previous year. I propose that there should be a subsect of the docs called "archive" or "legacy", where the field could be moved into. for example, source/docs/yearly-overview/images/2020-Game-Data/labview-game-data-code.png could be instead moved into another root level folder but have everything else untouched, becoming archive/docs/yearly-overview/images/2020-Game-Data/labview-game-data-code.png or legacy/docs/yearly-overview/images/2020-Game-Data/labview-game-data-code.png. alternatively, the repo level archive/legacy folder could have subfolders organized by years, and within those subfolders resources could be broken down by type. just an idea.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions