cool tech graphics

Drupal From Scratch: New Site Checklist

Filed under:
  • Set the Admin theme
    • Seven comes installed with Drupal 7
    • Rubrik is nice but has one bug that doesn’t show view replacement patterns
  • Set the site email address to your preferred administration email
    • admin/config/system/site-information
  • Before Creating any content (fake or otherwise)
    • Create content types
      • !!! Warning: once content has been entered, content types cannot be changed without damaging data
    • Turn on and configure path aliases with pathauto module
    • Turn on clean urls
    • Create text formats for user roles
      • admin/config/content/formats
    • Set up WYSIWYG editors if needed
    • Create image style settings
      • admin/config/media/image-styles
    • Create a 2nd admin account (Thanks to commenter Nik for this one)

What's your process for setting up a new Drupal site? Let us know in comments if you think we missed anything.

Date posted: November 2, 2011


What about IA planning? Design? Layout? Requirements gathering for site functionality? There's a lot of pre-production stuff that should go into any non-trivial site.

!!! Warning: once content has been entered, content types cannot be changed without damaging data

Well, OF COURSE you CAN edit your content types at ANY time without loosing data. AFAIK the only things you have to be carefull with are changing field settings for existing fields such as "Number of values".

Creating a 2nd admin account is pretty much one of the first jobs for me on a new install. This was a real pain in D6, but one of the great fixes that got introduced in 7.

@Cameron: This checklist is for starting *development*, yes all those things are necessary but that's not what this post is about.

@jochen, Good point, thanks for the correction

@Nik, Good one! I do that as well, I'll update the post.

i save out the db at about that point, so for all my new sites i start with a common setup, which is especially great for u admin roles

always thinks i'm a robot!

What about setting the user account creation settings to admin only. That's crucial. One time I forgot to change this setting and a bunch of porn sites created user accounts and posted spam.

Node Form Columns and Module Filter are 2 more modules that I always have installed right off the bat. As well as Admin Menu over the Toolbar.

The overlay module is the single worst thing about Drupal 7. The first thing I do on any D7 site is go to the modules screen and turn it off. Swapping the toolbar module for admin menu is also a good move.

For D7, Rubik's issue is actually with it's handling of all fieldsets/nested fieldsets but it is on the mend by the community ( so don't give up on it!

Well, checking permissions for every content type is regular workflow. Installing subpathauto is nice if the public will be editing content (node/14/edit is ugly, blog/my-post/edit is way better).

Add new comment

Restricted HTML

  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type> <li> <dl> <dt> <dd> <h2 id> <h3 id> <h4 id> <h5 id> <h6 id>
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <cpp>, <java>, <php>. The supported tag styles are: <foo>, [foo].
  • Web page addresses and email addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Metal Toad is an Advanced AWS Consulting Partner. Learn more about our AWS Managed Services

Have questions?