-
Notifications
You must be signed in to change notification settings - Fork 837
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
☂️ Restructure our docs #13434
☂️ Restructure our docs #13434
Comments
The new docs look way cleaner. 🚀 |
Good time to migrate docs link checker to https://github.com/UmbrellaDocs/action-linkspector |
Added validated architectures @ericpaulsen https://coder.com/docs/@restructure/admin/infrastructure/validated-architectures |
@stirby what is your rationale about "screenshots" being in getting started? I added it there, but I figured that section would be tutorial oriented. Overall, I'm a bit confused on the difference between about and getting started sections |
In my eyes, "Getting Started" should be day-zero setup process for those already interested in the product. "About" should be seen by anyone exploring the product, regardless of setup interest. I put it under "Getting Started" since I see myself "touring" the product by looking around the UI, then setting it up. I assume you'd suggest moving it under "About?" I agree it conceptually fits but I wanted to avoid a subsection there. |
Nevermind, open to moving screenshots under about. We could also add a changelog or similarly high-level docs under there later. |
I'm kind of stuck on where to put |
I would go with infrastructure but will link from groups as it's more useable with groups/teams managing their own compute resources. |
Seems like we may need a
Not sure what the README would look like, maybe talking about scope? Not a concrete decision, just something to investigate. |
We may also document the secret management methods we support at https://coder.com/docs/secrets. |
@matifali good call! I think these belong in "integrations" but we should link to them in the secrets doc as children. |
This is now complete. I added this under integrations and linked from |
Atif Tasks
Stephen Tasks
|
Tasks Atif
Stephen
|
Steve's task for 09/11 -> 09/14
|
Completed Tasks
Changes to main
Stephen Tasks
Edward / Atif:
|
We're waiting to return the enterprise feature comparison until we add the coderd licensing options. Then we'll have a "Licensing" section under administration.
|
I'll do the licensing stuff this week. What is an ETA looking like, including us adding redirects? |
Adding redirects requires fixing all dead links and stale images and checking for missing docs. If we can get these completed by end of the week we can add redirects and merge. |
Added this checkbox to the tracker above:
|
We're working on a new information hierarchy for coder.com/docs with a few goals in mind:
You can see our progress in the restructure-new branch or even on our docs site: https://coder.com/docs/@restructure-new
Coder.com Changes Required
og:image
for each pageDocs
Post-installation steps(part of control plane configuration)Reverse proxy (Setup SSL certs)Docker socket permission (explain for k8s, docker-compose and system-service) installationsadmin/auth
page)[x] Check if feat: create a token for another user via cli #13424 is merged & adjustenvbuilder
)coder-logstream-kube
Waiting until merge to add more performance benchmarking, blog post mention is sufficient
guides/
Add VM support foroffline
docs or mention that the guide is K8s onlyChores
make gen
writes to the new docs locationsTODO
sSwitch link checker to https://github.com/UmbrellaDocs/action-linkspectorReleases calendarThe text was updated successfully, but these errors were encountered: