Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Aug 11 2022
Aug 11

In conclusion

The challenges of creating a great digital experience today are ever growing, and if you are looking for a more flexible, more customisable alternative to SharePoint, then a move to Drupal should certainly be considered.

Drupal is widely regarded as the world's leading open-source enterprise platform for building content-rich digital experiences. Its highly flexible, scalable and extensible nature enables organisations to build better sites and experiences faster.

Moving away from SharePoint may seem like an insurmountable task, but as this article shows, the challenges can be overcome and you need not remain stuck on SharePoint forever.

If you are considering a move to Drupal, then Annertech is an award-winning Drupal specialist digital agency that can guide you through the process, helping you define a clear strategy and enabling you to make a smooth transition. 

Jul 31 2017
Jul 31

On Friday, all the accepted sessions for DrupalCon Vienna were announced, and we are delighted to report that, once again, 5 of our 8 session proposals were accepted! With Acquia and Pantheon being the only companies receiving more acceptances, we are extremely proud of our achievement. It also means that given our size, Annertech has more speakers, per staff member, than any other agency in the world.

This is the second year in a row, where we have had 5 sessions accepted for DrupalCon, and, along with FreistilBox, are the only Irish web agency to be represented. Our sessions this year span a number of different tracks, namely Project Management, Site Building, Performance and Scaling, Front End and Core Conversations, and cover topics such as building multilingual sites in Drupal 8, project forecasting, debugging performance issues, component-based design/development, and accessibility. Congratulations to all our speakers!

Here's a quick run down of each session.

Live Performance Workshop: A top-to-bottom performance overhaul

Speaker: Anthony Lindsay
Track: Performance and Scaling

In this interactive workshop style presentation, we'll take a terrible, awful, broken sample site, look at all the nasty ways that its performance is terrible, and fix them, one by one. We'll get the audience involved with suggestions at every step of the way.

All examples will be taken from real life experiences, but no real sites will be harmed in the making of this demo/session.

Lessons Learned from Building a Large Multilingual, Multi-region Site in Drupal 8

Speaker: Stella Power
Track: Site Building

Having recently launched a Drupal 8 website with 13 distinct languages across 4 different regions, this session will take you from the basics of configuring your content to be multilingual through to making it localised in different regions and the various pitfalls encountered and lessons learned along the way.

Estimates are dead, long live forecasting!

Speaker: Mike King
Track: Project Management

In his session, Mike will outline the good, the bad and the downright wasteful aspects of estimates and how they’re used, before contrasting it all with the positive benefits of using forecasting to communicate a range of outcomes and how this can be communicated with the wider team. There will also be a follow-up BoF to share open source tools so that everyone can take home this new set of skills.

Back to the Future: No More Static Mockups!

Speaker: Mark Conroy
Track: Front End

This presentation will be an easy-going rant about how to make things better for frontend developers and will start by taking a look at Photoshop, SketchApp and InVision and how these tools fail to deliver (by building up expectations for clients and problems for implementers). We will then move on to talking about designing in the browser and how tools such as PatternLab and Fractal (basically HTML, CSS, and JS - the foundation of the web) can help solve these problems. Finally, we'll look at how we can (easily) integrate PatternLab with Drupal, thereby going 'Back to the Future'.

Core Accessibility: How are we doing, and what can we do better?

Speaker: Andrew Macpherson (and Théodore Biadala and Kristen Pol)
Track: Core Conversations

As we build Drupal websites, our exposure to the world of accessibility is often driven by the client or website owner. If they have accessibility requirements, we learn about these and try to meet their needs. Sometimes, it's driven by our own desire or need to make our websites consumable for more people.

In Drupal core, we've been making great strides incorporating accessibility best practices into the UX and markup. It’s not only important to help increase Drupal product adoption in some markets (e.g. the public sector) that have strict accessibility requirements, but accessibility is important to make Drupal sites reach the most people with varying backgrounds and abilities. This can be good for business. It is certainly good for our humanity.

Congratulations to Anthony, Stella, Andrew, Mike and Mark on their great achievement. We look forward to seeing these and all the other great sessions at DrupalCon Vienna in September. Hope to see you there!

Jul 01 2016
Jul 01

TL;DR

We were already prepared for a scenario like the Aberdeen Cloud breakdown, owing to our disaster recovery plan. Fortunately we didn't have to set it in motion. Each night we have a simple script which takes off-site backups of all of our hosted sites. We've made the source code available on github, so hopefully this will help others prepare for the likes of the Aberdeen Cloud implosion, and perhaps we can share ideas on how to improve each other's disaster recovery plans.

Our experience with the Aberdeen Cloud incident

We have a large number of sites hosted by various cloud services. Since autumn 2013, we'd mainly used Aberdeen Cloud, and in autumn 2015 we started to explore other options to see what else the market had to offer. Platform.sh was the one that we decided to give a serious test for new clients.

Soon after that, Aberdeen Cloud began to seem a bit flaky. Longer response times on support tickets. Solr services started to fail, along with random outages of various other services. We accepted that for a while, but after having lost and regained SSH access to all of our sites (including git and rsync), we eventually decided that enough was enough and we couldn't put our trust in them anymore.

We had to migrate everything to alternative hosting platforms. Given the similar price points and the fact that they seem well funded and offer excellent support, we decided on Platform.sh. And so began Project Exodus. 

Over the next three weeks we migrated over 20 sites to Platform.sh in a staged approach. I wouldn't say that it was a straight-forward process. Lots of clients had specific quirks to their setup. For example, some needed a PHPBB forum, others had FTP access for uploading files, some integrated with external systems that required firewall changes, etc, while others had custom .htaccess redirection rules that needed to be rewritten for Nginx. However, we were very lucky and had completed Project Exodus nearly a month before Aberdeen Cloud finally came tumbling down.

So what if you were not as fortunate as us, and still have sites whose assets are no longer accessible? Stuck in cyberspace, or maybe just plain deleted?

Well, I'm not sure there is a lot you can do. Maybe read Code Engima's blog post about the different things they've tried. However, to put it bluntly, it sucks! Enough said about the matter.

Now it's time to ensure you're never caught out again.

But what can we do to prevent this from happening again?

All companies probably have their own way to deal with this kind of scenario, but I'll tell you about how Annertech deals with backups and recoveries.

We have two sets of backups. A backup from each day, for each production/live/master environment, which is hosted by the cloud service. Then there is an off-site backup (again, daily) used for disaster recovery. The latter one is the important one in this scenario.

The idea is that even if Amazon (which hosts Aberdeen Cloud services) pulled the plug, we would still have access to our clients' data.

We have a server, hosted by a different company, that: 

  1. Pulls down a copy of the database, from every cloud-hosted site, every night, and saves it for four days, before it deletes it again.
  2. Runs `rsync` on every cloud-hosted site, to get an up-to-date version of the files folder, every night.

Sounds simple? It is. All it requires is that your hosting partner supports running Drush on your remote sites and you're good. If you run Drupal sites, and your hosting partner doesn't support running Drush on the remote sites, find somebody else who does. It's that important!

Regarding the code for the sites; we keep our source code repositories on dedicated git services. And, more than likely, we'll also have a copy or two on developers machines.

I'd like to show you the two backup scripts that I made, one for Aberdeen Cloud and one for Platform.sh.

The code is meant to work in our setup only, and is not (yet) generic enough to just work out of the box elsewhere. The release of the scripts is meant to give you a leg up and some inspiration. This is by no means the final end point for these scripts - we are continually evaluating and improving our system, and I look forward to hearing what ideas you have on where we could take it from here too.

The entire repository of code can be "stolen" from github.

When you have a disaster recovery plan you also need to make sure that it actually works. You can do this by downloading the latest backup from each of your sites once a month, installing and then testing them. I've tested a site, where the DB file was corrupt, but only for that site, so make sure that you test all of them. The setup of test sites can also be automated by a script so you don't have to setup 10, 50, or 300 sites and test each manually. Scripts are your friends. Make good use of them and have them do all the hard work.

Now, if you really want to push this further, you should implement a "Smoke test" in all of your installation profiles, so that you can trigger that to see if the site is alive; or perhaps tie it in with a Jenkins server.

If something is unclear, feel free to put a comment below. If you feel like this could be improved, feel free to contribute with a pull request. We are all ears.

Aug 25 2015
Aug 25

At Annertech, there are three things we take very seriously: website/server security, accessibility, and website load times/performance. This article will look at website performance with metrics from recent work we completed for Oxfam Ireland.

