Again, I'm comparing to Joomla! here. There I would deploy for the client and then adding new menus and entirely new content would go through the backend.

I may be totally off here but with Couch you're essentially injecting the CMS aspect into a static HTML site. So I'm essentially making sections like divs editable. Which means adding a new section or page would require the designer to step in and do the job. This is not a major issue in itself but there are clients who want CMS so they'd ideally need you rarely if at all.

I can see where this would be great and simplify things for many clients. I'm definitely going to be using Couch but right now I'd like to figure out how it fits in and what it can or can't do.

But like I said, I may have totally missed something. I'm also relatively new to this.

[KK]

Which means adding a new section or page would require the designer to step in and do the job.

Not at all. Once you, as the designer, hands over the site to the client, the client can add/remove pages by himself.

I think you are missing the concept of 'cloned pages' that is central to Couch's working.
You are right that we 'inject' the CMS into static HTML pages but once you declare a static template to be 'clonable', the client can add as many copies of it as he needs.

You can find more info at
http://www.couchcms.com/docs/concepts/cloned-pages.html
http://www.couchcms.com/docs/concepts/n ... maker.html

May I request you to please take a look (just browsing through will do) at http://www.couchcms.com/docs/tutorials/portfolio-site/ ?
The tutorial is just 7-8 pages long but is profusely illustrated and will give you almost everything you'd need to work with Couch.
Please take this as a recommendation. It'd be time well spent

Thanks

Which means adding a new section or page would require the designer to step in and do the job.

Not at all. Once you, as the designer, hands over the site to the client, the client can add/remove pages by himself.

I think you are missing the concept of 'cloned pages' that is central to Couch's working.
You are right that we 'inject' the CMS into static HTML pages but once you declare a static template to be 'clonable', the client can add as many copies of it as he needs.

You can find more info at
http://www.couchcms.com/docs/concepts/cloned-pages.html
http://www.couchcms.com/docs/concepts/n ... maker.html

May I request you to please take a look (just browsing through will do) at http://www.couchcms.com/docs/tutorials/portfolio-site/ ?
The tutorial is just 7-8 pages long but is profusely illustrated and will give you almost everything you'd need to work with Couch.
Please take this as a recommendation. It'd be time well spent

Thanks

Seems I got ahead of myself a little. I'll most definitely run through that tutorial tomorrow.

This really does seem like the perfect CMS for me. Thank you