Hey! I had a quick look around and couldn’t see this being talked about. However, I was wondering if there are plans in the roadmap for CMS to be available as a component?
I know we’re not support to use CMS as a component but I was trying very hard to include CMS as a react component, I managed to do so (kindve) but as stated it does take over the whole site meaning that the rest of the site attempts to use a hashrouter?
Is there a particular reason the CMS uses hashrouter or could it be configured to use a browserRouter?
I took the route of using the npm install of netlify-cms-app, attempting to have more control over previews and ideally have my own navbar at the top of the CMS.
What are the go to options here when people use CMS as an npm package? I cant find many examples of it being integrated with a site itself, and if the CMS was its own separate site how do you make the content go to a different git repo, would seem a bit weird if that was the route to take?
Another option I thought of was to have the CMS in the same repo as my site but in a different folder, then build it into the public directory of my site, making it accessible in the same way the CDN is?
I didn’t put this as a feature since I’m sure there are solutions to what I am attempting, I just cant figure it out at the moment.