I have multiple established laravel apps .
At least two of them are in need of basic CMS functionality. Pages and posts.
How difficult would it be to integrate wardrobe core into an existing laravel app, that already has its own admin architecture?
I'm honestly not sure about integrating into an existing admin. It uses the default laravel login system so I assume you could just carry the login over and then modify wardrobe to match your existing layout.
I would probably recommend trying it on a dev setup just to see if it would work or not. You can follow the instructions in the "core" repo's readme to install into an existing laravel app: https://github.com/wardrobecms/core
If you have any specific questions along the way just post here and we will do our best to help.
In my experience I use a separate DB instance to manage wardrobe and my business logic application for SaaS apps and the likes. This is configurable in the database config for wardrobe package.
For a more brochure sites I would start with wardrobe as the main theme/blog platform and design everything around that using the default database connection.
I can appreciate Wardrobe's dedicated Admin panel, but this is one of the biggest things I'm hesitant on for integration with an existing website with and existing admin. I make a lot of websites for clients with custom admin's and asking them to have two admin's with two logins, etc... I personally don't have a problem with it, but some client's would (mostly because they are silly unreasonable people).
I actually have a quick question regarding this, im currently looking at doing this for my own personal website and was wondering what the best way is to go about sharing the main layout of the website with not only the wardrobe cms but also with the custom stuff that im looking at building which isnt going to be using wardrobe?
should i be trying to link everything back to use the theme that I have created in the wardrobe cms or should i be moving the main layout into the normal laravel views folder and going from there?
I think this is going to really depend on your preferences. If I was building a bigger site around wardrobe I would probably put my custom views in the public/theme dir and then just have my custom routes/controllers load them.
Also depending on how advanced you are wanting to get I am working on adding better custom routes for your themes. This should be ready in v1.1 if all goes as planned.