Skip to content
Permalink
main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

iam-knowledge-bits/docSystem.adoc

Go to file
 
 
Cannot retrieve contributors at this time
78 lines (52 sloc) 2.76 KB
Raw Blame
Open in GitHub Desktop

docSystems.adoc

2023-10-18 12:03 chat w SteveZ

I associate hierarchy with

.

I’d appreciate your reactions to some thoughts I had about the Grouper Survey Initial Recommendations: https://docs.google.com/document/d/1uWRomgUflT6Ec03vo-tL795XUUr2HdpU0WrVLZC-Yvs/edit?usp=sharing

Page Warnings - Experimental - Since - Deprecated - Obsolete - Replaced By - Outdated

- Steve Zoppi -

I have a similar "sense" of those taxonomies from the survey feedback too…​

I think that the missing "prescription" is how to maintain documentation in alignment with the version - so right now (the way you’ve written it up) it lacks the information hierarchy ands presumes "tagging" may be the primary means of categorizing a given article or document.

The thing I’m wrestling with (in my head) is - the information hierarchy that encapsulates each group of documents.

I don’t have good answers (yet) but I’m considering that there needs to be - two branches (at least) of hierarchy: (1) Global/Persistent Concepts and Facilities artifacts/documents/articles (2) Ephemeral/Version-bound artifacts/documents/articles.

2023-04-06 11:18:07 Setting up evolveum-like doc site

https://docs.evolveum.com/about/jekyll-environment/ ← install, config, build, run jekyll site

- local jekyll instance of Evolveum Docs running: -

2023-04-04 11:28:40 adding commenting to a static site

2023-04-03 13:11:12 evolveum approach to documentation