We use a suite of tools for performance testing. Some of these include Apache Benchmark, Yahoo's YSlow, and Google's PageSpeed Insights. Our favourite at the moment is NewRelic, though this does come at a cost.

Apache Benchmark (AB) is used for testing of the server application as well as load testing. It can identify whether or not your caching has been set up correctly and indicate what pages might be under-performing due to complex database queries.

However, it doesn't render the page or execute the JavaScript so it is not helpful for front-end performance testing. As on average 90% of a web page's load time is accounted for by the front-end, this is where we focus most of our performance testing efforts.

Areas we pay attention to when performing front-end testing include:

  • How long media assets take to load? This may indicate images in the content that are too large or too-high resolution. By reducing the file size of these images, we can improve the site load time.
  • Design assets, such as icons, can also be combined together in a single 'sprite', again reducing the load time as the number of files also reduces the time spent waiting.
  • Are there any scripts slowing down the site?
  • Identify which ones take longest and see if they can be tweaked or made asychronous.
  • Are there any CSS or JS files that can be compressed to make downloading and rendering quicker?

After we run our AB tests, we like to use services such as:

WebPageTest.org
SpeedCurve.com
Pingdom Tools
Chrome Developer Tools

Let's have a look at a case study of some of our recent work in this area.

Case Study: Improving the performance of oxfamireland.org

The Oxfam Ireland website was developed a number of years ago by Annertech, and while performance would have been important at the time, the reality is that a website can never be too fast. Oxfam asked us whether there were any marginal gains that were relatively quick to implement that we could deploy to the site.

Benchmark

If you can't measure it, your can't manage it. So the first step in improving performance is to see how the site currently stands.
There are lots of different ways to test the performance of a website, and for many years, the trusty Apache Benchmarking tool (AB) was our key weapon. This tool is still very useful in determining raw server performance for serving php pages.

However, in the case of Oxfam, we wanted something that was more relevant to real users. Enter "PageSpeed Insights".

PageSpeed Insights

Our first tool deployed was Google's PageSpeed insights. This is a free service run by google, which downloads, parses and grades a website's performance.

The key difference over AB is that browser performance is tested – so all the assets required to render a page – HTML, images, CSS, JavaScript, fonts – are downloaded, including those on third party sites.

PageSpeed insights runs a series of tests against the site, checking for various best practices, and returns a headline figure result.
This can be a bit skewed, as the result can be gamed a little. The actual figure can be improved by adjusting some items than have no real impact for the actual site under test.

Still – its gives us a grade, that we can aim to improve on.

The grade returned two different values, one for mobile and one for desktop. We ran the test against two key pages on the site: the homepage, and the "Get Involved!" landing page.

PageSpeed Insights report for Oxfam Ireland

WebPageTest

WebPageTest is another online testing tool, run by Patrick Meenan. While the UI might not be as nice as PageSpeed insights, the results returned are extremely detailed and very useful for in-depth performance monitoring and improvement.

In particular, the tests are run twice against the site, so any efforts made to leverage browser-side caching on subsequent page loads are measured.

For our purposes, we picked out 3 key metrics – SpeedIndex, Number of Requests and Page size. We aimed to reduce all of them. SpeedIndex is of particular interest. It is the average time at which visible parts of the page are displayed. From a user's perspective, this is a key value. There are other browser metrics that are measured, such as "DOM Content Loaded" and the "Onload" event, but SpeedIndex is really the best measure of "perceived performance" - as perceived by the end users.

What we did to improve things

Naturally a complete redesign/redevelopment was out of scope, and we're already using Drupal's inbuilt aggregation for CSS and JavaScript. The simplest tool at our disposal was the Advanced Aggregation module. However, this module isn't a straightforward 'set and forget' module, and takes some careful configuration and testing to produce the key results.

Our key objective was to move as much render-blocking JavaScript from the header of the HTML document to the footer. We also optimised the 'bundles' of CSS and javascript aggregated that are generated, and minified the javascript as part of the aggregation process.

How the numbers added up

After we had finalised our adjustments to the site, and verified the improvements on our staging infrastructure, the changes were deployed to the live site. As our focus was improving perceived speed, it was encouraging to see the significant improvement in the 'SpeedIndex' value.

On the Homepage first view, the value moved from 8373 to 7268, an improvement of 12.98% and on the repeat view, the value moved from 5487 to 4702, an improvement of over 14%.

