Join Duane Cross, Managing Editor for NCAA.com at Turner Sports, for a view from the other side of Drupal. In his career of managing newsrooms, publishing content and covering breaking news, Duane has experience with many different content management systems. As managing editor at NCAA.com, Duane and his staff use Drupal to cover the regular season and postseason for Divisions I, II and III of the 89 NCAA championships as well as the BCS title game.
Newcomers can easily become confused by key Drupal terms that seem similar, but actually have important and distinct meanings. What's the difference between a Region, a Field, and a View, and what do you do with them? This presentation will cover the 11 key concepts that absolute beginners need to understand before starting work on a Drupal website. It may also help people who have been working on setting up their site but are still confused about some of the terminology. By the end of this session, newbies will be armed with an understanding of basic Drupal jargon and ready to learn more.
"Believe it or not there is life after the launch. During this session will talk about what you should be thinking about during the concept stage all the way to after build support. We will talk about version control, and yes you should be using it no matter how small the project. Another topic will be managing the wonders and horrors of custom code. Deployment strategy as well as support cycles will leave you wondering why you didn't think about them more before.
Toward the end, the Q&A time turned into more of a discussion. The mic couldn't hear any of it, though, so the audio kind of peters out at the end.
The usability of a CMS for its administrators and editors is closely tied to the semantic sense of the site build. Likewise, the maintainability (including ease of upgrade and feature addition) is greatly enhanced by intelligent semantics. By semantic site building in Drupal, I mean that all content types should be labeled and represent types of content, that user roles should be labeled and represent permissioned roles of users, and so on.
You've heard the buzz about Drupal. You know it's a thing and you're at this event. But why are all these people crazy about it are why should you care. We'll look at Drupal, how it is build, how it is used, as well as why it is popular and widely adopted. We'll also address some of the most common questions such as what are the benefits of using Drupal over some other popular systems such as Wordpress or Joomla.
In this screencast I talk a bit about Drupal as a community -- a bunch of people with a common interest/passion, doing good things together. Topics in this video:
* Why the community is so important for the Drupal project
* How the formal things around Drupal core are managed (including release cycles)
* How the formal things around contributed projects are managed
* How and where to learn more and take part of the Drupal community
* Some of the fun/crazy stuff people in the Drupal community come up with
This screencasts talks about Drupal being open source, and what that means. It discusses:
* What open source means, from some kind of legal perspective
* That open source is not necessarily without cost
* That open source does not mean 'no vendors'
* That Drupal is a collaborative effort, involving thousands of people working together
* That Drupal has no official certification system (for a reason)
This screencast introduces the Drupal content management system, and discusses it from a wider perspective. The video includes:
* Where and how to learn if Drupal is the choice for you
* Some sites using Drupal
* The most important advantages of Drupal
* Some criticism of Drupal
* That Drupal is more of a tool for building a CMS than a complete CMS in itself
In this video you'll learn how to use api.drupal.org the canonical source for information about Drupal's hooks, APIs, and code documentation in order to find out information about implementing a particular hook, making use of a particular function or library of functions, and even gaining a better understanding of some of the big picture concepts behind Drupal's code and APIs.