Blog

Dries's picture

Drupal Gardens now in open beta

Today we’ve reached another important milestone at Acquia: Drupal Gardens is now in open beta. No more beta codes. No more waiting to try the service. Now anyone can access Drupal Gardens and create a free Drupal 7 site!

It’s been fun to watch Drupal Gardens grow and mature during the private beta. In addition to building out the feature set, we’ve spent a great deal of time improving the stability and underlying performance of the service. And we’ve had a wild ride on Drupal 7 HEAD along the way, as Jacob Singh describes so colorfully:

Running from an Alpha versus HEAD is like the difference between playing Jenga on a sleeping elephant to playing Jenga on a cocaine addled elephant riding a skateboard being jabbed in the [rear] with a hot poker.

We’ve also invested plenty of time with Drupal Gardens users - gathering feedback, performing user tests, discussing potential features. One request that was added in the latest release is site duplication. This is the ability to clone an existing site, including its design, functionality, information architecture and content, to create a new site. It’s one of the first Enterprise Drupal Gardens features, enabling site builders and designers to do rapid prototyping in Drupal Gardens and roll out new sites quickly according to pre-defined templates. Site duplication will evolve into site and theme marketplaces where anyone can share site templates for use by others.

Drupal Gardens continues to advance with great strides. I encourage you to take Drupal Gardens for a test drive and to share your feedback with us.

Linea's picture

New feature: duplicate your site and create your own templates

Drupal Gardens was upgraded yesterday and one of the exciting features you'll see is a Site duplication feature. You can build a site, duplicate it, and use the copy as a starting place for a new site. The duplicated site will have your theme and all your saved themes, your modules, and settings. Users who have the Site owner or Administration roles will be copied, along with the content they created.

Back when Drupal Gardens was still on the whiteboard, this was one of the features we thought would be great. Users agreed and it's been on the most requested features list for months. Being able to duplicate a site will save people days of work and give them a way to have consistent theme and branding across a large set of themes.

People are getting clever with how they'll use this feature. Here are a couple of stories from our beta testers:

The web team at a large university is flooded with requests for new sites. They'll create a set of site templates (faculty site, event site, project site) that have the university's branding and standard header and footer. Then they'll duplicate the relevant template each time someone needs a new site. This will save them days of work.

A web designer spends most of her time on large projects, but gets tons of requests from clients with small budgets. To make these small projects profitable, she'll let her clients select from a set of pre-designed themes. She'll duplicate the site that has the selected theme, use the copied site as a template, customize it a bit - and voila! The designer spends hours, not days, on the project and her client gets an affordable site. Everyone's happy.

To duplicate your site, go to your My sites page and click on the Actions link next to your site.

Chris Brookins's picture

Improved SEO, Media, CSS-view and more in Drupal Gardens' June 30 update

In addition to the rush the Drupal Gardens team gets when adding cool new features, we like to get things right, striking a good balance between power and simplicity.  In the last sprint, we spent a bunch of time polishing the powerful XML Sitemap and Media modules with a focus on simplifying the UX and providing smart defaults so they work immediately after site creation.  Out of the box, these modules are highly customizable with many configuration settings.  Our goal was to reduce complexity but still expose the power the Drupal Gardens audience needs.  While we'd like to think we got it right, ultimately our beta testers will be the judges. We are looking forward to their feedback! 

In fact, for every new feature add to Drupal Gardens, we carefully review requirements and UI rather than just add modules.  We first survey the existing Drupal 6 and Drupal 7 modules on drupal.org to see if any meet our architecture, scaling and usability requirements.  Most of the time we find a module that comes close, and we port it to Drupal 7 if necessary (like we did for HTML Purifier in this release).   We then adapt it to our needs, contributing our code back to the issue queue for that module.  Understandably, not all module maintainers agree with the changes we want in their modules, but that is OK since Drupal's flexibility lets us alter their look and feel without an ugly fork.  It's a lot of work, but we think it's worth it.

