Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IA Research] Determine directory structure for content #11

Closed
2 tasks
caylahamann opened this issue Aug 14, 2020 · 1 comment
Closed
2 tasks

[IA Research] Determine directory structure for content #11

caylahamann opened this issue Aug 14, 2020 · 1 comment

Comments

@caylahamann
Copy link
Contributor

caylahamann commented Aug 14, 2020

Summary

There are over 5,000 markdown files that will be in the documentation site. We need to figure out a way to structure this content in our repository.

Procedure

Open up a PR merging into research. If there is no changes in the code (and only research details), you can just make an edit in a text file, since there is no plan to merge this into main. Use the PR template research_PR_template.md either by coping the markdown into the PR or by appending the query string ?template=research_PR_template.md to the URL. Fill out the template by answering the research questions listed below.

Research Goals

  • Determine a file structure for content (is it determined by folder, by frontmatter ect.)
  • Discuss solutions with engineers, content creators and PMs to determine best path forward
@caylahamann caylahamann added enhancement New feature or request research and removed enhancement New feature or request labels Aug 14, 2020
@caylahamann caylahamann added this to the MMF 1 - Set Up & Research milestone Aug 14, 2020
@zstix zstix added the sp:5 label Aug 18, 2020
@zstix zstix added this to To do in Developer Experience Aug 18, 2020
@caylahamann caylahamann moved this from To do to In progress in Developer Enablement Team Aug 24, 2020
@caylahamann caylahamann moved this from In progress to In review in Developer Enablement Team Aug 24, 2020
@zstix zstix self-assigned this Sep 1, 2020
@zstix
Copy link
Contributor

zstix commented Sep 1, 2020

We spoke with some stakeholders and evaluated a few options. We have decided that we do not want to store all markdown files within a single directory. We would like to either make a fully-nested structure that mimics the category hierarchy or make a single-level structure where we have top-level category buckets.

Moving forward, we are going to try to migrate some content with one of these strategies and re-evaluate. I'm going to move this ticket to the next MMF, since that is when we will do that evaluation.

Meeting Notes

  • Use a nested hierarchy to store the files, with the hierarchy reflecting where a doc actually lives (for example, a doc at the first level would live in /Folder-A , while a doc at the second level would live at Folder-A/Folder-B . And so on.
  • We want the URL structure, the public-facing navigation, and the repo structure to all align.
  • We'll re-check this decision a bit later on when we do a simple test migration with doc/navigation titles that match the actual site.
  • Putting a doc in multiple places in the hierarchy is a technical puzzle we'll need to solve for.
  • We'd also like to explore automation/tooling to ensure that the directory, URL, and navigation stay aligned and don't drift

@zstix zstix moved this from In review to Proposed in Developer Enablement Team Sep 1, 2020
@jerelmiller jerelmiller moved this from Proposed to To do in Developer Enablement Team Sep 3, 2020
@jerelmiller jerelmiller moved this from To do to Proposed in Developer Enablement Team Sep 3, 2020
@jerelmiller jerelmiller moved this from Proposed to To do in Developer Enablement Team Sep 3, 2020
@jerelmiller jerelmiller added sp:1 and removed sp:5 labels Sep 3, 2020
@zstix zstix closed this as completed Sep 18, 2020
Developer Enablement Team automation moved this from To do to Done Sep 18, 2020
mfulb pushed a commit to mfulb/docs-website that referenced this issue Sep 21, 2022
rhetoric101 pushed a commit that referenced this issue Jan 10, 2024
chore: Update docs to include link to wiki
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants