Planet Drupal

Most e-commerce websites offer a checkout process indicator, the indicator often appears at the top of a checkout page and lets a user know which checkout process they are currently on. For example, an indicator should display each major checkout process such as checkout, review and complete. In this day and age, everyone wants to know how much effort is required to complete something and an indicator helps users gauge the effort required. Adding an indicator to a website that uses Drupal Commerce is very easy thanks to the Commerce Checkout Progress module.

In this tutorial, I'll show you how to setup the Commerce Checkout Progress module on your Drupal Commerce website.

 

I am so glad that my Dear friend Ashwini broke the ice for us. And I would

like to thank him for the same, I followed the steps and Bingo!!! 

I have Drupal on my machine. I  walked little further and quick look over changes.

 

Most striking changes I found :   

 

1) The biggest bang, if you haven't heard of is "Symfony meets Drupal 8"

Yes, that is correct! Drupal 8 has adopted many low level components like 

HttpFoundation, HttpKernel, Routing, EventDispatcher, DependencyInjection, and ClassLoader from 

Symfony to achieve more structured code & semantics with the help of OOPs,

which community was waiting a while.

 

According to me  Drupal will achive the same objects transmission through out

the flow with better encapsulation.

 

"By adopting HttpKernel, Drupal and Symfony projects will become more interoperable. 

It means that you will be able to easily integrate your custom Symfony applications with Drupal... and vice-versa."

- Courtesy Fabien Potencier, www.symfony.com (http://symfony.com/blog/symfony2-meets-drupal-8) 

 

2) New drupal 8 has Twig as template engine. Personally I was waiting for such change in drupal after

working for last 5 years. It was always a wish to have template engine as a part of core to speed up the 

performance. I hope it will be fast, secure & flexible as it is mentioned on http://twig.sensiolabs.org/.

Thanks to Fabien Potencier. But I guess this is also because Symfony2 has it.

 

3) The next thing made a tick was the folder structure & separations. Now drupal has structure like

core, modules, profiles, sites, themes and index level files with ROBOT.txt. The core has drupal's

traditional file & folder structure but there you can find additional folder called as "vendor".

This is the folder where symfony components resides. You can find 

Symfony classes : 

Symfony framework classes

Twig :

Twig is a modern template engine for PHP 

Composer :

Composer is a tool for dependency management in PHP. It allows you to declare the dependent 

libraries your project needs and it will install them in your project for you.

Doctrine :

The Doctrine Project (or Doctrine) is a set of PHP libraries primarily focused on providing 

persistence services and related functionality.

EasyRDF :

A PHP library designed to make it easy to consume and produce RDF.

Guzzle :

Guzzle takes the pain out of sending HTTP requests and the redundancy out of creating web service clients.

 

By bunch of all these, drupl 8 was never powerful than this.

 

4) While administration I did not find many changes than admin menu structure. But there are some modules

included in core than drupal7. 

Majorly, 

Views is part of core now. 

ckEditor is in there, which was surprise to me as I always prefered TinyMCE for Drupal sites. 

Language module is included in core for i18n.

 

With curasity I tried to have contents in two differant languages and it is user friendly.

Though personally I feel adding plugins in CKEditor is pain and needs improvements.

 

5) Last but not the least for now, documentation of hooks available for Drupal 8 is ready before 

it is stabalizing core. It is at http://api.drupal.org/api/drupal/core!includes!module.inc/group/hooks/8. 

And I am happy that it will really help community to conribute back to core modules/themes, core & contributed 

modules/themes.

 

I will try to explore more and will try to share more in upcoming posts.

I'm happy to announce that Lee Hunter has been appointed as the new Documentation Team Lead for Drupal. Lee has been a long term member of Drupal's Documentation Team, and has been a technical editor for thirteen years of his professional career. To read about Lee's vision for Drupal's documentation, please check out his announcement blog post. The short version is that he will focus primarily on coordinating the effort to document Drupal 8 and exploring ways of making Drupal a more effective tool for technical communication.

From 2010 to 2011 the Drupal Documentation Team was led by Jennifer Hodgdon (jhodgdon) and Ariane Khachatourians (arianek), and up until July of year just Jennifer. Without their leadership and effort, tens of thousands of people would have faced great challenges in using Drupal. I'd like to thank Jennifer and Ariane for the tremendous effort that they put into the documentation team.

Documentation is one of the most important aspects of Drupal, and not one that we should take for granted. Please join me thanking Jennifer and Ariane for their work, and in welcoming Lee as Drupal's new Documentation Team Lead.

