-
Notifications
You must be signed in to change notification settings - Fork 277
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
Improve Terraform Registry Documentation #1233
Comments
Hi @publi0! I think this is a great idea! We'd be very happy to accept a PR adding this. Let us know if you have any questions around categorization. |
@andrewsomething I didn't find any Makefile or script referencing the Terraform plugin for generating documentation. Do you use the plugin, or do you build the documentation manually? If it's the latter, a script for automatically adjusting the subcategories wouldn't be necessary |
+1 for following the control panel's categorization.
Currently we are creating the documentation manually. |
@publi0 This is now live with the latest release! Thanks again for the great contribution! https://registry.terraform.io/providers/digitalocean/digitalocean/latest/docs |
Enhance DigitalOcean Terraform Provider Documentation with Subcategories
Current Situation
The current Terraform Registry documentation for the DigitalOcean provider lacks organization, making it difficult to navigate and find specific resources or data sources.
All resources (including databases) are grouped together, which:
Proposed Improvement
Implement subcategories in the resources documentation markdown file to improve organization and readability.
Benefits:
Implementation Challenges
The current Terraform documentation plugin doesn't have a built-in option to define subcategories, requiring manual definition in the markdown files.
Proposed Solution
Create a script to automatically adjust the markdown files and add the necessary subcategory definitions.
If this idea is approved, I volunteer to implement the solution :)
The text was updated successfully, but these errors were encountered: