Hi Jiang and Hilmar, Thank you for all your help. I followed the steps (Jiang) in your instructions and it appears I'm able to create a base project and copy it. All this while having shared content classes and folders. Now on to cleaning up the previous mess... Thanks again to both of you for your help...
Regards, Joe Henry On Sat, Sep 13, 2014 at 11:34 PM, Jian Huang <jhuangsoftw...@gmail.com> wrote: > Hi Joe, > > The tool mentioned by Hilmar is not a bad tool. > > However, I would like to approach your answer from an product consultant > perspective, meaning using as much out of box functionality as possible. > Please prepare yourself for a wall of text. > > A multi site project or one site per project? Assuming you have one core > project, and you have some mini sites, roughly 15-30 pages. These mini > sites uses the same content classes. Then why not just have a Start Page, > each project is connected to a dynamic anchor, so each project can be > assigned different publication packages, publication targets and > authorization packages. Mini sites can even cross reference/link pages > from other mini sites. The drawback is that you will have a project with > many publication targets, publication packages, authorizations and asset > folders. Not to mention project size. > > Alright, you want to do the master project and shared/sub project > approach. That is fine too, as long as you have a strategy or know someone > who has done this before and can give you clear documentation. Here is the > strategy and unofficial documentation. > > Start and finish your master project first. Seriously, finalize it before > thinking about starting shared/sub project. Once master project is > completed, you then have a better understanding and picture of what content > classes and asset folders your shared/sub projects should have to quickly > spin one up. Create an empty project, then go back to master project, > share, not all, but the content classes and asset folders you think a base > shared/sub project should have, to the newly created project. Now, go back > to the newly created project, you have content classes and asset folders, > but page structure. In this newly created project, which I now call base > shared/sub project, create a simply project structure: start page, under > that, you have a home page with sub pages, navigation manager code, global > header and footer reference, css, js. Oh, create simple publication > packages for the css, js, main site structure. > > Now, to spin up a mini site, simply make a copy of the base shared/sub > project, in the copied project, flesh it out with content, give it a true > publication target, publish, WOW, now you have a mini site. > > Even in Management Server 10.1 SP2, they have fixed all the bugs I have > encountered with content class sharing. Simply update content classes in > Master project, push that update button, and the updates are pushed. Then > you just have to go to individual project to publish out the new changes, > or wait for nightly publish, if you have one setup. > > Project export and import: export order doesn't matter, but make sure to > import master project first. After all projects are imported, go to master > project and ensure the sharing is still there, if not, just re-share. > > Project sharing is not difficult...just many corners and turns. Just need > someone to spend an hour or so and walk you through it, you will be fine. > > On Saturday, September 13, 2014 1:32:09 PM UTC-4, Hilmar Bunjes wrote: >> >> Hi Joe, >> I know what you mean. A lot of our customers and other companies I know >> stopped sharing content classes from a master to many different projects. >> There are pretty often problems that changes of (especially) content >> elements are not synchronizes correctly. Sometimes, all of the projects >> receive the change, sometimes only few of the projects received the change >> and so on. If you find a project with a faulty content element you need to >> change it again and share it and so on... >> >> (Not only) for this purpose we create a tool ( >> http://www.erminas.de/en/web/products/cms-sync-tool.html) to sync >> content classes between projects and servers. This way we manage most of >> the master/slave projects now. I know other companies that export the >> content classes after each change and import them into the other project, >> then switch the content class of the pages and remove the old content >> class. However, having multiple templates makes this procedure more >> difficult as you need to copy each template on its own... >> >> Best, >> Hilmar >> > -- > You received this message because you are subscribed to the Google Groups > "RedDot CMS Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to reddot-cms-users+unsubscr...@googlegroups.com. > To post to this group, send email to reddot-cms-users@googlegroups.com. > Visit this group at http://groups.google.com/group/reddot-cms-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/d/optout.