So you have a virtualhost set up for Apache and your local site is running at http://yoursite.local and everything is working great on your computer. Now you want to test that awesome responsive design you've been working on with some other device(s), so you try to go to yoursite.local which won't work unless you want to modify the host file on the device(s), which is something you can't even do to an iPhone/iPad without jailbreaking it. Gah.

So, then you try to access the site with your device by just using your computer's IP address + the path to your docroot (for instance 10.0.1.10/mysite/trunk/htdocs/) - great idea and now the site at least sort of loads, but all the links to the CSS/JS and image files are broken...

In my own search to avoid jailbreaking I finally figured out how to enable normal-looking-pages access to devices following a bit of trial and error. The whole setup to enable this is done on the computer your site exists on - no need to fiddle with any of your other device(s) settings:

1. Edit the /etc/host file on your computer and add you computer's IP along with the relative path to your site (relative to Apache's docroot). For example:

10.0.1.10 path/to/site/

2. Add a virtualhost to apache like so, using your computer's IP address as the server name and this time use the absolute path for the site:

<VirtualHost *:80>
DocumentRoot "/Users/myuser/Sites/path/to/site/"
ServerName 10.0.1.10
</VirtualHost>

3. Restart Apache and now you should be able to access your site with any other device on your network by simply using your computer's IP address as the url.

Categories: Drupalmobiledevelopmentresponsive

With Mobile in the forefront of digital government initiatives, laying the foundation for a mobile solution for the Department of Energy (DOE) was a priority. With this in mind, we wanted to meet this challenge for DOE in a way that was efficient and affordable.

PHP's command line interface doesn't respect the max_execution_time limit within your php.ini settings. This can be both a blessing and a curse (but more often the latter). There are some drush scripts that I run concurrently for batch operations that I want to make sure don't run away from me, because they perform database operations and network calls, and can sometimes slow down and block other operations.

Can you tell when the batch got backlogged? CPU usage spiked to 20, and threads went from 100 to 400.

I found that some large batch operations (where there are hundreds of thousands of items to work on) would hold the server hostage and cause a major slowdown, and when I went to the command line and ran:

At Four Kitchens, we have done quite a bit of work within the education industry. As we began looking into expanding our footprint within the education web technology space, we discovered that there was a corresponding need in the marketplace waiting to be filled; especially within higher ed. Universities and higher ed institutions continue to look for ways to cut costs, deliver content more effectively and easily, ease administration, and facilitate online learning/training. While several (open source and proprietary) solutions exist, there seems to be little clarity into what the options are, and perhaps more importantly, what the possibilities may be.

So we set out on a quest to understand the “lay of the land” a little better. Broadly speaking, there are three categories of solutions:

Learning Management Systems (LMS)

Succinctly, an LMS is a software application for the administration, documentation, tracking, reporting, and delivery of education courses or training programs. There are an incredible number of LMSs available to choose from; some proprietary, some open source, some completely custom built, some entirely off the shelf. Traditionally, LMSs have focused more on content delivery than content management, which is part of the reason we found that almost no academic institution is entirely happy with the LMS they chose to implement. Said another way, a complete solution for an academic institution involves the best aspects of CMS and LMS, and traditional LMSs have been very poor at CMS functionality.

Part of the problem, I venture to guess, is that there is surprisingly little available documentation around what the business and functional requirements of a good LMS are! The argument could be made that every academic institution has different needs and it is thus difficult to compile a unified set of requirements. But despite those differences, is there core functionality that we can distill as universally applicable? It would seem that at a minimum, the requirements of an LMS are:

1. Classroom management (attendance, etc)
2. Delivering content to students
3. Collecting completed assignments
4. Reporting student performance
5. Streamlining administration
6. Improve customer service
7. Developing and queueing standard content, and providing opportunities to tailor content
8. Provide self-service learning for students and employees
9. Deploying learning resources and programs quickly
10. Extending, maintaining, and enhancing communities

Some of the LMSs that we feel best meet these objectives are:

Canvas: Arguably the most robust and full featured LMS offering currently available, Canvas is on a meteoric rise and has been gaining use in both the higher ed and K-12 segments. It is an open source and open API product, and is one of the few (only?) LMSs that has a free mobile app to go along with it.

Sakai: Sakai is a full featured LMS built by Stanford, which has been adopted by MIT, Berkeley, and others. It is not open sourced, but operated on a community backed license.

Moodle: Moodle is a fully featured and powerful LMS, but the once dynamic open source community behind it has seen some attrition. The LMS isn’t on the leading edge anymore, but with continued support from developers, it continues to remain very relevant.

ELMS: Headed by Bryan Ollendyke of Penn State University, ELMS is the most prominent Drupal based LMS. A lot of progress has been made, but there is still some work to be done, and Bryan is a well of knowledge on the subject and is happy to talk to anyone that wants to help further its development.

Blackboard: The original dominant LMS, Blackboard has since fallen out of favor with the emergence of the other more modern, elegant, and open source solutions. It is regarded as a very rigid LMS, and awful as a CMS. Blackboard has attempted to stay relevant by acquiring Moodle and Angel.

While perhaps biased, Instructure (the makers of Canvas) have a feature comparison chart on their website.

Site building solutions and tools

Site building tools are especially important to higher ed institutions, as they frequently need to provide academic units and departments an easy way to brand themselves under the institution’s overall brand. ImageX Media, Chapter 3, Funny Monkey, and several others have done excellent work to provide open source solutions that provide the ability to manage content, rapidly deploy sites, control branding, etc. Our four favorite Drupal based solutions are:

• OpenEDU, ImageX Media
• Open Academy, Chapter Three
• Julio, Funny Monkey
• Open Scholar, Harvard

Social based “LMS” platforms

This class of solutions is centered around giving teachers and students a way to interact easily online. It shifts away from the “heft” of traditional LMSs to try to facilitates easy communication, discussions, sophisticated learning opportunities (traditional and e-learning), content distribution/sharing, etc. Taking the view that allowing educators and students to connect more easily provides the greatest value, all the other functionality and bells and whistles are built around that core premise. While none of these services use Drupal, the big players are:

Edmodo: With 7.4 million users at over 80,000 schools, Edmodo is considered one of the best solutions for Elementary and Middle Schools. It boasts very good security safeguards and granular permissions controls, a high degree of personalization, and customers speak highly of the responsive support team. Edmodo was the first of its kind, but is now seeing increased competition from the next two in this list.

Lore (Coursekit): Lore is at the newcomer to this arena, but is moving to the forefront rather quickly thanks to strong financial backers. It is “Course-centric”, in that each course has it’s own private “social network”. Users love its clean and elegant UI.

Schoology: Schoology combines some of the best elements of Lore and Edmodo. One of the big selling points is that unlike Edmodo’s “wall” which can get cluttered. Schoology has threaded discussion boards to make content easier to find. It also has better security and permissions granularity controls than Lore. Despite the lite/social nature of the service, Schoology bills itself as being able to perform full-blown LMS functions.

What to choose??

With all these options out there (and these are truly just a sliver of the pantheon of offerings), it is easy for education institutions to feel completely overwhelmed by the choices available. Perhaps this is natural given our open source leanings at Four Kitchens, but we believe that the best option for education institutions is the one that makes data exchange, interoperability, and connected systems most easy to achieve. The process efficiencies, cost savings, ease of administration, reporting that higher ed and K-12 institutions crave can only be realized when the systems work in concert. A comment made by one educator that I talked to should be of particular note to technical service providers; he said, “All these educational services and websites try to be software and lock you in. What I would REALLY like is for a way to make all these systems talk to each other. If you can do that, you’ve got a real winner!”

Date: Wednesday, February 27, 2013 - 17:00 to 18:00

Several organizers of the Downtown Los Angeles Drupal group are meeting for the year's first Downtown Drupal Governance Meetup on Wednesday, February 27, 2013 between 5-6pm.

In the spirit and tradition of our user group and events, this meetup is open to all Downtown Drupal members and is an excellent opportunity for anyone who's interested in getting involved or is just interested in observing our open governance model.

Join us in person at Droplabs or remotely via Google+ Hangout!

Agenda

Our agenda for this meeting is to review (and possibly publish) the proposed Downtown LA Drupal Governance policy:

   http://groups.drupal.org/downtown-los-angeles/governance  

If you plan to attend, please be prepared and familiarize yourself with both our group's mission at http://groups.drupal.org/downtown-los-angeles and our current governance proposal at http://groups.drupal.org/downtown-los-angeles/governance prior to this meetup.

Join Us on Google+ and Twitter!

To join the meeting, use the following URL:

   Google+ hangout: https://plus.google.com/hangouts/_/7378d9b61d65107cb08a67d67ef7e75fd8a2f67d
   Short URL: http://ex.tl/ZMW  

During the meetup, the event organizers will be monitoring Twitter for feedback and questions that mention @DowntownDrupal.

Location and Directions

This event is hosted by Droplabs (@Droplabs), a collaborative coworking space, classroom and hackerspace in Downtown Los Angeles.

   Droplabs
   651 Clover St.
   Los Angeles, CA 90031

We're quickly gaining a reputation for being the only coworking space around with a with a low-cost business model: come work here and use our tables, chairs, WiFi and conference room with a low, daily or monthly membership fee and only pay more for the extras, such as 24/7 access, equipment rental and a locker for your belongings.

Droplabs is in the Mission Junction neighborhood of Los Angeles at Big Art Labs, just 1 mile down Main St. from Philippes (the first-ever venue for Drupal meetups in Southern California!) and Union Station. We're one block west of The Brewery, the largest live-and-work artists' colony in the world.

Free parking in our large parking lot is first-come, first-served. After parking in the lot, follow the yellow signs that point to Droplabs. (If our lot is full, you can park for free on Clover St.)

Droplabs is a brief walk from the Main St. / Lamar St. stop on the the Metro Local 76 bus line. This is also the Lincoln Heights / Chinatown DASH stop.

To carpool or catch the Droplabs shuttle from Union Station, post below in the comments.

What to Bring

Just bring your laptop, your business cards or whatever else you need. You're also welcome to bring some light food, sodas or beers to share with others at the meetup.

Please note that our guest wireless network is limited to 1Mb per client, so bring your MiFi router or a phone you can tether with if for some reason you need a lot of bandwidth. Access to our high-speed network is included with a Droplabs membership.

About Downtown Los Angeles Drupal

The Downtown Los Angeles Drupal group regularly meets in and around Downtown Los Angeles, California. We organize a large number of weekly and monthly events on various Drupal topics, including the general Downtown Los Angeles Drupal meetup that has been meeting regularly each month since early 2010.

The Downtown area is the most active area for Drupal in the Greater Los Angeles Area and has seen hundreds of Drupal events, including job fairs, meetups and workshops, study group meetings, conferences about design and theming, paid trainings, FREE tutoring sessions from Drupal professionals and barn raisings to benefit non-profits and members of our community here in and around Downtown Los Angeles.

Attending Drupal events in and around Downtown Los Angeles is one of the best ways to meet and talk with other Drupaleros and we encourage you to attend as many meetings and special events as you'd like. Whether it's to find solutions to problems you've been having, sharing something you've learned or just meeting interesting like-minded people, the Downtown Los Angeles Drupal events are an essential resource for Drupal professionals and hobbyists alike.

If you aren't already a member of Downtown Los Angeles Drupal, it's easy to join our community. Our community calendar is on our "Events" tab on our home page at http://groups.drupal.org/dtla  

The Downtown Los Angeles Drupal group proudly participates in the California Drupal Travelers Program and can host businesses and community members who are visiting the area. Inquire within by contacting any of the Downtown Los Angeles Drupal organizers.

Tags:

• Meetup
• Planet Drupal

The best type of blog post is the type that leads to action.

It seems that my recent post Drupal Modules: Usability Starts With A Name seems to have done exactly that.

As a result of that post and the comments that followed (on this website and in the issue queue), I have renamed the Storm module to Project Management.

Project Management is now the name and the description of the module. A new user now knows the context of the module without any additional explanation.

I have wondered since whether it was the right decision. But I am reassured that there was unanimous support for this change in comments, and the number of people participating in the issue queue has increased significantly since the change.

You can try Project Management (still a work in progress for Drupal 7) on this demo site. A version is also available for Storm (the stable modules for Drupal 6).

This practical example is, I hope, a motivation for more module maintainers to reflect that "Usability Starts With A Name".

Category: WebsitesTags: Drupal PlanetStormProject ManagementusabilityDrupal

Writing engaging, reusable microcontent is tricky business. Whether you need titles, tweets, or summaries, consider the destination channels and the workflow.

Writing short bits of user-facing text -- microcontent -- is no picnic. Coming up with a punchy, attention-grabbing tweet is tough enough; writing a memorable 50 character title for a breaking news story can stress out even a creative wordsmith. It's like the writer's equivalent of Fitts's Law: the smaller the target, the narrower the margin for error.

In heavy-duty, reuse-oriented publishing systems, it's common practice to save several variations of an article's title and summary text. That gives writers some breathing room in more forgiving display contexts, but ensures they don't blow past hard limits for the short stuff.