On the Get Involved page, we managed an improvement of over 10% on the first view, and almost 3% on the repeat view.

The other benchmarked values weren't improved significantly on this phase of the work, and indeed, the page weight increased slightly. This is a feature of performance improvement where significant increases in one benchmark may come at the cost of another.

The chart below shows the load time of Oxfam Ireland's home page before and after optimisation of the site. It shows the results for both initial visitors and repeat visitors, the latter being where their browser has cached some elements of the page.

Oxfam Ireland website performance changes

Click here to read the full results of the process.

Ongoing

Since this work was carried out, a significant design update was applied to the homepage on the site. Using our predetermined benchmarking tools and measures, we were careful not to throw away our performance gains recently made.

The benchmarking process sets a line in the sand of where the website performance is currently at. Performance is now a key factor in any changes made to the website, and its has a significant effect on the bottom line.

Feb 16 2015
Feb 16

Why this blog post?

So what I want to contribute back to the Drupal community is an understanding of how Solr works, why/how it differs from Drupal Core Search module, and the benefits Solr has over core search.

Note: all Annertech hosting packages come with the ability for your site to use Apache Solr built-in.

The focus of this blog post will be for site builders. No code, and only a minimal amount of command line skill is required.

We will also look at the results from benchmarks which conclusively prove the performance benefit that can be obtained from using Apache Solr. And as we all know, performance benefit means more conversions and higher sales on your website/e-commerce platform.

My experience

I've used Solr in a variety of different projects over the past 4 years. Most recently on the Royal Museums Greenwich website where Solr is also being used to search non-Drupal content.

Documents

Slides and other documents that this post is based on can be found here. (This was originally a presentation at Drupal Open Days Ireland in 2014).

What is Solr

Solr is a blazingly fast open source enterprise search platform that can rival bigger name brands such as Google.

Solr is/has:

  • Written in Java
  • Easy to implement in a servlet container (Tomcat, Jetty)
  • REST-like API
  • Index content via XML, JSON, binary or CSV over HTTP 
  • Query it via HTTP GET and receive XML, JSON, CSV or binary results
  • Advanced Full-Text Search Capabilities

When do you use Solr?

There are overall scenarios where you should consider using Solr.

  • If searching is a major part/feature of your site.
  • If finding content is mainly done by searching and you would like to offer an auto complete (like when you are using Google) and a "Did you mean"-feature (also, like Google), Solr is the way to go.
  • If you need fine grained search control, like access control.
  • If you want to use faceted search, Solr really starts to shine.
  • If you have lots of content, which I'd say starts around 5,000 nodes, Solr's speed of returning results really overtakes Drupal's core search module.

Sound like a good fit? Here's the modules you'll need.

Here is a list of modules you might consider using when you want Drupal to connect to a Solr instance. There are a few more out there that might be the ones you need, but in my opinion, these are the best for beginners.

The Sarnia module is probably not needed for beginners, but the module is so cool that I had to mention it. It allows you to search in an index that was not created by Drupal. This means that you can have a 3rd party system indexing the content, and still display it in Drupal, using the views module.

Let's get started

Start a Solr instance

  • Hurry, get a copy of Solr.
  • Next, from your console, extract the downloaded package and enter the 'example' folder.
  • Type 'java -jar start.jar' and the server will start running.
  • You can verify this by visiting http://localhost:8983/solr/admin. You should see the Solr admin page.

The Drupal part

  • Enable the 'Search API' and 'Search API Solr' modules mentioned earlier. Follow the installation instructions carefully. Especially 'Search API Solr' which contains information on how to copy configuration files from the module folder into the Solr server. Remember to restart the Solr instance after you copy the new configuration.
  • Enable search_api_solr module
  • Go to admin/config/search/search_api
  • Add new server

Set up a new apache solr server

  • Add new index

Create new apache solr index

  • Configure what fields to index. These will be available from a the view used as a search page. 

Configure Drupal fields for apache solr search

  • Press the ‘Index now’ button. This will send the content to Solr instance.

apache solr indexing drupal nodes/pages

  • Have cake. This is a very important part! Do not skip under any circumstances.

After you install apache solr on a drupal website, you need to eat cake

The new search page

All you need to do now is create a view, using the new node index, set up your exposed filters (search for the fulltext field), and the fields to be displayed.

