Do you have a go-to list of modules for every install?

[Simon66]

Do you carefully consider each module you install or do you have a go-bag of must-have modules that gets uploaded with every install?

Here's my go-bag... wheels up in 20...

AceEditor
CGExtensions
CGSimpleSmarty
CGSmartImage
CustomGS
FormBuilder
Gallery
GBFilePicker
ListIt2
ListIt2XDefs
SEOTools2

Each of these is guaranteed to be used in every site I create.

What's your list if you have one?

[Wishbone]

What I do is have a CMSMS install with all the modules loaded, customized the way I like, summary/detail templates with a bunch of my normal stuff in it, working contact form, some of my common UDTs, GCBs, etc... Also have working examples of CSS/JS menus, content sliders the way I like them, Cufon.. I then do an SQL dump, and zip the entire thing up, and use that for the start of my projects. I then delete what modules, etc, that I don't use.

[JohnnyB]

I do the same as Wishbone and keep a .zip of CMSMS with the default modules, plugins, udt's and settings for each of them, including default templates, etc. I then extract the .zip and import the .sql saved from my default settings. The tricky thing is keeping everything current.

My go-to list of modules for every install:
CGExtensions
CGSmarty
CGSmartImage
Formbuilder
Snippets
Sitemap Made Easy

[faglork]

2 modules which havent been listed so far:

Toolbox (the autolightbox feature is great)
Revisions (although still beta, it works well)

cheers,
Alex

[paulbaker]

And another that's not been mentioned: Archiver
http://dev.cmsmadesimple.org/projects/archiver
Takes 30 seconds to install and saves a copies of every changed Content Page, Global Content Block, Stylesheet, or Template for if (when) an editor messes up.

[Simon66]

Thanks for the replies.
Before I try them out, what are the major differences between Archiver and Revisions?

Has anyone tried both?

[paulbaker]

Haven't tried Revisions.

[paulbaker]

Hmmm, thought of 2 more.

Statistics, which gives an easy-to-use interface for clients to get an idea of visitor numbers.

Notifications, so that I get an email when a visitor fails to get in to admin area because of wrong username/password. And an email each time telling me when people successfully login. Gives a good idea of who does (and doesn't) update their sites themselves.

[Simon66]

Thanks for those Paul,
I'm definitely adding them to my list.

[pixelita]

Great suggestions so far and very timely, as I am in the middle of updating a whitepaper I did a few years back on CMSMS and I need to update the list of modules.

I quite like Owner Manual for use with sites developed for clients.

I also love Wishbone's technique of putting all his pots and pans together and then ditching what he's not going to use for that project. Keeps development time to a minimum.