-
Notifications
You must be signed in to change notification settings - Fork 33
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
[DOC] Create a glossary to explain all the concepts #1275
Conversation
♻️ PR Preview 4c4721b has been successfully destroyed since this PR has been closed. 🤖 By surge-preview |
ea4a5bc
to
642441a
Compare
642441a
to
074be92
Compare
Co-authored-by: Marcin Michniewicz <45601541+aibcmars@users.noreply.github.com>
Co-authored-by: Marcin Michniewicz <45601541+aibcmars@users.noreply.github.com>
docs/users/index.adoc
Outdated
@@ -30,3 +30,5 @@ include::bpmn-support.adoc[] | |||
|
|||
include::architecture/00-index.adoc[] | |||
|
|||
include::glossary.adoc[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would put this before the bpmn-support.
The bpmn-support paragraph is the 1st one that provides details about the lib. Glossary is general paragraph that reminds all import concepts that we use in the lib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as discussed, we may also add links to the glossary in the rest of the user documentation
Put it right after usage, prior introducing more details about the features
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok with my changes 😜
Closes #1272