You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know this is a bit early, but I would like to recommend eventually having a Users Guide for CKE5 (in addition to developer/API docs). The last one that was created was for CKE3.x, and I reference it a lot for my end users. However, I often have to mention the caveat that it is "old documentation".
I realize that you are trying to support a variety of UI "looks" for CKE5, so creating a useful Users Guide may seem like an impractical or impossible task.
Here is what I suggest: Essentially "crowd-source" CKE5 User Guides. You could maybe do this by putting the CKE3.x docs (as a starting point) in a dedicated GitHub repo, and allow application developers to do forks and pull requests on the docs. This way, you keep your time investment to a minimum, and by allowing the docs to be forked, application developers can handle creating a version of the docs that is customized for their particular CKE5 build/implementation.
The text was updated successfully, but these errors were encountered:
I know this is a bit early, but I would like to recommend eventually having a Users Guide for CKE5 (in addition to developer/API docs). The last one that was created was for CKE3.x, and I reference it a lot for my end users. However, I often have to mention the caveat that it is "old documentation".
I realize that you are trying to support a variety of UI "looks" for CKE5, so creating a useful Users Guide may seem like an impractical or impossible task.
Here is what I suggest: Essentially "crowd-source" CKE5 User Guides. You could maybe do this by putting the CKE3.x docs (as a starting point) in a dedicated GitHub repo, and allow application developers to do forks and pull requests on the docs. This way, you keep your time investment to a minimum, and by allowing the docs to be forked, application developers can handle creating a version of the docs that is customized for their particular CKE5 build/implementation.
The text was updated successfully, but these errors were encountered: