Skip to content

Conversation

@aimeeu
Copy link

@aimeeu aimeeu commented Oct 15, 2025

Jira: CE-1062

I copied content from Confluence wikis TW content types, web-unified-docs reference, How to contribute to Vault docs and sidebar explanation from nomad/website/README.

  • Add tech writer processes.
  • Add generic contributor guide.
  • Add notice to top of repo README. This directors contributors to the new contributor guide. Remove docs contrib section from README. Andy Schlossberg and DevDot team agreed to this approach.

Previews:

@aimeeu aimeeu requested review from a team as code owners October 15, 2025 13:14
@aimeeu aimeeu marked this pull request as draft October 15, 2025 13:14
@github-actions
Copy link
Contributor

github-actions bot commented Oct 15, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal 🔄 Building (Inspect) --- ---
Unified Docs API ✅ Ready (Inspect) Visit Preview Tue Nov 4 15:54:18 UTC 2025

@aimeeu aimeeu requested a review from boruszak October 16, 2025 15:16
Copy link
Contributor

@boruszak boruszak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This review was me going through this PR at a high level and leaving some initial notes that are as much for me as they are for you. I'm going to checkout the branch and make some commits directly, per your suggestion, to speed up the process.


### Workflows

@TODO use which presentation??
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

List, but get rid of the sentence after the colon, and make each item a link to the workflow.

---
```

This repository's content guide includes detailed instructions on how to [create a new page and add it to the navigation sidebar](/content--guide/create-new-page).
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This repository's content guide includes detailed instructions on how to [create a new page and add it to the navigation sidebar](/content--guide/create-new-page).
This repository's content guide includes detailed instructions on how to [create a new page and add it to the navigation sidebar](/content-guide/create-new-page).

fix link


In our documentation, you can use custom markdown enhancements to produce pages with tabs, named code blocks, badges, and alert boxes.

Correct usage of these enhancements is documented in this repo's [content style guide](/style-guide). The custom components and additional configuration options are avaialble using the `dev-portal` repo.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Correct usage of these enhancements is documented in this repo's [content style guide](/style-guide). The custom components and additional configuration options are avaialble using the `dev-portal` repo.
Correct usage of these enhancements is documented in this repo's [content style guide](/style-guide).

Suggest removing "The custom...." sentence. Content contributors don't need to know the DevDot underlying architecture in order to use the custom components, and this sentence makes me think I might have to do something with the dev-portal project in order to use custom components.


## Navigation sidebars

The structure of the sidebars are controlled by files in the `./content/<product>/<version>/<data>` directory. Each file contains a configuration for a section of product documentation. For example, `docs-nav-data.json` controls navigation in the product's `Documentation` section on developer.hashicorp.com.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The structure of the sidebars are controlled by files in the `./content/<product>/<version>/<data>` directory. Each file contains a configuration for a section of product documentation. For example, `docs-nav-data.json` controls navigation in the product's `Documentation` section on developer.hashicorp.com.
The structure of the sidebars is controlled by files in the `./content/<product>/<version>/<data>` directory. Each file contains a configuration for a section of product documentation. For example, `docs-nav-data.json` controls navigation in the product's `Documentation` section on developer.hashicorp.com.


Correct usage of these enhancements is documented in this repo's [content style guide](/style-guide). The custom components and additional configuration options are avaialble using the `dev-portal` repo.

## Navigation sidebars
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to duplicate this here when it's in the create-new-page file? Probably safe to say that the majority of contributors aren't going to be modifying the sidebar files. Potentially less confusing to keep all the sidebar content with the create new page content.

- An `index.mdx` file is not required for each subdirectory.
- If you use `index.mdx` files: you must add the file to the navigation `.json`, but the `.json` file can resolve it from the name of the directory. In the example, notice that it uses the `directory` path rather than `directory/index`. A common convention is to set the `title` of an index node to be `"Overview"`.

### Custom or external links
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest moving this section to create-new-page file.


## Redirects

Detailed guidance on redirects and formatting is available in the [content guide](/content-guide/redirects).
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Detailed guidance on redirects and formatting is available in the [content guide](/content-guide/redirects).
Find detailed guidance on redirects and formatting in the [content guide](/content-guide/redirects).

active voice

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants