Large docs update #346
Large docs update #346
Conversation
* First pass of docs editing * More edits
… into docs/refactor
alishamayor
requested review from
arctan5x,
hendolim,
jmeixensperger,
jonathan-vega-splunk,
jrigassio-splunk,
lephino and
nwang92
as code owners
[skip ci]
alishamayor
force-pushed
the
docs/refactor
branch
from
6cd1afc to
ff26156
Compare
| For more instructions on how to bring your own certificates, please see: https://docs.splunk.com/Documentation/Splunk/latest/Security/ConfigureSplunkforwardingtousesignedcertificates | ||
| Fore further instructions, see [Configure Splunk forwarding to use your own certificates](https://docs.splunk.com/Documentation/Splunk/latest/Security/ConfigureSplunkforwardingtousesignedcertificates). | ||
|
|
||
| ## Build from source |
There was a problem hiding this comment.
I'm wondering if we should move this to CONTRIBUTING.md? I think we might want to tailor this ADVANCED.md section to outline/detail individual features of the Docker image and how it can be used by the end user.
Building images is more of a developer workflow, and the majority of end users should not need to know how to build everything from scratch (hopefully, assuming we've done our jobs in delivering a usable image :P)
There was a problem hiding this comment.
The docs/refactor branch name is a bit of a misnomer here. I really only edited for content and clarity rather than the architecture of the docs, which is the next step. A bunch of sections definitely need to be shuffled around.
There was a problem hiding this comment.
I agree that it needs to be separated out based on users and use cases, and I'll tackle that on the next go around. 🔨
alishamayor
force-pushed
the
docs/refactor
branch
from
f83a8c4 to
8136212
Compare
4 participants
Fixed formatting and broken navigation
Updated language for clarity and concision