Two months later and I am ready to create a Child project.

I create a Master project that has everything I need. I am wondering how to create a Child project.

I tried to create the Child project as a copy of the Master and fresh project, without any success.

In the Master project, I selected the Content Classes nods and clicked on Edit Content Class Sharing (did the same for the Folders under the Project nod). I selected the Child project as the destination. Both the Project Folders and Content Classes have the green check mark on them.

Do I create a copy of the Master or start with a fresh project as the Child project? Is there anything else (other then Edit Folder Sharing and Edit Content Class Sharing) that I need to do to share the Master project?

Thanks,
Jamie

1. Nav Mgr usage in large projects - hints and tips

2. All about plugins

3. RQL for beginners

4. Incorporating .NET component references within the CMS

5. A single list of all RedDot user resources, including other blogs, facebook group, google group etc.

Cheers

Phil

It sub-section will have it’s own navigation with some common link (contact page, feedback. ect..). So, not too much sharing.

What you are saying makes sense to me. I am still building my project, I will let you know how it turned out.

Thanks again,
Jamie

I’m glad you found the article helpful

1) When you say your site has 25 sub sections, are they separate, or do they share the same navigation? If it’s the latter it may be worth trying to stick to one child project as you will hit issues trying to bring all the navigation together.

I do have to say though that I’ve no experience of handling a 6000 page site, our largest is about half that. You will start to encounter speed issues with large projects, especially if you show multiple layers of navigation on one page like we currently are.

If you’re lucky, and they don’t share much of the navigation, then I would say yes to the 25 child projects as it will make your life so much easier.

2) The interesting thing about content class sharing is that you can have as many layers of sharing as you want. You will probably end up with a three tier setup, rather than a two tier one. Your generic templates that need to be in all projects can be in the master project, then you can have the first layer of children bringing in the styles and initial structures of your different designs. Then each projects of these can have children that have the actual content (in effect making them grandchildren of your master project).

Using the idea that you can have children inheriting from any level means that you can become more specific with your projects, templates, styles and permissions the further down you go… but still running from one core set of templates. (I hope that makes sense?)

3) By the time you publish out of Reddot, you don’t need to worry about the sharing… so your original FTP targets should be more than adequate

Good luck!
Paul

I work for a Government Department and we just purchased RedDot. Being still in the planning phase, I am trying to figure the best path for us. From what I read, so far, I believe master/child project is the way to go.

I have a questions:

1. The department website has about 25 sub sections with approximately 6000 pages. Would you make one master and 25 children projects? One child project per sub section?
2. As we are ready now, we are going forward but something that we need to keep is the creation of one master all of Government websites. Is it possible to share content class between two master projects?
3. We are going to use FTP as the Publishing Target and keep ftp rights that we have them now. Ie. We are only ftp access to the department folder (off the root of the Government’s site) and not the root itself. So, if the sharing between the two master projects (Government Master and Department Master) is possible, do we need access of the

Thanks in advance.
Jamie

Unfortunately, a current limitation of RedDot CMS is that it requires an asset manager folder to be assigned to all image and media element placeholders. In other words, there is no way to select a “Null” folder setting (or select a: “[Local folder]” alternative).

Since the Asset manager folders are typically shared from the foundation project, this results in all asset content (potentially from multiple child projects) being loaded into common asset manager folders by default…and that’s potentially disastrous (especially if your users are poorly trained) with users from different projects either:-

mistakenly overwriting each others content or
creating multiple versions of the same content, bloating your Asset libraries in the process.

The best solution to avoid this would be to have all child projects use their own local Asset Manager folders…but that’s where we hit a problem. because although the “Folder” option for each element can be manually amended to point to a local asset folder, it appears that everytime you update a content class in the foundation project and roll out the change to all child projects, your local settings are over-written!

I’m mostly done with your other question, so that should be up over the weekend… with pictures this time