We're currently working with a client on the nitty-gritty details of their new content model, and we're trying to iron out the best mix of fields to provide flexibility without overloading content authors. How many variations are enough? Karen McGrane's advice is simple and to the point: "As many as the writers will fill out, but no more." We plan to do some experiments with simple prototype interfaces to see what they're comfortable with, but before proceeding I did a quick review of the microcontent landscape to better understand the constraints of popular formats and channels.

From longest to shortest, here's the rundown:

• App.net post: 256 chars
• Twitter card summary text: 200 chars
• Facebook og:description text: 160 chars
• Google page description: 155 chars

One of the better features of the views module in Drupal is the ability to cache your view's output. This can come in handy when your view is doing a lot of computation. Caching your view will save your server a lot of unneeded work. One of the big current drawbacks of this feature is if you enable caching for your view and you have an exposed filter, you'll run into the following scenario:

User A enters a value for the filter

• Read more

Knowing what your customers are doing before spending money in your Drupal Commerce store can be valuable information for your business. It could help you create the shopping experience that meets the needs of your customers. With Google Analytics you can collect valuable visitor behavior information. Drupal Commerce is where the actual sale happens. In this tutorial I will learn you how to put those two together. It enables you to integrate Drupal Commerce order information with Google Analytics.

Configure the Google Analytics profile

First enable ecommerce tracking in your site's Google Analytics Profile. Learn how to do that in this Google Analytics tutorial on enabling ecommerce tracking. And while you're at it, make sure it reflects the right currency amount in that profile. 

Configure Google Analytics Module

Download and enable Google Analytics module. To allow Drupal Commerce order tracking you should at least enter the Google Analytics UA id at example.com/admin/config/system/googleanalytics. If you want to do more advanced things like for example 'user segmentation' or 'internal site search' tracking, have a look at this tutorial about configuring Google Analytics module.

Configure Commerce Google Analytics Module

Download and enable Commerce Google Analytics module. No configuration required. Yes, module maintainers rock. They are making this even cooler: Rules integration is currently in development. 

Configure Drupal Commerce product Titles and SKU's

Make sure your Drupal Commerce product titles and Stock Keeping Units make sense as they will be used in reporting. Note that Commerce product titles are a different thing than the titles of your product display nodes. If you're using Commerce Kickstart, have a look at this tutorial on how to change the product titles.

Test ordering Drupal Commerce products

Always be testing: place a few orders in your store, and check if they show up in your Google Analytics profile. Make sure you set the Google Analytics date range to include today - by default it doesn't include today. And make sure the order amounts, product prices, tax amounts and shipping cost are correctly tracked.

Testing orders without paying

When testing your ecommerce order analytics you don't want to actually pay for the order with money. Have a look at the Commerce No Payment module to be able to pay without really paying for it.

Tracking Email Metrics with Drupal Commerce

If you're interested in tracking eCommerce metrics regarding email campaigns, have a look at [my upcoming tutorial about Tracking MailChimp campaign Metrics with Drupal Commerce and Google Analytics].

Category: Drupal Planet Drupal Commerce Google Analytics

Episode Number:  108 Post Topics:  Drupal Contrib Drupal 7 Drupal Planet Site Administration

The Drupal 7 Coffee Module is a handy module that streamlines the administration of a Drupal 7 site by allow a quick search like mechanism for navigating to various administrative screens or for adding new content to your Drupal website.

In this episode you will learn:

• How the Drupal Coffee module can speed up your Drupal administration tasks
• How to use the Drupal Coffee module to navigate around Drupal administration pages

DDoD Video: 

read more

14 FebA distribution for Drupal User Groups II

I had an earlier blogpost about our work on a design and distribution package that Drupal User Groups all over the world could use. After having the concept refined and the wireframes ready, we went on with creating the design and organizing a code sprint to get things going.

Read more

Image Style Basics

Drupal offers the possibility to easily process images via image styles (formerly known as imagecache presets). In our current case of a photo heavy website we had to integrate a watermark image on all images supplied by the site. For this purpose we used the image style action Overlay (watermark).

The configuration of the style is really simple - but could be enriched with scaling and all other available actions.Read more

The TableField module implements a custom field that allows users to attach tabular data to any content page/entity type. Data can be entered into the table manually or imported via a CSV upload. The amount of rows and columns can be configured globally on an entity type or on a per node basis. The field can also be configured to allow users to export the tabular data as a CSV file.

In this tutorial, we'll create a Company content type and use this module to display opening times.

