Integrate Academy #3233
Replies: 1 comment 1 reply
-
Github comes with some features, for example: anyone can propose edits, discuss edits, see revision history, and undo changes. So question to you, Dave, which features of Github, if any, must be supported in order to migrate away from it? I could imagine a userflow that moves the editing of academy content into the community platform, if that is what you mean by "integrate academy." Here is the idea: To edit a page:
To create a new page:
To upload a new image: To replace an existing image: To edit the sidebar: To delete pages/images: All of these pages (and endpoints that modify data) should require special admin rights. With this flow above, you also don't have the ability to preview, unless they make changes on a test instance first. A more complicated flow could also be decided (for example with pending edits and approvals) but that depends on which features are needed. Given the flow above, I am not sure if Docusaurus could still be used; as it would need to be able to convert markdown content into HTML at runtime (because an admin may come and change the content at any moment.) Maybe it can do that, no idea. Maybe github.com/markedjs/marked would fit requirements, I didn't check. What I have described does not necessarily address problem 1, 3, or 4, but I imagine it would bring problem 3 one step closer to being solved. There is a chance that "Integrate Academy" meant something totally different, so let me know if I misunderstood. (TBD = to be determined.) |
Beta Was this translation helpful? Give feedback.
-
The academy is essential for all our communities since it brings the core knowledge to everyone. The academy is setup using an external tool (docusaurs) which has a few problems.
The goal here is to identify the problems and discuss/share possible ways forward to see if it's worth putting on our roadmap.
Current problems
Things to keep in mind
Whats needed next
Beta Was this translation helpful? Give feedback.
All reactions