Yes, but that would be needed only if you were creating the insert parts in Freeway. Then you would use that Action to force Freeway to generate fragments. But if you are building the shell in Freeway, and the fragments in another application (text editor or a semi-WYSIWYG like Dreamweaver) then you have to take care of that step manually in that environment.
If the person making the fragments needed to preview their work, they would either need to paste their work into a copy of your Freeway-designed shell and preview the resulting page locally, or they would need to upload it to the server and view it there.
There’s one other problem that I haven’t heard addressed here. If there are going to be many inserts and one shell, you are going to need some sort of server-side logic to combine the two. Server-side Includes (SSI) are used primarily to insert one or more template parts into a variable page, not the other way around.
For example, in a traditional SSI workflow, there might be a header and footer as separate partials (fragment files), saved as header.inc and footer.inc. Then each “real” page in the site would be the content (the body of the page) with some little snippets of code where the header and footer would go, and these pages would actually contain all of the canonical page-parts: html, head, (style, script, title) /head, body, /body, and /html. In your structure, this would be the part created by the “content” developer.
This means that you would be the one making the sub-page parts, and your work would be inserted into the other person’s site structure, not the other way around.
Another way to do this (although it seems like a lot of double-work to me) would be for you to create a separate blank page for each page created by the other developer, and then have a separate and unique include statement in that blank page to suck in the other person’s work. You would maintain the overall site structure and all navigation, but you would be creating a duplicate page in Freeway for each of the hand-coded content page fragments.
The way that I would approach this would be to decide which one of you is to “drive” the project (only one may do so) and then either do the traditional SSI thing using my TemplateHelper Action to create the sub-page parts in Freeway for the other developer to insert into his or her full-scope page layout, or use an application server like PHP to assemble the pages using a URL scheme to select the proper content to include. Either way, you will not have a lot of duplicated effort, and the concomitant opportunity for disaster.
freewaytalk mailing list
Update your subscriptions at: