We're looking to add CMS to our existing products (multiple apps) help web app that's currently a custom built app just displaying versioned documentation from a git repo. I'd like to use umbraco for it's powerful CMS.
Has anyone built (or have recommendation on how to approach this) a site that delivers version controlled pages/docs? Example. We have multiple products but if we can figure out how to deal with one, we can deal with multiple. A user hits the site and want to visit the user guide for product Foo. They'd hit the site and should be (in my mind) be sent to the latest versioned page with the option to switch (just like you'd expect with ms docs for example. So path might look something like mysight.com/products/foo/1.5/user-docs or mysight.com/products/foo/2.0/user-docs.
One approach out-of-the-box is to create a doc type that is a category placeholder and you drop all the docs for a particular app in within a numbered folder like Products > Foo > x.x (one for each version). The in your code behind add some logic to spit out other available versions so users can switch between versions from within a particular doc.
Note that we are trying to move away from version control in the repos as it's become too much setup for all the users involved which are mainly BA's and PMs. Not all our products even have a git repo as they are 3rd party apps that are built inside a no/low-code product. We're looking to extract that complexity of the md files we currently have managed in a git repo and move it to a full featured CMS like Umbraco. I already know I can do it but really just looking for some guidance, tips/tricks, lessons learned, etc. Thanks!
Building versioned product wiki type app
We're looking to add CMS to our existing products (multiple apps) help web app that's currently a custom built app just displaying versioned documentation from a git repo. I'd like to use umbraco for it's powerful CMS.
Has anyone built (or have recommendation on how to approach this) a site that delivers version controlled pages/docs? Example. We have multiple products but if we can figure out how to deal with one, we can deal with multiple. A user hits the site and want to visit the user guide for product Foo. They'd hit the site and should be (in my mind) be sent to the latest versioned page with the option to switch (just like you'd expect with ms docs for example. So path might look something like mysight.com/products/foo/1.5/user-docs or mysight.com/products/foo/2.0/user-docs.
One approach out-of-the-box is to create a doc type that is a category placeholder and you drop all the docs for a particular app in within a numbered folder like Products > Foo > x.x (one for each version). The in your code behind add some logic to spit out other available versions so users can switch between versions from within a particular doc.
Note that we are trying to move away from version control in the repos as it's become too much setup for all the users involved which are mainly BA's and PMs. Not all our products even have a git repo as they are 3rd party apps that are built inside a no/low-code product. We're looking to extract that complexity of the md files we currently have managed in a git repo and move it to a full featured CMS like Umbraco. I already know I can do it but really just looking for some guidance, tips/tricks, lessons learned, etc. Thanks!
is working on a reply...