To give a little more of a grip on what that last point means, here are the 5 modules I almost always use and that a designer should add to a CMS driven application:

Paragraph: a simple text module that contains markup. I sometimes also call it the paragraphS module and have it contain multiple paragraphs to allow the user to create several in a row.
Media: a basic module containing either just one image or video that can have a caption
Image + text module, that has an option to vary in alignment. This is a great visual device as it can work both as a link to more detailed content on another page, or as an element to break monotony in a page containing lots of text.
Collection: a selection of several teasers to other pages of a specific content type. Like a couple of news items or a bunch of events.
Streamer: A quote or large form text that repeats something on the page. This allows the user to quickly get a feel of the general content. And also breaks the monotony without having to add another image.

These are modules that cover most of ground, but this is just a standard set that doesn’t make the website stand out. It is advisable to add at least one or two modules that are unique to the project and directly align with the project goal. This gives the CMS editor freedom to both use the site as a publication platform while keeping te main functionality of the application in view. So this can be a special application form, an image mosaic or a specific graphic.

Like so you will be able to create a good design and let me know when you are done. Because who knows, maybe we can build it together!

Are you seriously going to start another journal?

How to prevent a CMS from getting abandoned

Why would anybody want a headless website?