Visit your newly created search page, and watch Solr do it's magic.

Here's an example of a pretty simple search page, inspired by Drupal Core's search result page.

Apache solr drupal basic search results

Here is a more complex one, using some exposed filters, to narrow down the search result.

Apache solr drupal advanced search results page

The next image shows how a page, using the faceted search feature, could look.

Apache solr drupal faceted search blocks

But how does it perform?

DISCLAIMER: This is not a valid test, and the result is only used here to give a glimpse of what the difference might look like. The results will most likely look different on your environment. You can see the shell scripts I used to perform the test in the document folder I pointed out earlier. All tests were performed on a system where content was using cache.

I used a pretty standard Drupal setup for this test. A few content types, and some modules for SEO and some for making the content editing easier. What isn't ordinary about this Drupal installation is that is that it contains 70,000 nodes.

You can find the specs on the machine used, including server software, in the document folder I pointed out earlier, in the 'Search execution time' spreadsheet.

Apache solr drupal search result chart

The results are pretty clear: Drupal core's search takes longer as you put more words in the query. This may seem fair enough, as it makes the searching more complex. But when using Solr you can't barely see any difference at all. It doesn't really matter if you search for 1 or 6 keywords. The response time for a page is almost the same.

Apache solr drupal search result table

Super extra mega bonus!

I've put together a Drupal installation with a Solr bundle. Feel free to download it to test it yourself. Don't forget to read the README.txt. You can say thanks by leaving a comment below.

Download Now

About using Solr in a production environment

Solr for developers is quite easy to set up, but if you want to use it in a production environment, there are more things to take into account, such as security, performance optimisation, etc.

If you are not a skilled IT administrator I strongly recommend that you ally yourself with a team of experienced Solr maintainers/administrators, so they can help you set up things properly.

If you want to discuss Annertech helping you build an award-winning website, please feel free to contact us by phone on 01 524 0312, by email at [email protected], or using our contact form.

May 08 2013
May 08

Some upcoming events that could be of interest: Drupal Training, and DrupalCamp Dublin.

Annertech are presenting a public training day on 23rd May in Dublin. The courses presented will be:

Drupal in a day: http://drupalinaday2013.eventbrite.ie/
Drupal for developers in a day: http://drupalsitebuilding2013.eventbrite.ie/

Some upcoming events that could be of interest: Drupal Training, and DrupalCamp Dublin.

Annertech are presenting a public training day on 23rd May in Dublin. The courses presented will be:

Drupal in a day: http://drupalinaday2013.eventbrite.ie/
Drupal for developers in a day: http://drupalsitebuilding2013.eventbrite.ie/

Drupal in a day
Get a solid introduction to Drupal (6 or 7) in one day. Learn about the most essential features and concepts of Drupal through hands on activities. By the end of this day you will be familiar with Drupal terminology and be able to identify how many Drupal sites are constructed. You will know how to identify and choose modules to get the functionality you need.

Full details and signup at http://drupalinaday2013.eventbrite.ie/

---

Drupal for Developers in a day
Participants will be brought up to speed on Drupal and will be ready to tackle their own project. Learn how to manage media, build calendars and complex, dynamic queries of content by selecting and configuring the most popular modules.

Full details and signup at http://drupalsitebuilding2013.eventbrite.ie/

---

For either course, you'll need to bring your laptop, with Drupal installed, but don't worry if you haven't got that far. I'll be there on the day from 8am to help you get setup in advance.

If you feel that this could of interest to any of your colleagues, please forward it on.

[If you can't pay by Credit card, please contact us and we'll work something out]
---

DrupalCamp Dublin
Meet and learn from the best Drupal minds in Ireland bringing together developers, themers, end users and those interested in learning more about the platform. DrupalCamp Dublin takes place on the 24th and 25th May at the Guinness Enterprise Centre, right next to the Guinness Storehouse.

This is a free 2 day event - more details at http://www.drupalcampireland.org/

Mar 06 2012
Mar 06

We're often asked by clients and potential clients if there are any courses which will give them a good hands-on view of Drupal, what it does, and how to do it. And now we can say, yes there is.

Aside from bespoke training which we do on a regular basis for clients, we've decided to provide a public training day which is open to anybody. The course presented is Acquia's "Drupal in a day", and participants will receive a full course manual.

