Hello Drupal

Editor's Notes

• #2: Ideally you will have sent them the “before you arrive” activity- to make an account and site on DG. \nAs people come in, make sure they have done the “before you arrive” activity. If not, hand them their manual, and show them to fire up their browser and create and site on Drupal Gardens. This lowers the risk of sites needing to queue. \n
• #3: \n
• #4: This is a short introduction. Main purpose is to get familiar with the audience, and make sure they know what you’re going to do today. \n- Make sure people have their gardens site set up. If not, get them started in the manual.\n
• #5: This is a quick overview of what they will do today. Don’t dwell on each slide. Just go through quickly!\n
• #6: Point out that the schedule is in the manual, or if you have revised any of the times. \nGo over any pedestrian details regarding lunch locations, where to loo is, etc. \n
• #7: We’ll look at cases which demonstrate real-world examples of the same procedures you’re learning. \n
• #8: There are a variety of new features and functionality. \n
• #9: 1. Configure your site name and slogan. \n2. Create a static block of text.\n3. Add new content.\n4. Add a webform to collect information from visitors. \n5. If you have time, add a banner. \n
• #10: After this introduction section, the blue slides generally match to the “UNITS” in the manual. You can start a unit with a quick presentation and a demo if suitable.\n
• #11: Fill in information about your company!! Or ALT+TAB to your own site, or add in your own slides.\n
• #12: This slide left blank! Open up tabs in your browser of your own recent client projects and show of what YOU have been doing!\n
• #13: Please mention the training available. Mention how important feedback will be to us.\n
• #14: Ask about their previous experience.\nIf you have a small group, < 10 people, Have each person introduce themselves, and tell about a project they are currently working on where they think Drupal Gardens (or Drupal) may help.\n
• #15: \n
• #16: Do a check to make sure everyone has the right equipment. You may or may not be providing the environment for them. Make sure all the students have a local Drupal instance available and working.\n
• #17: If they haven’t done these things, point this out in the manual under “before we start” and get them on it. \n
• #18: Lots and lots of people have questions about what Drupal Gardens is, and they need a comparison. \nWe had to include these slides about the service as it left new users with many many questions!\n
• #19: We’ll be using a hosted version of Drupal. Drupal Gardens is simply, Drupal, but hosted so you you don’t worry about upgrades to software. \n
• #20: New users are often confused by this! \nDrupal Gardens has a selection of popular modules. But you can’t add your own. There are also small user interface differences, such as a “Save Draft” button. But if you like that, you can add that to your own site - because the modules are ALL open source. \n
• #21: Overall - the user interface looks almost exactly the same. \nWith Drupal Gardens, you get hosting, and you also get a “Help” link to a search tool, and a list of your sites. \nWhen you click on appearance you see the main differences. \n
• #22: This is only available in Drupal Gardens. You develop visual design using a themebuilder tool. This is not open source, and it’s one of the features that makes the service sticky.\nHowever you CAN export your site and themes.\n
• #23: You can export, but currently you cannot import a site into Drupal Gardens.\nOn your “my sites” list you can export and host anywhere, bringing your data with you. You can also duplicate a site to make a new iteration, or use a base site to replicate. \n
• #24: \n
• #25: Direct participants to open their manual to the Welcome section, and locate “Exercise: Change your site title”. \n
• #26: Direct participants to open their manual, and locate “Exercise: Change your site title”. The title of your site will appear in the title bar of your browser and in search engine results. The slogan will appear on the front page title bar, and under the heading of the site. What will you call your site?\n
• #27: \n
• #28: The Drupal community often uses “Lego bricks” as the preferred metaphor for what Drupal is. \nhttps://twitter.com/#!/tom_eric/status/26847650412 \n
• #29: The metaphor is useful because we can think of some systems working well out of the box. Yet if you want to customize them, it’s more difficult. With Drupal you can get more customization, but the individual pieces are more generic.\n
• #30: We can think of elements such as fields, content types and modules as individual components. The various distributions can be thought of as kits, with custom made components, with some assembly required.\n
• #31: Talk about what Drupal IS. \n
• #32: Drupal is many different things to many different kinds of organizations and companies.\n
• #33: Companies, museums and organizations such as the King Center use Drupal to maintain an online presence. \n
• #34: Drupal is a publishing platform. \n
• #35: Florida hospital uses faceted search to help patients find expert care. \n
• #36: Dev.twitter.com - used for discussions, documentation and knowledge sharing.\n
• #37: \n
• #38: \n
• #39: Drupal is widely used in academia as well. Both for online presence and as virtual learning environments.\n
• #40: \n
• #41: These sites for Warner music artists are built on Drupal gardens- they have a centralized way to manage many sites.\n
• #42: \n
• #43: Companies are building and hosting “site builder” services. \n
• #44: Digital agencies such as Commerce Guys can specialize in e-commerce, and released their code as open source. \n
• #45: \n
• #46: Compared to other CMS, especially proprietary and custom CMSs.\nWhile Drupal’s core modules are flexible, there are a range of contributed modules to extend to most feature sets you need.\n
• #47: Compared to other CMSs....\nYou can build on top of a flexible, well documented API to save yourself hours of coding from the ground up.\n
• #48: You can improve your client’s user experience with back end customization and themes.\nHere we see “workbench” which makes a more user friendly content administration UI. \nHere is also the Admin module which adds a sidebar and the Rubic admin theme.\n
• #49: Drupal does a few things out of the box...Menu system; Content type creation; User management; Taxonomy; Comments; search, content translation, etc etc... and more - in addition you can create unique functionality through coding... \n
• #50: Just check out the distribution packages which are specific products for a specific case. You can download them and have the beginning of your conference website, your online community or publishing platform.\n
• #51: Drupal’s community has evolved with mature, experienced agencies with specialization in both technical areas and verticals such as education, commerce, small businesses, and drupal-specific services. \nAs a service provider yourself, you can find potential collaborators to compete for larger projects. \nThis is also attracting many new clients with specific needs.\n
• #52: Drupal has a highly active community of contributors. Just in Feb 2012, Drupal surpassed 16k actively contributing Developers! That doesn’t count the many active users and advocates who help others. \n
• #53: Thousands converge for the conferences. Twice yearly in N. America and Europe, and soon annually in S. America. These show the combined numbers for the events. Went from 50 people in Antwerp in 2005, to averaging 4500 each year. At this time, we don’t know yet how big Munich will be!\n
• #54: There are DrupalCamps happening all over the world, all throughout the year with numbers from 60-400 people. Each week, the Drupal Dojo hosts a virtual session. And You can find weekly or monthly meet-ups on local Groups in your area. \n
• #55: There are bi-annual conferences, one in the US, one in the EU- and soon in South America. This is a place to hire or be hired, to learn, to socialise. GREAT PLACE FOR NEW DRUPALISTS!!\n
• #56: This is an administration tour. There are specific activities in the manual for this. You can also rush through this as a presentation if you don’t want to do the activities. Where this is an activity it says “Try this...”\n
• #57: Drupal plays well with others. PHP is pretty much the only requirement. \nDrupal can support other SQL databases, but needs additional support for noSQL databases.\n\n
• #58: The administration area is customizable. You can even change the way it looks or add your own administration pages.\n
• #59: There are basic content types, such as basic pages and articles. You will see how to make new content types. \n
• #60: The core block system has some basic layout and positioning tools. These can be extended with a number of other modules.\n
• #61: \n
• #62: \n
• #63: Drupal’s theme system is one of overriding output. A minimum theme can be done with just a CSS overrides. \nSeparation of business logic and display from data using the theme system.\n
• #64: This section is for a LESS technical audience. You can skip this if you don’t have that audience!\n
• #65: SKIP IF GROUP IS FAMILIAR WITH CMSs! Anyone remember “The Webmaster”\nFirst let’s look back for a moment to see the problem Drupal was originally designed to solve. Sites were mainly text and images, with a hierarchical site structure. Sites were assumed to be accessed mainly from their front pages, before powerful search engines. Site maintenance consisted of updating text pages. \n
• #66: SKIP IF GROUP IS FAMILIAR WITH CMSs!\nCan anyone think of why this might be a problem?\nDesign updates?\nUser generated content?\nWe may think of the original way websites were designed. All the data and design was kept in one file. Sites became increasingly complex to update and redesign with data and presentation trapped in one file. \n\n
• #67: SKIP IF GROUP IS FAMILIAR WITH CMSs!\nNow database driven sites could be built off of templates. Business logic separated from templating logic. Now you had users, logging in and interacting. \n
• #68: SKIP IF GROUP IS FAMILIAR WITH CMSs!\nSites are more interactive, social and media rich than they were even 10 years ago. \nExpectations are that the site is driven by users, not by site owners.\nIn addition, Open source became very important, in large part because now files could be transferred more easily w/o disks!\n
• #69: \n
• #70: \n
• #71: The Economist had to do a major migration from a previous content management system. They have massive amounts of content. \nAt 1) We see a simple list of the latest blog posts, their authors, and how long ago they were done. \nAt 2) We see a static block of links. This might be maintained through just editing the HTML of a block for example.\n
• #72: Previous: Cold Fusion on Oracle Data base\nComplex data structure; Complex joins for simple relational cases\n
• #73: The fulcrum of this project was the migrate module. Migrate allowed incremental synchronization between systems.\n
• #74: Direct.gov hosts all public services in one place. This is NOT a Drupal site.\n
• #75: They made a microsite to allow participants to share prototypes of mashups in a collaborative digital environment with the open source development community. The addition of non-personal government data sources gave the community a chance to innovate alongside the government. \n
• #76: These are the basic requirements - to allow developers to submit apps and for others to share ideas. \n
• #77: The entire submission form is the same kind of form they use for adding other content, like blog posts. This one is extended with custom fields. \n
• #78: Direct participants to open their manual, and turn to the exercises in Session 1\n
• #79: First, we’ll add a block. 2nd, we’ll position the block in the sidebar. 3rd, we’ll check to see the block.\n
• #80: When you get to the Block configuration page, also look at the other blocks were are available by default. These options appear depending on modules you have enabled, and how you configured modules. \n
• #81: We’ll add news items with an image, which show up in the news list. If you have time, you can challenge yourself by adding a basic page. This static page, is a different content type, and is not configured to display on the front page. Direct participants to open their manuals and try these!!\n
• #82: \n
• #83: Do reviews optionally, if you are doing the 3 hour version, or if you want to reinforce some concepts.\n
• #84: Introduce the client. And also click on the inspiration link to review a site for some ideas. Step by step tutorials to excite people about reusing cast off materials in creative ways. Contributors can apply to be “tutors” and write articles. Contributors can submit videos to demonstrate techniques.\n1. Elicit: How they’d make the slogan go to to the right? (Use CSS). \n2. Elicit: What content type is showing here? (A tutorial, but we only see the title and summary). \n3. How would they place this video and this photo of a user on the page? (They may not know this now, but pique their curiosity, and they will see more about this next. \n
• #85: \n
• #86: \n
• #87: In your mind, you may be thinking of a mental site map.... this model is so ingrained in us. Folders, documents... \nMake the document, add the content.\n
• #88: We tend to think this way- starting with the structure of the pages... \nDesign planning tends to focus on the front end - what is visible and visual. You may imagine this WHOLE page as one unit.\n
• #89: Then we think about how the content will fit in. We want to place the content directly. \nMaybe the top article is a featured article?\nMaybe the bottom ones are from specific authors or sections of the site?\n
• #90: You may have content appearing in different ways in different places on your site. \n
• #91: Instead, think Content first. Imagine your data storehouse of information. \n
• #92: Imagine if you had generic posts with a page title and body text. Your editors might put in any manner of content, such as text, images, location information, etc. \nIf you structure the content you have more control of what data gets saved when editors add content.\n
• #93: \n
• #94: \n
• #95: \n
• #96: Visit this site. It may look a little different from this image. Locate the poll block. \n
• #97: Enable the poll Module > Add a poll > Place block in the sidebar.\n\nThe twitter module probably works like this to. When you configure the twitter module, a block will be generated automatically. \n
• #98: Visit this site. Identify MENUS and BLOCKS\nLook at the components on the site. Some components come from modules: Poll module. Some might be custom blocks with HTML. \n
• #99: These are the same regions you see in your block display. Admittedly, this isn’t intuitive. There are additional systems which provide drag and drop control. Mention Panels.\n
• #100: All themes in Drupal Gardens have the same regions available to them. These are arbitrary. \n
• #101: Often people wonder how Drupal integrates with other systems\n
• #102: \n
• #103: The level of integration will make the difference as to what solutions you use. \n1. Follow module\n2. Core aggregator, feeds, and others. \n3. Twitter provides a “tweet” button, but there are other services such as Add this, AddtoAny, etc. \n4. The Twitter module allows a login.\n
• #104: Again it depends on what level of integration you want. Do you just need a Like button? Do you want users to see who else is logged in? Do you want to develop an application?\n
• #105: There are so many different kinds of integration modules, it depends on your own needs. \n
• #106: Open up the http://opensource.com website. Show it to people - have them visit it to think of questions. \n
• #107: OpenSource.com is a high volume news site, with participation from multiple authors, and users who can add comments, and have profiles. In this example we can see the same content rendered in different ways in different places. \n1) On the front page, the image is smaller. 2) We see a medium size image on the topic page. 3) We see the full page view of the article.\n
• #108: Each content type comes with two displays by default. However you can get more specific kinds of display by selecting fields. \n
• #109: You can configure a thumbnail to be, for example, 100 x 100 pixels, and it will automatically update the thumbnail throughout the whole site. Let’s look at this in more detail.\n(You don’t need to read the slide to them!)\n
• #110: First, you’ll extend your content type by adding an image field. This handles uploading the image and storing it. You will configure how many files per field, and where the image gets stored, and even a default image. \n
• #111: You’d also need to configure how the image is going to be processed. You can rotate, crop, scale, desaturate. Here is the UI for configuring media styles. \n
• #112: When you configure display you can add a view modes to configure. In this case, Full content and Teaser modes. \nThen you can select the “Image style” from the list of configurable options.\nWant MORE display modes? Use Display Suite. \n
• #113: \n
• #114: So now, when you look at a great site like London.gov.uk you can understand how they manage to show content in different places in different ways. \n
• #115: Direct participants to open their manual, and turn to the exercises in Session 2\n
• #116: The options available depend on what modules you have enabled and installed. \n
• #117: Do reviews optionally, if you are doing the 3 hour version, or if you want to reinforce some concepts.\n
• #118: Introduce the client. And also client on the inspiration link to review a site for some ideas. Explain, this is a website for a special bijoux museum. The site helps keeps repeat visitors coming back again, while enticing potential visitors to see what is on offer. \n- Elicit: How many content types can they see suggested here? Point out the tabs. (Exhibitions, interviews, pages.) Tease out that a listing page: “What’s on” might be different from a basic page “About us”. \n1. Elicit that the 3 “current” exhibitions display an image and a link, but no text. Draw out how this “teaser” mode may be configured, and how it knows which are “current”. \n2. Elicit that the buttons are probably just graphics and links in a static block.\n3. Elicit that this is a list of exhibitions which are not currently on. Elicit that this is a HTML list, and only a linked title.\n
• #119: \n
• #120: \n
• #121: \n
• #122: Contributed modules answer the question: Can Drupal do X? Most likely “There is a module for that.” \nModules extend the functionality of Drupal. These are some examples. \nFivestar for ratings, Date and Calendar for adding dates and displaying content in calendars.\nViews slideshow, or the “ShareThis” module which add quick links to social sites. \nYou could think of them as add-ons, or as plugins or extensions; or as applications which run on Drupal. \n
• #123: Modules extend the functionality of Drupal. You could think of them as add-ons, or as plugins or extensions; or as applications which run on Drupal. \n
• #124: Modules are mainly text and PHP files. And any supporting libraries, scripts, image or CSS files.\n\n(If anyone asks, this is Comment Allow Anonymous)\n
• #125: Drupal’s theme system. Control visual look and final place to alter rendering markup, separate from the data. Components include CSS files & PHP files with HTML. \n
• #126: Themes are text files and any supporting libraries, scripts, image or CSS files.\n\nTemplate files are a mix of HTML and PHP. \n\n(If anyone asks, this is Danland). \n
• #127: Drupal “core” is a set of scripts which handles users, content, the menu system, taxonomy, translation, search. \n
• #128: In your “sites” folder you add your alterations. This can be done with contributed libraries, modules and themes, or custom modules and themes. Let Drupal do the easy stuff, and spend your time doing the really tricky custom stuff. \nNow we’ll do some exercises to see how this works. \n
• #129: If there is one cardinal rule in Drupal, it is: Don’t hack core!\n\nSee the red X there? - Don’t be “that guy”\n\n
• #130: \n
• #131: Browsing through the module categories gives you a sense of the range available. Some are utility modules, some work at a system level, some at a user interface level.\n
• #132: You don’t want a specialized module for events, posts, member profiles - when you can leverage the existing fields system and views which you are already using on your site. \nA good example is the Event module which used to do one thing: add and display events. now it’s replaced by using several modules together. \nThis makes the solution more flexible.\n
• #133: Drupal used to have more “all in one” modules. Similar to a Joomla-approach.\nNow, developers collaborate on more abstract tools - to lessen duplicated effort and improve the over integration among modules.\n
• #134: Since Drupal 6 - Specific modules are being replaced by the combined features of more generic modules.\n
• #135: We’ll go into module selection in more detail. but emphasis here, as again, that each module must be maintained.\n
• #136: The indicators also listed in their manual.\n
• #137: Search for specific modules, and sort by compatibility.\n
• #138: Go to an example project page, show what is information is available on the project page.\nWe’ll look at 3 parts of a project page in more detail.\n
• #139: This information is at the bottom of the project page. Drupal is not backward compatible. What they can see from this listing? Elicit the major version update from 6.x-1.3 v 6.x-2.x. Elicit comparison of the -dev branch.\nThis is the Flag module.\n
• #140: Project information is a good indicator of health. \nCompare these two projects. What are some differences? \nElicit: Status, reported installs. One is a module one is an install profile. (First is Flag, second is Meetu.)\nJust because only two others use it, doesn’t mean it’s not a perfect solution for you.\n
• #141: Drupal is software which runs on a webserver. \nIt’s written in PHP, accessing data in a database like this one pictured here. \nIn the core folder, you’ll find a series of text files, such as PHP files, CSS and scripts. \n
• #142: You can search by version and see reviews here. \n\n
• #143: The similar modules review group on g.d.o might have comparisons available for you\n
• #144: This will take 10 minutes minimum.\nThis is an optional section of the presentation. Do this if you have people who have some HTML/CSS experience, or are front end people. \n\n
• #145: \n
• #146: Here is an example site with a customized theme. \n
• #147: Drupal Gardens has a managed theme system. This can be exported (and customized with a sub-theme).\nSo keep in mind it’s different in Drupal gardens.\n
• #148: A basic theme can be made with a simple .info configuration file, saved into a folder of the same name. \nIn sites/all/themes\nIn this case, the theme is “newlook”. \n
• #149: When you go to “Appearance” in Drupal’s admin area, you see the disabled theme listed there. \n
• #150: Enable the theme and set as default to see what happens.\n
• #151: As soon as you enable it, and view your site you notice something - a “blank” theme in Drupal doesn’t yield a “blank” site.\nOther CMS use tag-based templating so you have to pull in all the content. \nWordpress- a blank theme yields nothing. WordPress is a pull system, where you have to specifically put in tags into templates to see your site. \nDrupal on the other hand is a push system. With this system, you are overriding the output.\n\n
• #152: In this case, Normalize is a third-party CSS file. And the others are custom.\nYou can add in CSS files this way, as well as JavaScript. \n
• #153: The CSS files you added to the .info file, are pulled into the system.\n
• #154: As a final step you’ll make sure to “aggregate and compress” CSS files for performance. \n
• #155: The order of the regions as declared in you .info file will be the order in which they appear in your Blocks configuration screen.\n
• #156: \n
• #157: So far we’ve seen how a basic Drupal theme, even with an .info file inherits the templates of the core and contributed themes. A base theme inherits the template files, CSS and settings of an identified parent theme. \n
• #158: Many core modules include template files which define how Drupal is rendered. For example the USER module has a user-profile.tpl.php\n
• #159: This template renders the user profile.\n
• #160: \n
• #161: \n
• #162: \n
• #163: Based on the naming patterns you can make new templates to add to your theme. What do you think these templates would do?\nRefer to your manual for the key documentation on this.\n
• #164: \n
• #165: Caveats of what not to do... putting in SQL queries. Bad. \n\n
• #166: This will take 10 minutes minimum.\nThis is an optional section of the presentation. Do this if you have people who are developers/coders.\n\n
• #167: You need to know Drupal site building before you build modules. Reduce duplicated effort and increase the ease of upgrading and maintenance. \n
• #168: Mostly, end-users interact with the finished products. It’s important they get involved early. \n
• #169: Editors will be involved with moderating content, but also to some extent, even changing the layout. \n
• #170: About 80-90% of your work is configuration to create the end products. Selecting projects, configuring them.\n
• #171: And about 10-20% is going to be working with the platform to create custom functionality. \n
• #172: When you make a module you choose which events to interact with.\n
• #173: \n
• #174: This section is for a more technical audience. You can skip this if you don’t have that audience!\n
• #175: \n
• #176: This is one of the key principles of the Drupal project.\n
• #177: Minor updates are straightforward, go to the “Update tab” on your modules list. You will also see Themes here. \nFirst, download the updates. If they are doing the activities on Drupal Gardens, point out the upgrading is managed for them.\n
• #178: Now you have a new version of the code files in your directory. This next step runs any require upgrade scripts. This may mean changes to the database, so make sure you backup. \n
• #179: After you run the scripts, your site will be taken out of maintenance mode.\n
• #180: Both minor and \n
• #181: First, you’ll do research. Are the modules you need available? \nNext you’ll prepare and make a backup. When you perform the upgrade you’ll do this in phases, first upgrade core, then contrib. You’ll test and backup as you go.\n
• #182: This is sometimes a good thing. Drupal encourages module maintainers to eliminate waste of duplicated effort. Often they can pool resources. \n
• #183: \n
• #184: This company, Varnish Software, uses their site to generate leads. For example, 1) after you provide your contact information in a webform here, you get access to a whitepaper. \nAt 2) We see a list of topics for browsing content across the site. \n
• #185: Telenet Group is the largest provider of broadband cable services in Belgium. This is the self-support site for their services. They use Apache Solr to build indexes of content.\nAt 1) We see category blocks. These are generated through Views.\nHowever, at 2) We see “Also interesting for you” a list of related articles generated from the Solr index. This is selected on-the-fly to show related articles based on an index. \nThe most important thing is to help their clients find related information quickly.\n
• #186: Direct participants to open their manual, and turn to the exercises in Session 3\n
• #187: Direct participants to open their manual. Do the activity to enable a new module and add a webform.\n
• #188: \n
• #189: Do reviews optionally, if you are doing the 3 hour version, or if you want to reinforce some concepts.\n
• #190: 1. Elicit what this suggests: that editors look through dogs, and select specific ones. If you have a fast group, you might ask someone to search for a solution. After they understand the scenario, you can explain the Flag module. \n2. Elicit what this suggests: That tweets are slurped in. This could be an embedded widget from Twitter, or explain the Twitter module which brings in a feed. \n3. You can use this as a point of departure, and even talk about the things which they’d find if they clicked the “donate” button. \n
• #191: \n
• #192: You can skip this if you don’t think it’s appropriate. \n
• #193: Modules, themes and install profiles/distros are contributed and maintained by people who do this work on a voluntary basis. Of people who use Drupal - 0.05% of people are actually contributing to the project. Now we’ll learn a little bit more about the stories behind the projects. \n\nhttp://www.flickr.com/photos/ceardach/4550842375\nhttp://www.flickr.com/photos/ceardach/4551537132 \nhttp://www.flickr.com/photos/ceardach/4549904317\n\n
• #194: Open source is more than contributing lines of code, it’s also building relationships and negotiating with others. The more you do in the community, the louder the voice you get. Sometimes we use the phrase “scratch your own itch” and this is often how contributed modules start. Let’s look more closely. \n
• #195: Stella was a C/Perl/PHP software developer by day, making real-time financial transaction server software. She used Drupal on a personal sites she maintained for fun. She started with the avatar select module, and then took over the Lightbox 2 module to use on her photography site. She has co-organized local meet-ups and regional camps. There are many Drupal success stories like these. She is part of the security team. \n
• #196: So when you are in the issue queues for a particular module, think of people like Stella and Jacob. Both busy with their work, new companies or new babies, organizing local events and more. \nThere are many ways you can contribute besides code... forum help, issue queue triage, marketing, organizing events, donation, getting sponsorship.\n“Module developers are not gods- they are people like you.”\n\n
• #197: \n
• #198: This is DrupalCon in Brussels in 2005. (quickly to next).\n
• #199: The DrupalCamp recently in Dakar was about the same size.\n
• #200: And about the same size as this monthly Boston meet-up. \n
• #201: Cover this if you have a group of students or career switchers. \n
• #202: \n
• #203: There are many roles available. From site builders to coders, from visual design to systems administration. \n
• #204: This is a skills map for learning Drupal. It’s important that everyone knows the Green and Yellow stuff. Then move on to customizations. http://j.mp/drupalskills\n
• #205: Direct participants to open their manual, and turn to the exercises in Session 4\n
• #206: \n
• #207: In addition to the community events mentioned earlier... here are some resources we recommend. \n
• #208: Starting off at the documentation will cover most bases.\n
• #209: Since you’re starting out on Drupal Gardens, also check out the documentation on the service. \n
• #210: If you do purchase books, please do buy them from Drupal.org which gets affiliate bonuses from the purchases. \nD7 module development is a great resource if you are going to attempt custom coding. And the definitive guide is a good reference. It’s VERY big. Recommend to buy it as an e-book. \n
• #211: If you prefer videos\n
• #212: Drupal training by Acquia partners is competitively priced compared to other commercial training. You learn with subject matter experts. Please mention training to people for follow on! http://training.acquia.com/ (surprising that many people were coming to Hello Drupal and not hearing that it was available in many places!)\n
• #213: \n
• #214: Please give us your feedback before we wrap up. Put this address on the white board so they can still see the link as you answer questions. \n
• #215: \n
• #216: If you find you have extra time - direct people to this site to try and figure out how it was done.\n
• #217: \n