Site Tree Import
Many times, by the time we are ready to prototype, we have already gotten to a fairly stable IA. The idea of building out an entire architecture for a medium to large site, one page at a time via the "add page" front-end capability seems really tedious and sort of archaic. However I have not yet been able to find any ability to import any kind of a file into the system in order to shortcut that process.
I am not concerned about having to teach people to build a file to a particular specification or format if that is necessary.
So, can anyone point me to a built-in integrated way to do this, or an add-on that accomplishes this task? I assume I could get a dev to write me a script that would do this via the API, but this seems like such a fundamental ask that it is hard to imagine it is not already baked in somewhere.
Home About Contact Us Our Team Our Board Products Widget 1 Widget 2 Pro Widget Services Widget Support Widget Training
and then import it into C5 in such away that it automatically creates a basic page structure. The labels listed would be used as the page names with some basic default page type (since this can easily be changed later). Creation date would default to when it was imported. Alias would default like it does now automagically when you type in a name.
I do not need to to automagically deal with adding page types, blocks of content, create Concrete5 instantiations, etc. I just need a fast way to build out a skeleton site architecture that can be done quickly by anyone once the IA is mostly solidified. Then the whole go in an massage/create/update individual pages process can proceed through the normal Concrete5 workflow.
If the text file is much more complicated or difficult to specify than what I have shown above, then it would probably be faster just to add each page using the add sub page button. I was just hoping to be able to go from sitemap in outline form to C5 site architecture rapidly.
You can generate and view the full sitemap at anytime in Concrete5, these articles I did may help provide a better view of the process.
Generate the Sitemap xml File in Concrete5:
View Full Sitemap in Concrete5:
Hope this helps,
Thanks for your reply. However, what I am trying to find a way to do is not generate a site map out of Concrete5 it is importing one into it.
I have in the past used several homespun CMS products that allowed me to create a simple text file in outline form that showed pages and hierarchy. Then I could import that file and it would create a basic page structure in the CMS.
For a small site clicking Home in the site tree and selecting add page, then filling out the rough details and saving, then clicking add page again, then navigating to a sub page and clicking add page again, etc. is fine. But for a large site with a 3 or 4 level deep site tree it is a real pain in the ass. Typing in the site tree in a text editor, or outputting it as a text file from whatever you use to build site maps (Like visio or omnigraffle) is MUCH easier that adding one page at a time by hand.