One of my main goals here at the DA is to communicate - A LOT - about what's going on. It's my intention to put a blog post up after every board meeting summarizing our discussion so that you get more than just the meeting minutes to go by. Well, today was my very first board meeting as Executive Director, and, well, the open meeting was REALLY short. Like under five minutes short.

Simplytest.me

• What is simplytest.me?
  • “simplytest.me is a website where you can quickly test out a drupal.org project online without messing around locally.
    There are about 20.000 projects and some of them fit better to your needs than others do, and simplytest.me helps to find the right one.”
• Who is behind the project? Is it just you, or a team?
  • “Most of the initial development was done by myself, but I got much support from my colleagues and also Stuart Clark helped me cleaning up some messes recently.
    The project itself is opensource and I’m generally happy about any feedback I get.
    Everyone reporting bugs or making suggestions is part of the team for me.“
• Is this just for modules? Or can you tryout themes as well?
  • “It’s pretty much for any type of project hosted on drupal.org.
    It works for drupal core itself since version 6, for modules, themes, and even installation profiles, or distributions as we call them now.”
• What’s the basic interface like? How do you test out a project?
  • “I tried to keep the interface as simple as possible. All you need to do is basically start typing the name of a project hosted on d.o, then some autocomplete suggestions will appear,
    which you can select the project from. You can alternatively directly type in the project shortname or even the number of a sandbox module.
    After you selected a project simplytest.me shows you the available and supported versions which you can select. Then just click on ‘Launch Sandbox’ and it mostly takes about five
    seconds and if everything worked out you will be redirected to your personal sandbox and you’ll have 30 minutes to figure out whether a project does what you need or not.”
• What if 30 minutes are not enough, can I get more time?
  • “For most modules 30 minutes should be enough but if you need more time, for example to check out commerce kickstart, you just need to register on simplytest.me and your
    sandboxes will automatically last one hour. If you still need more you can contact me and I’ll see what I can do.”
• What happens if there are dependencies?
  • “Resolving dependencies turned out to be to most annoying problem while creating simplytest.me.
    In good cases all dependencies are described in the .info file of a project and they can be resolved recursively without problems. But things get complicated when dependencies have
    other names than the projects shortname.
    For example if a project has ‘content’ as dependency, there’s pretty much no good way for a machine to figure out that it needs to download ‘cck’”
• What about third party libraries?
  • “Third party libraries that need to be manually downloaded are even worse than dependencies.
    I simply have to rely on the developers here to reference all necessary libraries in a proper .make file.”
• Is there more planned for the future?
  • “Yes! The most frequently requested feature is to be able to apply patches on the selected project. I also want to add some kind of statistics page. There are many other suggestions
    too, but I still want to keep the user interface as simple as possible.”
• Where is funding coming from?
  • “I was very happy that my companies CEO didn’t hesitate a second to sponsor some of my working time and even the first server for the project.
    After simplytest.me got a bit popular I soon got a mail from RealityLoop and they also wanted to sponsor a server.
    I’m really grateful for their support, especially because they really showed that they were interested in the project and it’s potential for the Drupal Community rather than getting
    customers on their website.”

Use Cases

• What are some use cases for Simplytest.me?
  • “The intended usecase for simplytest.me was to be able to quickly spin up a testing site and figure out whether a module has the functionality you need.
    But it’s really cool to see that people are using it as on-demand demo sites for their modules and themes, or even for their client presentations.”
  • Demo content (maybe install devel?)
• What kind of feedback have you received from people using the site?

Questions from Twitter

• Blue-Bag - @ModsUnraveled simplytest.me interview @patrickd_drupal great service! Any plans to allow >1 module selection?
  • "Yes! That feature was also requested very often. It’s definitely planned, though it’s not very easy to implement, so it will take some time."

It felt like yesterday when it was announced that Sydney would host the DDU in 2013 at the Melbourne DDU 2012. After the great camp that Melbourne community had delivered, I was inspired to volunteer with the local Sydney team in putting on the DDU in my own city. But what I didn't expect was that DDU 2013  was going to turn into a the first DrupalCon held outside the U.S and Europe. The conference was held in Coogee at the Crowne Plaza, overlooking the beautiful beach.

Magda

aGov is a Drupal distribution built to address the accessibility, security and design guidelines for Australian Government sites. In a previous blog, I talked about some of the benefits aGov has for public sector agencies trying to do more with less in the online environment. In this post, I'm going to show you are practical example of building a micro-site using aGov, to show you how easy, and quick, it is to get up and running.

We're going to be building a site for a government initiative, but you could easily use the same methodology for a smaller public sector agency, a special event, an informational site, or a minister.