We just released a new version of Drupal Gardens with the following new items:

  • Updated all sites to include all Drupal 7 core changes through June 21. For a complete list of what is new, see the raw CVS commit messages from June 1 to June 21.
  • Added support for XML sitemaps to help search engines index your important pages for better SEO. The XML site map can be optionally configured to include references to important menus and content on your site. Once indexed by a search engine, your site's XML site map will be displayed in search results. 
  • Improved the usability of media browsing, media management and finding media content.
  • In the ThemeBuilder's Styles > Borders and Spacing tab, you now can set any attribute such as width, height, border or padding to auto (e.g. use the default value that the browser calculates) or inherit (the value inherited from the parent element).
  • In the ThemeBuilder, you can now optionally choose to display the selected elements using CSS selectors or natural language terminology. With View CSS: Off (the default) elements you click will be displayed in natural language -- e.g. All paragraphs in all field-items in the main region. With View CSS: On elements you click will be displayed using CSS selectors -- e.g. #main .field-item p, which is useful when working with raw CSS in the Advanced tab.
  • In the ThemeBuilder's Power theming mode, the element selector now shows more elements on the screen at once, and for long elements, you can scroll left or right to see all of it, without wrapping to a new line.
  • Added Indent / Outdent buttons to the WYSIWYG editor.  
  • Zapped a truck-load of bugs reported by our incredible beta testers.

Haven't tried Drupal Gardens yet? 
We are sending out invitations all the time - just sign up and we'll get one out to you ASAP!

Chris Brookins's picture

New Drupal Gardens theme design contest - compete for an Apple iPad!

Want to win an iPad like our last winners did?   To qualify for the contest:

  1. If you don't already have a Drupal Gardens site, Signup for the beta - no worries, it's free.
  2. Click to create a site and go wild with the Drupal Gardens ThemeBuilder to customize your design.  One of our last winners created her site on a day.  You can too!  Feel free to use both the ThemeBuilder and its Advanced tab with custom CSS to to push your design to the limits.
  3. Add a link to your Drupal Gardens site in the Drupal Gardens Showcase Forum

We're looking for unique, beautiful sites to show in a Drupalgardens.com showcase, so some of you may see your theme design featured on the site.  The deadline is September 30th and a panel of judges will pick the best design. We'll announce the winner in the Forum and in a blog post on Drupalgardens.com.

The best design will win an Apple iPad - so enter today!

Linea's picture

Drupal Gardens Design Contest Winners!

The Drupal Gardens design contest submissions are in!  People submitted so many great themes that it was really tough to choose just one winner - so the judges decided to pick two!

The winning themes where chosen for their innovative, attractive and modern designs. and the winners are   ...drum roll please

http://valarietravels.drupalgardens.com by Valarie Martin Stuart

and.....

http://jonnycampbell.drupalgardens.com by Jonny Campbell

Congratulations to our winners - enjoy your new iPads! And thank you to everyone who submitted a site! To see the winning sites and other great sites that people designed for the contest, visit the Drupal Gardens Sampler site.

New contest starting - submit your site by September 30th!

We had so much fun in this contest that we decided to start another!  Submit your beautiful Drupal Gardens site to the showcase forum between July 1 and September 30 for a chance to compete. 

Linea's picture

A quick look at the ThemeBuilder power theming feature

I'm not a CSS expert, so I love that I can create beautiful themes for my sites without writing a line of code. Ok, a real designer wouldn't call my themes beautiful, but they look good to me. We designed the ThemeBuilder both for people who aren't fluent in CSS and for professional designers who need to create sophisticated themes for their sites. When we released the first version of the ThemeBuilder, designers told us that the ThemeBuilder was limiting. As one designer told me, using the ThemeBuilder was like "themeing with mittens". We took this feedback and went back to the drawing board to rebuild our themes and add a lot more power to the ThemeBuilder. The latest release of the ThemeBuilder gives you the option of working in a Power theming mode to take advantage of new feautures.

Here's a quick 2 min video to show you what this feature looks like:

If you don't have time for a video, then here are a couple of screenshots of the ThemeBuilder turned off and on.

With power theming turned off, you'll click on an area of your page and the ThemeBuilder will select the regions that are most commonly styled, like the header, navigation, or sidebar regions.


