Conversation
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
/review |
|
/review |
| @@ -0,0 +1,6 @@ | |||
| --- | |||
| build: | |||
There was a problem hiding this comment.
@aevesdocker Our create org doc has about ~330 hits per month. I'm doubting if burying it within a category is the call, even if it makes the /admin/ category more skimmable/digestable. Should I use the /setup/index.md doc as the default Create net-new org, or keep it in an empty state and have all create org actions bucketed together...
There was a problem hiding this comment.
I actually don't think it will make any difference. 330 hits isn't huge in the context of our other docs pages, plus the category you're putting it in makes sense. If you were burying it in a weird category I'd be more concerned
aevesdocker
left a comment
There was a problem hiding this comment.
I love this PR. 2 minor questions and then
🚀
| @@ -0,0 +1,6 @@ | |||
| --- | |||
| build: | |||
There was a problem hiding this comment.
I actually don't think it will make any difference. 330 hits isn't huge in the context of our other docs pages, plus the category you're putting it in makes sense. If you were burying it in a weird category I'd be more concerned
|
|
||
| To access Insights, contact your Account Executive to have the | ||
| feature turned on. Once the feature is turned on, access Insights using the | ||
| To access Insights, contact your Account Executive to turn on the feature. Once enabled, access Insights using the |
There was a problem hiding this comment.
we actually need to update this rule. this is wrong and can be ignored
PR to capture work:
Filing a follow up PR to create parallel structure in the
Companysubcategory. This PR's scope is forOrganizationonly.