2 ms·
This is how I tell people to use Confluence. There’s no hope of ever having the general set of all articles organized in a way that makes sense so just try to
by mason55 5y ago
This is how I tell people to use Confluence. There’s no hope of ever having the general set of all articles organized in a way that makes sense so just try to make the article searchable. If it’s about an error, make sure the error message is in there. If it’s about configuration of a feature make sure the feature name and “configuration” is in the title. Also make sure to write a paragraph describing what the article is about and different times someone might need it.
It’s like internal white hat SEO
- smcnally 5y agoMaking docs discoverable is good, and this works well for retrieving mostly static documentation and tickets. It gets complicated when when resulting items are used for troubleshooting or new documentation and tickets. When results, e.g., include multiple tickets and documents referencing the same error or configuration, which do you use for troubleshooting? Which results are the authoritative / canonical / source of truth for documenting the latest configuration directives? Versioning used well for the input helps. Organization and ontology is additional context for using search results well.