When you you turn on power themeing, the ThemeBuilder gives you access to more specific areas so you can do more fine-grained styling.

To learn more about how the themes work in Drupal Gardens, read these blog posts by Jesse Beach, one of our engineers. Her first is an intro to ThemeBuilder theming, followed by one describing stacks, wrappers, and columns.

Lynne Capozzi's picture

A vote for Drupal Gardens

Calling all Drupal Gardens fans. Help Acquia make it to the podium at the next Mass Innovation Nights event on July 14th!  Acquia will be showcasing Drupal Gardens at this local technology event and we’re also in the running to present a live demo. But we need your votes to do it! Only the top 5 exhibiting companies get to present and we’d love to be able to show the local bloggers and technology enthusiasts here in Massachusetts what Gardens is all about. All you have to do is go to:

vote-here. We’re first ones on the list!

Voting stays open right until July 14th so spread the word. Thanks!

-Your Acquia Team

Chris Brookins's picture

Removing the mittens in Drupal Gardens' June 10 update

When we started planning Drupal Gardens 18 months ago one of our goals was to help break down the barriers to creating stunning Drupal web sites. To that end we developed the Drupal Gardens' ThemeBuilder -- to allow people to point and click to create uniquely designed web sites, even if they don't know what CSS is or don't have the time to learn Drupal 7's powerful theme system. While the early beta versions of the ThemeBuilder went a long way, our beta testers asked for more, and rightly so.  At the time it was difficult or impossible to add custom image borders and backgrounds around some sections of their site, and they couldn't implement fluid-width columns, or custom page widths. Also designers with a strong vision spent a significant amount of time undoing the styles in our starter-themes instead of building up their masterpiece from a blank slate.  In addition, sometimes there were not enough hooks available to attach custom styles, which prevented our beta testers from creating some amazingly unique designs. 

Thankfully, the Drupal Gardens team is pretty good at listening. After absorbing the requests that we heard in our forums, usability tests and in many conversations, we decided what was needed was a rethinking of the Drupal Gardens themes from the ground up to address those concerns. In addition, we needed to enhance the ThemeBuilder to let power users access all the underlying structure of the themes without resorting to Firebug and writing CSS (which Drupal Gardens still lets you do -- in the rare case you need to). All of this new power isn't for everyone, and so we made sure most folks can still just pick a theme and click and style it to make it their own. But when the mittens have to come off so you can intricately style your site exactly as needed, you can now turn on a new "Power theming" switch to access a powerful new CSS Navigator and element selector to reveal every detail of of the Drupal Gardens themes. We have seen some of the fruits of this effort already - less than 1 day after posting the update one of our users created this unique site and we see hundreds more unique sites sprouting. We are pretty excited to see how people use these new gardening tools!