You'll need to bring your laptop, with Drupal installed, but don't worry if you haven't got that far. I'll be there on the day from 8am to help you get setup in advance.

You can signup here http://annertech.eventbrite.ie/

[If you can't pay by Credit card, please contact us and we'll work something out]

Nov 12 2011
Nov 12

A good night out at the Eircom spiders for two of the Annertech team this week. After Stella's little arrival came a bit early, a flu-ridden Edward was drafted in to fill the void.

Two of our clients were up for Awards. Trócaire had been nominated for two awards - best charity and best campaign, while runireland.com were in the running for the community award. Trócaire unfortunately left empty-handed this time around, but RunIreland were successful in their category.

It's a first Eircom spider award for Annertech - one of many to come hopefully!

Aug 08 2011
Aug 08

At DrupalCon Chicago earlier this year, Stella spoke with Kent Bye from Lullabot. They discussed recent improvements to the Coder module which can help you automate code reviews and upgrade your modules. They also discussed future plans for the module that will increase the number of security checks on Drupal modules.

The interview has now been released as a Drupal Voices podcast.

Apr 07 2011
Apr 07

I recently came across LiveReload and was impressed. Actually impressed is an under statement. I was amazed. LiveReload has really improved the way I work with css. As it says on its github page LiveReload is browser extension & a command-line tool that:

  1. Applies CSS and JavaScript file changes without reloading a page.
  2. Automatically reloads a page when any other file changes (html, image, server-side script, etc).

Getting it to work is straightforward. You simply need to download the LiveReload gem and install the extension/plugin in your browser of choice (as long as your browser of choice is Chrome, Safari, or Firefox!). When you have all that set up you can make edits to your files and have the changes display instantly in the browser. Even better if you are doing css and js changes the page will only load the css or js file. As such it is like using firebug to tweak properties except that you can do it in your IDE of choice.

I got this to work fine on Drupal 6 but I ran across a bit of a problem using Drupal 7. I was not sure what the problem was but eventually tracked it down to the fact that LiveReload will not work with css files imported using @import. As anyone who has been using Drupal 7 or following its development knows Drupal 7 uses @import extensively to get round the IE 31 link/style tag limit.

LiveReload has such a positive impact on my workflow that I was not going to let something small like that stop me using it! After a little bit of digging around I came across a solution to the problem.

Thanks to the new hook_css_alter it is easy to change the properties of a css file. So something simple like this

function MYTHEME_css_alter(&$css) { // Alter css to display as link tags. foreach ($css as $key => $value) { $css[$key]['preprocess'] = FALSE; } }

will render css links as a link tag rather than a style tag with @import. Perfect! It works because the default style if you do not preprocess is a
tag. You can dig into to drupal_pre_render_styles to learn about how css files in Drupal 7 are rendered.

Nov 30 2010
Nov 30

One of the biggest developments that happened at DrupalCamp Ireland in Dublin earlier this month was the decision to form an organization to manage the promotion of Drupal in Ireland.

Up to now, Drupal Camps in Ireland have really been organized by a loose group of individuals, and that worked pretty well for smaller events. However, Drupal Camp has grown up now and we have to pay people for venue costs, catering, while sponsors are looking for a little more accountability.

So we have put together a fledgling organization to manage all that stuff. Seven people were elected to the committee and in there in the think of things are myself Alan, as chair, and Stella as treasurer.

Its still early days, expect to hear more from Drupal Ireland in the future.

Nov 14 2010
Nov 14

Annertech are happy to announce that we will be sponsoring the upcoming Drupal Camp Dublin, taking place next weekend on the 20th & 21st Nov in Trinity College Dublin.

Edward O'Riordan and Annertech's own Stella Power are the main organisers of the event, which is aimed at both beginners and experienced developers alike. Stella will be talking on a few different topics including a session on Drupal Security and how to ensure you keep your site secure. Alan Burke will also be giving two presentations at the event, one on "How to use Git" and the other on HTML5.

The day before the camp (Friday 19th November), Alan will be giving the "Drupal in a Day" day-long training session. This is perfect for people completely new to Drupal or those who are still trying to find their way around. This training is designed to get you up to speed quickly and prepare you for the Drupal Camp the next day.

More information on the event, including accommodation and the venue, can be found at http://drupalcampireland.org

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web