Thread

Not sure if this is helpful or not (though it worked for me in some cases): if you have the “right” kind of admins, you could consider coding a special “edit” link that only shows up for them, and takes them DIRECTLY to editing the “static” content for that page.

I like this idea a lot. I just experimented with adding the backend links—generating them was a bit of a chore, but it seems to be working now. After that, I just put the edit link in an {if logged_in}{/if} block.

Thanks for the tip!

I might be a day late and a dollar short here, but, perhaps this info will be useful for your next project.  There was a bit of discussion over at this thread.

We really dig Structure for page management.  It’s way, way more straight forward to use than the “Pages” module, and offers a solid replacement to EE’s default edit entries list page.

Generally we setup a Pages channel, which, depending on requirements, might have some or all of these custom fields:
- Text fields for meta title/keywords/description
- Wygwam field for page content
- Matrix field for the page’s images/gallery
- Playa field(s) for the pages’s top/side/bottom modules/widgets
- One or more select boxes that allow users to pick various layout options

I’m sure the one page / channel model has some merit, as Boyink knows his stuff, however, I can’t think of a good reason off of the top of my head as to why I’d ever want take that approach… it seems like it would make getting around in the control panel more confusing than it has to be.