We've all heard Drupal can run every site from your personal blog to massive social networks. The framework is flexible and powerful enough to do anything. The showcase list of Drupal sites is impressive and growing. The community behind the magic continues to expand exponentially. The awards keep pouring in: Best Open Source CMS, Most Valuable Person, Top Innovator.
Enough Already.
James Walker
This session will take a good, hard look at everything that's wrong with Drupal. From the bewildering interface to the API's that aren't, it's time to take a step back from the Drupal love-in and take a serious look at what we've done. We'll cover all that's wrong about both the code and the 'community' behind it.
Installing and maintaining a Drupal website is a straight forward process, even if most of the work required has to be done manually. This is sufficient if you only maintain a single or small number of sites, but it starts breaking down when you maintain ten, a hundred, or even a thousand sites. Aegir is a new set of contributed modules for Drupal that aims to solve this common problem.
Adrian Rossouw
In this session, I will explain the Aegir system, how the different pieces fit together, and how it can help you or your business save time and money on tasks that are easily automated. Work smarter, not harder. To deploy a new site you simply have to create a new Site node. To backup or upgrade sites, you simply manage your site nodes as you would any other node.
Video not available
With Drupal 6, we started working on a better multilingual support for Drupal and now have better language management/negotiation and basic multilingual content and translation features working. However, some more work needs to be done in Drupal 7 to have a fully multilingual system. This session will discuss the current development status and what needs to be done to "fill the gap". We'll also have a discussion about our options and how we can make a fully multilingual Drupal happen.
Jose Reyero
Gabor Hojsty
Nedjo Rogers
Speakers
- Jose Reyero
- Gabor Hojsty
- Others
If you're coming to Drupalcon, don't miss out on the final "sprint" day on Saturday, a chance to sit down with your fellow Drupalistas and share your own contributions to help move Drupal forward!
At Drupalcon Szeged, we divided into several teams, including the documentation team, usability team, testing team, database team, "fields in core" team, and more. This year, we hope to continue in this tradition, so there's something for absolutely everyone, no matter what level of expertise. Pick a team that's talking about something that interests you, or bring your own itch to scratch!
Map/Reduce. Functional programming. Clouds. Document-oriented databases. Column stores. The future is coming and we should be prepared.
Karoly Negyesi
David Strauss
Agenda
We intend to talk about the next chapter in parallel computing, about the technology all of our sites are going to use in the next few years.
Goals
What should people come away from your session with?
Utter shock as everything they knew about computing is about to turn upside down.
Resources
What resources related to you session should people be aware of?
Each Drupal site is filled with opportunities to reach out and contact users. System messages, content notifications, mass mailings and newsletters, or online discussions and and two-way relays. This talk describes available solutions for sending, receiving, and tracking messages sent through a Drupal site for any purpose.
Allie Micka
Jeremiah Davis
Agenda
This session will move from GIS concepts to Drupal GIS practice. We will talk about the principles of storing, organizing, and searching geodata, the practical usage of geodata in Drupal applications, and how geographic functionalities are implemented by existing Drupal modules.
Allie Micka
Brandon Bergren
Jim Craner
Agenda
- With the advent of new geographic/mapping modules and tools, Drupal is increasingly effective at allowing users to associate their content with specific geographic locations and create compelling maps that display this association. We will discuss what types of problems can be solved by talking about information in terms of geography.
Over the past few years, we have come to rely heavily on web-based tools, such as blogs, forums, wiki, and other to collaborate, manage schedules, and share information. At the same time, chat (or Instant Messaging) has become one of the predominant forms of communication. One issue remains, however: the web based tools and chat don’t really “talk” to each other.
Darren Ferguson
Agenda
My talk will be focused on addressing that issue and harnessing the power of Jabber (XMPP) to enrich Drupal-based sites and application with real-time communication components. Likewise, I’ll show how web-based collaboration and information sharing add context to Instant Messaging.
Quality Assurance is Good for Business.
Drupal makes it easy to add powerful features to sites, whether through standard tools (CCK, Views, Panels 2, etc.) or through hand-coded extensions. Sophisticated modules and themes can provide great advantage or great frustration to the end user. We'll discuss some standard and not-so-standard techniques that help ensure the delivery of quality Drupal sites that are a joy to use.
Fen Labalme
Nathaniel Catchpole
Agenda
We'll touch on Selenium and Simpletest, but those tools are covered in greater depth in other sessions. Our goal is to take a more holistic approach, covering such topics as:
- Why is spending time (and money) on quality assurance good for business?
- Using source code control and multisite effectively to manage Development, QA and Live sites
Drupal 7 now includes the Field API which provides "CCK functionality" in core. The Field API supports attaching fields to nodes, users, remote data objects, and any other type of entity. This session introduces the Field API for module developers that want to define custom node content types and fields or field-enable their own object types.
Barry Jaspan
David Strauss
Agenda
- The definition of Field Type, Field, and Instance
- Bundles, and why they are (not exactly) like content types
- Using the Field CRUD API to define fields and instances
- Using the Field Attach API to field-enable an object type
Goals