The Easiest CMS on Zope... Zwiki
Remember, Zope is an application server, not a CMS (content management system). A typical beginners mistake while learning Zope is to only use the built-in elements (for example Folder and Page Templates) and push content into these. That is "wanting it the easy way", which is one good recipe to end up with the head on a brickwall while having a velocity above the usual rotation of this planet. "Zope is an application server, not a CMS" means: You need an application to run on Zope. A proper application consists of a bunch of python filesystem based products. One very typical application of that is a CMS. There are some CMS for Zope out there that are well known, but that I don't like so much. One easy, fast, and simple alternative is a closed Zwiki...
The easiest and cleanest CMS on Zope is a Zwiki: Install it, style it, close it to allow editing/commenting only for authorized users, educate those users how to use it. Done. The content model of that is pretty simple. And you might have to follow some guidelines to get a consistent navigation and styling. But for a small company, a personal site, or a small event site (what I would call "a bunch of pages" sites), a zwiki based site is fine. If the users are clever enough to be able to learn structured text or html editing you are rolling real fast. I think some people have even integrated Epoz or Kupu into Zwiki (though I didn't try, stx/html is good enough for me). Want an example? My Greek site in the works is being done this way.
But won't people just change the wiki?
One objection you could have here is "but it's a wiki, people from all over the place will go in and change my pages". Which is the reason why we remove the editing and commenting privileges for anonymous users. That way, the wiki part ("go in and edit any page") is only for our own editors. The wiki turns into a CMS. Anonymous visitors can only see the pages, not change them.
You likely don't need the workflow anyway
A lot of CMS solutions don't need big stuff like workflows. If you don't know what a workflow is here: It's a way to specify that changes to a page have to go through different levels of approval. A writer submits changes to a page. An editor has to check those changes and give his OK. In large organizations maybe a lawyer has to give her OK too. You likely don't need this nightmare. But once you have one of those big systems you will have a huge learning curve explaining your users why they have to click through 7 checkboxes and dialogs to put some small change online (or you might spend the time to switch off the built in workflow). Workflows are not for the small folks.
Mix and match with other Zope products
Some CMS also have lot's of add-on tools, like weblogs, a user forum, image galleries. That is a more valid point to choose a big CMS solution over a "closed" Zwiki solution. Zwiki has some things built in, but not all those. But we should not forget that Zwiki is just one application running on Zope. It can easily be combined with COREBlog (for weblogs), or one of the Zope gallery products, or ... etc. Definitely the work to integrate the layout of these solutions is larger than for plugging in a module into a "big" CMS. But the hard part -- integration of user accounts -- is taken care of by the Zope security and authentication machinery.