On to the meat of this release. Here is what's new:

  • Updated all sites to Drupal 7 Alpha 5 + all core changes through May 31. For a complete list of what is new, see the Drupal 7 Alpha 5 release notes or the raw CVS commit messages from May 14 to May 31.
  • Enabled Mollom comment spam blocking on all sites.  Every site has been provisioned with a Mollom account and comments made on the site will be protected.  You can turn on Mollom protection for most other Drupal forms as well.  You may choose to disable Mollom as long as you first turn on comment moderation for anonymous users.   
  • Added a new "Bare bones" theme which contains no styling at all (no borders, no colors, no font styles, etc.)  Use this theme if you want to start completely from scratch and build up from a base to create your own theme masterpiece.
  • Restructured and updated all themes to make them very flexible, standard, accessible, and SEO friendly.  The benefits are significant including:
    • Easier ThemeBuilder styling:  Now more than ever, the first thing you click on will be the element you want to style -- without resorting to use of the element selector (now hidden under Power theming, see below).
    • Flexible width support: Containers within the "page" element have fluid width styling.  The page width can be easily resized from 0 to 1100px.  The default is 960px wide.
    • Flexible gridding with fluid-width columns: All columns can be re-sized with the ThemeBuilder.  By default, they distribute evenly across a row according to the visible content.
    • Standardized HTML Structure: All themes are based on a standard structure so it is possible to start with any one theme like Kenwood and eventually style it to look like any other theme such as Campaign or Impact.
    • Better SEO: The h1 tag is always used exclusively for the node title on a node page. No more than one h1 is used per page which is important for search engine optimization.
    • More accessible:  Every Gardens theme page has a "skip to content" link just inside the body tag to provide a shortcut to screen-reading browsers and keyboard support.
    • Plenty of styling hooks: There are now a sufficient number of wrapping elements to reproduce nearly any design while satisfying Internet Explorer's lack of support for CSS 3 styles.  The structure of blocks now includes hooks for top and bottom cap decoration as well as an inner wrapping element that can be used to style the vertical edges or background of blocks.
    • New styling elements: Each top-level container (page, header, content, and footer) contains decoration structures.  With them you can place background images and styles that are not dependent on content, separating how your theme looks from the data it presents.
  • New Power theming.  While Power theming is off (the default ThemeBuilder behavior) you simply point, click and style your site.   If you need more fine-grained control over what you are styling,  click to turn Power theming  on and you will be able to:
    • Select many more theme elements with the new CSS Navigator.  After selecting any element on your theme, arrows will appear next to it allowing you to select the element's parent, first child, or sibling element (basically traversing the DOM to access elements hidden from the point and click method).  This is very useful to find the right element for the style change you need, and see the theme's structure.
    • Access the Element selector to control the scope of your styling.  e.g. style all h2s identically or only style the h2s located in your theme's sidebar.  Or style how any element appears in the hover state, active state, etc.
  • Fixed many bugs as reported by our awesome beta testers.

Are you a CSS junkie? 
If you want to learn more about the structure of the Drupal Gardens themes, our own Jesse Beach who lead the effort has started writing about them on her blog.  Check it out.

Haven't tried Drupal Gardens yet? 
We are sending out invitations all the time - just sign up and we'll get one out to you ASAP!

Linea's picture

Design Contest Extended to June 30th - win an iPad!

We've had a flood of new people joining the Drupal Gardens site over the last few weeks so we decided to extend the deadline for the Design Contest to June 30th.

The prize is an Apple iPad.

The rules are easy:

1) Design a theme for your site using the ThemeBuilder

- This can be a real site or a site that you're thinking about building

- It's ok to add custom CSS via the Advanced tab

2) Log into DrupalGardens.com and go to the Showcase forum. Click 'Post new Forum topic' on the right side of the page and provide a link to your site.


The winning theme will be selected by a panel of judges and the winner will be announced by July 9th.

Check out the Sampler site to see some of the sites that people have built on Drupal Gardens.

Good luck!


Photo from Apple.com

Dries's picture

10,000 Drupal Gardens sites

Earlier this year, we launched Drupal Gardens in private beta here at Acquia. A couple of days ago, we hit the 10,000 site mark! I want to thank all the people that that continue to help test Drupal Gardens, and whom created 10,000 new Drupal Gardens sites in such a record time. It is great to see more and more people build real sites on Drupal Gardens, and to see the platform that once was only envisioned, come to life.

We decided to build Drupal Gardens because we believed that many individuals and organizations want a killer web site, but have no idea that Drupal is a great way to build one. Even if they did hear about Drupal, few non-technical people succeed in installing a Drupal site, creating a nice-looking theme for it, and keeping Drupal up-to-date. We also learned that there are plenty of organizations that maintain tens, and even hundreds of micro sites and that Drupal Gardens has real promise in the enterprise. Our goal is to make Drupal Gardens a good fit for all of these audiences.

Talking to Drupal Gardens users, and reading people's reactions on Twitter, I'm convinced Drupal Gardens can be the game changer that we envisioned it to be. It's frickin' exciting!

Now we've passed 10,000 sites, our goal is to work towards an open beta, rather than a private invite-only beta. This means that over the next couple of months, you'll see us focus more on fixing bugs and fine-tuning so we can open our doors for more people. Of course, we'll continue to add new functionality too. A lot of big new features are already in the design and planning phase, but more about our plans in a future post.