Have feedback on the documentation? Post it in the Drupal Gardens user forums.
Drupal Gardens in Depth What is this document?....................................................................... 3 FIRST STEPS ....................................................................................... 4 Log in to your Drupal Gardens site ........................................................ 4 Getting around your site...................................................................... 4 The administration menu bar............................................................. 5 The shortcut bar .............................................................................. 5 Edit or delete shortcuts, add custom shortcuts..................................... 6 Administrative overviews - "by task" and "by module" .......................... 6 Your Drupal Gardens site is instantly visible online .................................. 8 Maintenance mode - Keep your site offline until you are ready to launch .... 9 Put your site into maintenance mode.................................................. 9 Access your site while in the maintenance mode .................................. 9 APPEARANCE - Drupal Gardens ThemeBuilder .................................... 9 What's a "theme"? What is "theming"? .................................................. 9 Open the ThemeBuilder ...................................................................... 10 ThemeBuilder Publishing Controls ........................................................ 10 ThemeBuilder Themes Tab.................................................................. 11 Themes Tab - Gardens themes ......................................................... 11 Make Your Own Custom Theme ........................................................ 12 Themes Tab - My themes................................................................. 13 Publish a Theme ............................................................................. 13 ThemeBuilder Brand tab ..................................................................... 14 Palettes - Set site-wide color palette .................................................14 Logo - Set site logo and favicon ........................................................ 14 ThemeBuilder Layout tab .................................................................... 15 ThemeBuilder Styles tab..................................................................... 17 Select page elements ...................................................................... 17 Font.............................................................................................. 18 Borders & Spacing - box model controls .............................................19 Background ................................................................................... 20 ThemeBuilder Color picker .................................................................. 21 Apply theme palette colors to page elements ......................................21 Add custom colors to your theme palette and apply them to page elements ....................................................................................... 21 Select and apply new color palettes to your theme ..............................23 ThemeBuilder Advanced tab - Add custom CSS to your site's theme .........26 Site elements not included in the ThemeBuilder .....................................27 Site name and slogan...................................................................... 27 Site information page - front page settings, site e-mail, error pages ......28 Headers, footers ............................................................................. 28 ThemeBuilder FAQ, Tips and Tricks ......................................................28 How do I insert a page-background image that doesn't move when I scroll down the page? .............................................................................. 28 Add a banner to the front page of your site only ....................................29 Add a banner image to the front page ...............................................29 Add text to the banner region........................................................... 30 Banner display settings ................................................................... 31
Give your front page and internal pages different layouts........................32 CONTENT .......................................................................................... 32 Content types - what are they? ........................................................... 32 Drupal Gardens standard content types and what they are for .................33 Add your first content - basic tutorials ..................................................34 Write a blog entry: ............................................................................ 34 Add an image to your content .......................................................... 36 Tag your node ................................................................................ 38 User comments and other settings ....................................................38 Publish your blog entry .................................................................... 39 Edit a node, change its teaser ... ......................................................... 39 Edit or delete your blog entry ........................................................... 39 Teaser and full node view ................................................................ 40 Change the teaser .......................................................................... 40 Show the full version of nodes instead of teasers ................................40 Make a static "about us" page ............................................................. 41 Make a contact page .......................................................................... 42 Add one or more contact categories ..................................................43 Add a "Contact" menu item .............................................................. 43 Add custom text to your contact form................................................45 Edit existing content, blocks or menus..................................................47 Content type settings overview ........................................................... 47 Menu Settings ................................................................................ 48 Book outline................................................................................... 48 Revision information ....................................................................... 49 URL path settings ........................................................................... 49 Comment settings........................................................................... 50 Authoring information ..................................................................... 51 Publishing options........................................................................... 52 Default content type configurations......................................................53 Article: information and settings .......................................................53 Basic page: information and settings .................................................53 Blog entry: information and settings..................................................54 Book page: information and settings .................................................54 Forums and forum topics: information and settings .............................55 Poll: information and settings ........................................................... 57 Custom and customized content types..................................................58 What is a content type? What are fields?............................................58 Why custom (or customized) content types or comments? ...................58 Data entry: Field Widgets ................................................................ 58 Fields ............................................................................................ 59 Add a custom content type (example) ...............................................60 Add fields to a content type or its comments (example) .......................64 Arrange fields on a content type or its comments (example) .................70 Manage content type display (example) .............................................71 Custom content type, creation, displays (example)..............................72 Add block and page views of a content type .......................................74 STRUCTURE....................................................................................... 74 Structural elements - overview............................................................ 75 Menus and navigation ........................................................................ 75 Make a menu link for new or existing content .....................................75 Blocks.............................................................................................. 76 What is a block? ............................................................................. 76 What is a block region? ................................................................... 76
Display your theme's block regions ...................................................77 Create and place a new block ........................................................... 78 Move a block.................................................................................. 79 Make a block only appear on certain pages.........................................80 Hide/Disable a block........................................................................ 80 Create dynamic pages and blocks - Simple Views...................................80 Build a view ................................................................................... 81 Edit or delete existing Simple Views ..................................................82 Create a link or menu entry to a view ................................................82 Organize your content in books ........................................................... 83 Add a content type other than "book page" to a book ..........................83 Book settings when creating content ....................................................84 Site-Internal Links - tips ..................................................................... 85 USERS ............................................................................................... 86 User registration ............................................................................... 86 User roles and permissions - access to functionality and content ..............86 User roles......................................................................................... 86 Standard user roles......................................................................... 87 User permissions ............................................................................... 88 Create custom user roles and assign them permissions...........................90 Give other users access to your site while it is in maintenance mode ........92 User avatars ..................................................................................... 92 Add or change personal user avatar ..................................................92 Default site-wide avatar................................................................... 93 Custom site-wide avatar .................................................................. 94 Site-wide avatar settings ................................................................. 94 LAUNCH YOUR SITE! ......................................................................... 95 Check, test double check. ................................................................... 95 Did you add custom CSS in the ThemeBuilder? Check your site in multiple browsers. ......................................................................................... 95 Create site-tester role, give access to offline mode and let test. ...............95 3, 2, 1 ... Launch! Take your site out of maintenance mode. ...................96 MODULES .......................................................................................... 96 Activate/Deactivate modules ............................................................... 96 Configure modules............................................................................. 96 Configure the Mailing list module ......................................................97 Configure the Comment Notify module ..............................................98 Registering and configuring custom domain names ........................ 102 Is my domain mapped correctly? Check your CNAME record ............... 102 Set up domain mapping ...................................................................... 0 Map a sub-domain ........................................................................... 104 Set up domain mapping on GoDaddy ................................................. 105
What is this document? Drupal Gardens in Depth - This manual, is a growing set of in-depth descriptions of Drupal 7 and Drupal Gardens functionality including: • Appearance: the Drupal Gardens ThemeBuilder • Content: creating basic content, content types, making static and dynamic pages • Structure: blocks, menus • Users: user access, role, permissions • and much more
If you'd like a quick overview of how to get started with Drupal Gardens instead, see the Drupal Gardens Quick Start Guide. If you don't find what you are looking for here or you have feedback on the documentation, visit the Drupal Gardens user forums.
FIRST STEPS Log in to your Drupal Gardens site User login block - The User login block is presented by default to all anonymous site visitors (those not registered and logged in to your site). If you visit to your site and find yourself logged out, the standard themes in Drupal Gardens display the "User login" block on the front page - enter your username and password to log in (in Drupal, the "theme" is the combination and placement of visual elements on your website). How do I login if the User login block isn't there? - If you don't see the User login block, you and your users can always log in at http://example.com/user (substituting the address of your site for "example.com") - you will be redirected to a Drupal Gardens login page. If you are already logged in, this URL takes you to your user profile page.
Getting around your site In Drupal Gardens documentation, navigation instructions are given as a "click path", that is how to click through the administration menu and tabs. For example - "Navigate to the Blocks page at Structure > Blocks" means: "Click Structure in the administration menu, then the link to the Blocks page."
"Navigate to the Comments tab on the Content administration page at Content" means: "Click the Content link in the administration menu, then the Comments tab"
The administration menu bar This navigation tool will take you to all the top-level administrative areas of your website.
• "Home" - link to the front page of your website. • Dashboard - Opens the configurable site dashboard. By default, there is a link to your Drupal Gardens site management page on your site dashboard. You can customize this page with useful dashboard widgets. • Content - Browse, list, add and filter content, comments and media. • Structure - Manage the "structural" aspects of your site, including blocks, menus, content types and more. • Appearance - Opens the Drupal Gardens ThemeBuilder. See below for more information on the ThemeBuilder. • People - List, filter and manage user accounts: block and unblock users, add and remove user roles, cancel user accounts. • Modules - Activate and deactivate specific functionality on your site. • Configuration - System, user, format, date and many more site settings. • Reports - Information on your site's status, visitors, page visits, visitor- and search statistics, activity logs and more. • Help - Links to standard Drupal 7 help pages. These pages contain valuable information relevant to configuring, understanding and running your Drupal Gardens website. • Other links: ◦ "Hello username" - Link to your user profile page. ◦ Log out - Logs you out of your Drupal Gardens site. ◦ open/close shortcuts (small triangle at top right) - This link expands and collapses the customizable shortcuts bar. The shortcut bar In Drupal Gardens, you can make your own, personal navigation bar with links to the pages you need to visit most!
• Add a shortcut - Any page with a small "+" plus sign next to the page title can be added to the shortcut bar:
• Remove a shortcut - Any page already in the shortcut bar can be removed by clicking the "-" minus sign next to the page title:
Edit or delete shortcuts, add custom shortcuts • Edit or remove shortcuts - Navigate to Configuration > Shortcuts, then click the "edit shortcuts" link at the top right corner of the page (or click "Edit shortcuts" on the shortcut bar itself) to edit the current shortcut set. On the "Customize shortcuts" page you can add, remove and modify shortcuts from the currently used shortcut set. • Custom shortcuts - Click "Add shortcut" on the Customize shortcuts page to add completely customized shortcuts to any URL on your site. • Custom shortcut sets - Add and configure shortcut sets adapted to the needs of different tasks and user roles. Click the "New set" radio button, enter a name for the set and click "Save configuration". ◦ Edit custom shortcut set - Any shortcut set selected on the shortcuts page can then be edited by clicking the "Edit shortcut" as above. ◦ Switch between shortcut sets - Any user with the "Select own shortcut set" permission can choose between available sets.
Administrative overviews - "by task" and "by module" If you click the "Dashboard" link at the top left of any administrative page or the administrative menu bar, you will be taken to the dashboard, a customizable site management page on your site dashboard. The dashboard also offers "by task" and "by module" administration tabs.
Administer by task - Your Drupal Gardens site's administration organized on the same basis as the administrative menu bar: by subject areas such as people, configuration, structure, and so on.
Administer by module - Your site's administration broken down by module. This is a great way to get an overview of each of your modules' functionality, its permissions, configuration and so on.
Your Drupal Gardens site is instantly visible online Note that any and all changes you make to your site are visible online unless you move it into maintenance mode while you are setting it up. See Maintenance mode for more information.
Maintenance mode - Keep your site offline until you are ready to launch Drupal's maintenance mode exists for when you need to keep your Drupal Gardens site private and offline for non-authorized visitors before it is ready to launch or later when you add new features or make other changes. Put your site into maintenance mode In maintenance mode, the site maintainer (the user who created the site) and any other users with the "Administrator" user role will be able to access and modify your site as usual. All other site visitors will see the message you enter on the maintenance mode page. • Navigate to the Maintenance mode page at Configuration > Maintenance mode. • Check the check-box labeled "Put site into maintenance mode". • Edit offline message to be displayed to site visitors while your site is offline as needed. • Click "Save configuration". To put your site back online, un-check the maintenance mode check-box on the Maintenance mode page and click "Save configuration". Access your site while in the maintenance mode Site owner and administrators can always log in - The site owner (the person who registered and first logged in to a Drupal Gardens site) and any other users with the "Administrator" user role can access and modify your site as usual while it is in Maintenance mode. Log in at /user - To log in during Maintenance mode, navigate to the /user page in the browser at http://example.com/user. You will be redirected to a login page. Give other users access to your site - If there are other users working on your site with you, see Give other users access to your site while it is in the maintenance mode for instructions how to allow them to access your site. back to top
APPEARANCE - Drupal Gardens ThemeBuilder What's a "theme"? What is "theming"? In Drupal, the "theme" is the combination and placement of visual elements on your website; the arrangement of blocks in various regions, different layouts on different pages, the selection of colors, fonts and graphics. In Drupal Gardens, the ThemeBuilder lets you choose and customize your site's look directly in your browser.
The Drupal Gardens ThemeBuilder - The Drupal Gardens ThemeBuilder gives you easy to use, yet powerful theming tools so you can give your Drupal Gardens website its own gorgeous look in minutes. You can use the themes that it comes with as is, tweek them a bit, or fully customize them to create a unique look. Your Drupal Gardens themes are fully compatible and exportable - In the back end, Drupal Gardens combines your styling choices and any image files you upload into valid CSS and fully exportable and compatible Drupal themes that you can use on any Drupal 7 website.
Open the ThemeBuilder To get started working on your Drupal Garden's site's theme: • Make sure you are on a public-facing page or your website - that is, a non-administration page. If you haven't created any content or other pages, this means the front page. Click the "Home" breadcrumb link click to get there. • Click "Appearance" in the administrative navigation bar to open the Drupal Gardens ThemeBuilder
ThemeBuilder Publishing Controls The right side of the ThemeBuilder control bar contains controls for publishing changes to your site's theme, changing which theme is published, and opening and closing the ThemeBuilder itself.
ThemeBuilder publishing controls, from left to right: • Undo/Redo - Undo and redo changes to your theme going back to the last time you saved your theme. • Export - Export your entire theme, CSS, images and template files for use on any Drupal 7 site. • Save - Save changes to a custom theme. This clears the "undo/redo stack". You cannot undo/redo beyond a save point. • Save as - Save a new copy of the theme you are working on under a different name. • Publish - You can work on new themes for your site in private without affecting what site visitors see. No changes you make to any theme in the ThemeBuilder are visible to site visitors until you publish that theme. When your changes are ready to go live, simply click publish. ◦ If you have been making changes to a default Drupal Gardens theme, you will be prompted to name it and save it as a custom theme of your own before you can publish it. • -/+ - Minimize/maximize the ThemeBuilder while working on your site's appearance. Get the ThemeBuilder temporarily out of the way without having to close it or save changes to your theme. • X - Close the ThemeBuilder - To reopen it, click "Appearance" in the Administration menu when you are on any non-administrative page of your website. • Above the controls - The name of the currently selected theme (not necessarily the published and publicly visible theme) is displayed above the controls.
ThemeBuilder Themes Tab
Themes Tab - Gardens themes Your Drupal Gardens website comes with a number of preconfigured default themes. You can publish your site using any one of these or use them as a starting point for a custom theme of your own. To change your site's appearance, select a theme from the Themes tab and click "Publish" to make it your site's live, public theme. You'll be asked to name your theme; then it will be saved and published.
Make Your Own Custom Theme • Select a standard Drupal Gardens theme to use as your starting point. You can change every aspect of it (column layout, colors, background images, fonts, etc.) to suit your needs. ◦ "Broadway" and "Minima" are 2- and 3-column themes respectively by default. These themes are pared down to the bare essentials and good if you want to design your site's look more of less from scratch. ◦ "Sparks" and "Kenwood" offer a little more structure, a defined area for a banner header on your site, and the main menu - your main site navigation, see Structure > Menus - below the banner image. ◦ "Sonoma" and "Campaign" have the main menu at the top of the page and show a little more of the potential built into all the Drupal Gardens themes. • Click "save as" - You will be prompted to give the new theme a name. • Draft mode - Your new theme, it will be in draft mode until you save it and click "Publish", making it your site's public theme. While a theme is in draft mode, only you can see it and any changes you make to it.
• Click "Publish" to make it your site's live, public theme.
Your saved custom themes, published or not, are all available to you under "My themes" on the ThemeBuilder Themes tab.
Themes Tab - My themes Once you have saved a new theme, it appears under "My themes" on the Themes tab and can be used as the public face of your website. All of the themes in "My themes" can also be copied ("save as") and used as starting points for new themes, just like the standard Drupal Gardens themes.
Publish a Theme You can work on new themes for your site in private without affecting what site visitors see. No changes you make to any theme in the ThemeBuilder are visible to site visitors until you publish that theme. When your changes are ready to go live, simply click publish. If you have been making changes to a default Drupal Gardens theme, you will be prompted to name it and save it as a custom theme of your own before you can publish it.
ThemeBuilder Brand tab
Palettes - Set site-wide color palette A selection of color palettes you can apply to your current theme. If you select a new palette, your theme's standard colors will be replaced by those of the new palette. Any custom colors you have created remain unchanged and available to you in the "Custom" section of the color picker on the ThemeBuilder's Styles tab.
Logo - Set site logo and favicon Set your site logo and favicon here. Site logo images will be uploaded at their original size - They appear in the header region and you may have to adjust the size of your logo to make it fit. Note: the header region's height changes to match the height of its background image (see: ThemeBuilder Styles tab - background) if that image is taller than the default header height. This allows you to customize the height of the header to fit a tall logo image by using a taller header background image. Site favicon images (the little graphic that appears on browser tabs to distinguish your site from others) are automatically re-sized on upload to a standard size and format.
ThemeBuilder Layout tab
Select the ThemeBuilder "Layout" tab - You can select from several one-, twoand three-column layouts and apply one to the page you are on only or to your whole site. Choice of column layouts:
The current main layout of your theme is labeled "Applied to all pages". You can apply a layout to any individual page or your whole site. See: ThemeBuilder FAQ, Tips and Tricks for how to apply different layouts to your front
page and internal pages on your site.
Preview a new layout by clicking it. Apply the layout to your whole site or only the page your are viewing.
Cancel the layout preview without applying it to any page by moving your pointer over that layout and clicking "cancel":
ThemeBuilder Styles tab
Select page elements To modify a page element in the ThemeBuilder, you need to select it first. The selection process allows you to refine your selection until you are certain your changes will only be applied to the exact element you intend. Choose an element - Move your pointer around the page while you are on the ThemeBuilder Styles tab. When you are over page elements that you can select, a red dotted border appears around them:
Select an element by clicking on it. When selected: • It will be highlighted with a blue background • Its selector chain will be displayed in the arrow-shaped boxes along the top of the ThemeBuilder • An exact description of the selection will be displayed right below the selectors (this description will be updated as you refine your selection as described below).
Refine your selection 1: multiple option drop-downs - Any element in the selector chain displayed with a small triangle next to its title contains multiple selector options (usually levels of selector specificity or refinement) that you may choose from.
Refine your selection 2: applied selectors - Some elements in the selector chain may appear in light gray. These elements may be used to select the element you have chosen, but are not being applied in the current configuration. Applying or removing elements in the selector chain may increase the specificity of your selection or change the element selected all together. If changes you make to the selector chain end up selecting a completely different one to the one you intended, start over by clicking the page element you intend to change.
Font Set the font characteristics of any page element. • Select a page element (see above) • Font - "auto" selects the default font of your theme • Format ◦ Font size - Click and drag the number ◦ Font size calculation - Select px (pixels) or em (percentages) from the drop-down ◦ Boldface and Italics - click the respective buttons
◦ Color - Click the color sample box to open the color picker
Borders & Spacing - box model controls Set the margin, border and padding of any page element. • Select a page element (see above) • Margin and padding - Click and drag an edge or a corner of the margin or padding layer of the box-model-representation. Dragging an edge changes the side you select. Dragging a corner changes the both sides it touches simultaneously.
• Border style and color - Choose from the CSS border styles listed in the drop-down. Click the color sample box to open the color picker.
Background Set the background color and/or image of any page element. • • • •
Select a page element (see above) Change the background color - Click the color sample box to open the color picker. Change the background image - Click "Browse" to upload an image. Repeat - Background images can be placed once or set to be tiled (repeated). This is especially useful for smaller background images and textures. The four tiling options are: ◦ Repeat horizontally and vertically ◦ Repeat horizontally only ◦ Repeat vertically only ◦ No repeat • Scroll - Background images can scroll with the page or be fixed (the content will scroll over the background) Tip - Try combining a background image with some alpha transparency or translucency with various background colors for spectacular results.
ThemeBuilder Color picker This powerful tool allows you to control the colors of your site's theme: apply colors from your theme's standard palette to any page element and select new colors, add them to your custom color palette and apply them to page elements. Apply theme palette colors to page elements • Select any page element while on the ThemeBuilder Styles tab. Its color will be displayed in the color sample square. • Click on the "Color sample" square will show the color currently assigned to that element. Clicking on another color from the palette will apply the new color to that element.
Add custom colors to your theme palette and apply them to page elements • Select any page element while on the ThemeBuilder Styles tab. • Click the color sample square next to "Color". This opens the color picker, displaying your theme's standard color palette on the left and your (empty in the screenshot) custom palette on the right.• Click "+" to add custom colors - click the plus sign to add custom colors.
• Current color displayed - The color tool expands to show you the full color picker with the element's current color selected:
Pick a color - by moving the spectrum slider to the desired color range and click in the hue window to select the specific color. Apply color to selected element and add to custom palette - Click "Add" to add it to your custom color palette and apply it to the selected element.
Find custom hex color codes - Your custom colors' hex and RGB codes are displayed in the color picker. You will need if you want to use them in custom CSS rules on the ThemeBuilder's Advanced tab.
Select and apply new color palettes to your theme See a selection of color palettes - Click the color picker color palette tab on the right side of the color picker to see a selection of color palettes you can apply to your current theme. Replace your theme's color palette - If you click on a different palette, your theme's standard colors will be replaced by those of the new palette. Custom colors you have created remain unchanged and available to you in the "Custom" section of the color picker.
Color palette examples Standard Sparks color palette - Here is the Drupal Gardens standard theme, "Sparks" using its standard color palette and with the "Sonoma", "Sprout", and "Sunflower" color palettes applied:
Sonoma color palette applied to the Sparks theme:
Sprout color palette applied to the Sparks theme:
Sunflower color palette applied to the Sparks theme:
ThemeBuilder Advanced tab - Add custom CSS to your site's theme
Add custom, valid CSS styles or selectors to your site theme in the CSS pane that are not available using the ThemeBuilder controls. Theme color cheat sheet - You can add or change CSS rules and be sure you are using the colors of your current theme by copying them from the hex codes cheat sheet on the right of the page.
To add CSS that includes a custom color you have chosen with the color picker, open the color picker, click the "+", then select your custom color to see its hex code.
Site elements not included in the ThemeBuilder Site name and slogan • Add or change the name of your site (not its URL) and its slogan, at Configuration > Site information.
• Theme display - The site name and slogan's display in your site theme can be activated or deactivated with the "Show ..." check-box below each entry field. You may want to hide them if your site logo graphic contains your site's name, but there is a good reason to have these set nonetheless: • Browser display - Even if you have hidden the site name and slogan in your site theme, they will still be displayed in the title bar and/or tabs of most browsers.
Site information page - front page settings, site e-mail, error pages
• • • •
On this page, beyond the site name and slogan, you can also change several other aspects of how your site appears to visitors: Front page posts - If you have a blog-style site using the standard front page configuration (by defining the "Default front page" to be "node" - see below), this sets how many blog entries and other content will be appear on the front page. Site e-mail - The "from" e-mail address on e-mail sent your your site. Default front page - You can set this to be to any page or URL on your site. The default setting is "node", which automatically makes your front page a "river of news" - displaying front page content in reverse chronological order. Set error pages - You can create custom pages to be displayed for 403 (access denied) and 404 (page not found) errors. Any URL on your site can be displayed. Leaving these blank will display standard messages. Headers, footers Blocks and regions - Drupal Gardens' themes come with various regions, including those for headers and footers. To add a header or a footer, you need to place a block in an appropriate region. You can place existing blocks in regions or make new custom blocks (for example: disclaimers, copyright notices, contact information, etc.) and place them in the various regions. You can also select which pages the blocks should and should not be displayed on. To add a simple custom block, navigate to the Blocks page at Structure > Blocks, click "Add block" and add a description, title, body text and display region on the block creation form. See the blocks section for more information.
ThemeBuilder FAQ, Tips and Tricks How do I insert a page-background image that doesn't move when I scroll down the page? • • • •
Open the ThemeBuilder. Select Background on the Styles tab. Select the page background by clicking it. If you need to add a new background image, click "Browse" and upload a new image. • Click the "No scrolling" selector under "Scroll".
Add a banner to the front page of your site only You can add one or more blocks that will only be displayed on the front page, or on selected pages of your choice. You can use this feature to embed ads, images, or other specific content. For example, your front page might feature a banner image and a welcome message, while your blog or news page might contain links to contests, your photos or other content.
Add a banner image to the front page • Open the ThemeBuilder • Go to the Styles/Background tab • Select the banner region
• Click "Browse"
• Upload your banner image
By default, the "banner" region only appears on the front page of your website, not on internal pages. Here is a blog page from the same site:
Add text to the banner region Text added to the banner region will also only appear on the front page by default: • Navigate to the blocks page at Structure > Blocks • Click "configure" next to the banner region • Add a title and text using the WYSIWYG interface
Banner display settings • Select a region for the block to be displayed in - you can place any block in any available block region. The image below shows the banner placed in the "Banner" block region. • Region <none> - This hides the block from display completely. You may "reactivate" a block at any time by assigning it a block region on the Blocks page or on its editing page. • Front page only (default setting) - With the "Only the listed pages" radio button selected, <front> displays the block on your site's default front page. If you have set a custom front page, you will need to enter the appropriate URL. • Every page but the front page - Changing the setting to the "All pages except those listed" radio button would cause the block to be displayed everywhere on your site except the front page. • Custom pages banners - You can create custom banners (and other blocks) for different sections of your site by creating multiple, custom blocks, applying them to various pages and sections of your site using these page visibility settings. • Save the block
Give your front page and internal pages different layouts • Open the ThemeBuilder. • Click the Layout tab. • Select internal layout - Click the layout you want for your site's internal pages and click "All pages" to apply it to your whole site. • Select front-page layout - Navigate to your site's front page (click the house symbol on the far left of the administration menu), select the frontpage layout you want and click "Just this page". • Voilà! Your front page now has a different layout from the rest of your site. back to top
CONTENT "Content" is the information in a Drupal website that is presented to its users. Drupal's fundamental unit of content is the "node". Drupal Gardens come with five standard, preconfigured types of nodes you can create, called content types.
Content types - what are they? A content type is a standardized data model – a collection of attributes, called "fields", that make up any given node (Drupal's basic unit of content). Drupal nodes are always of a given content type.
Different content types are created with different functions in mind and therefore have different sets of fields. For example, the Drupal Gardens standard content type "Blog entry" is made up of three fields: title, body and tags. You can customize the existing content types or create new ones for specific purposes. For more information, see: Custom content types. Site administrators can edit content types' standard settings and define custom content types at Structure > Content types.
Drupal Gardens standard content types and what they are for Drupal Gardens comes with a set of standard content types. Each one has a set of default behaviors that make it suited to a particular purpose. The default settings can be changed on an individual, per node basis or globally for all nodes of a content type. For example, Article nodes will always appear on your front page, but you could specify that one particular one should not (and appear on a "News" page instead). You could also specify that Article nodes never appear on your front page. You can also modify the standard content types and create your own, custom content types. For more information, see: Custom content types. • Article - Intended for announcements, press releases and other "timespecific" content. • Basic Page - Intended for static pages like "about us", mastheads, or similar. Do not use this content type to make a "contact" page, the Contact module can create a contact page for your site (and contact pages for individual users). • Blog entry - If your site has multiple contributors, use this content type for blog posts. ◦ The posts can all appear (in order of submission) on your front (or other page) and be sorted into single-author blog pages. • Book page - "Books" in Drupal are sets of nodes that have been organized into sections (chapters) and an order (like pages in a book). Books have a built-in hierarchical navigation. Top level nodes are "books" containing lowerlevel chapters, sections and pages. For more information, see: Organize your content in books) • Forum topic - Post a forum topic to begin a new discussion thread in your site's forums. You will need to create at least one forum container and/or forum before you can post forum topics. • Poll - Create simple surveys on your site. A poll allows you to put a question to your site visitors and let them choose from a set of answers. Node specific settings - When adding a node, you can specify the various settings for that specific node at the bottom of the content creation page. Content-type settings - You can edit each content type's global default settings: navigate to the Content types page at Structure > Content types, click "edit" next to the specific content type, modify its settings and save your changes. See also: Default content type configurations, Content type settings overview
Add your first content - basic tutorials This section will take you through creating some basic content (2 nodes and a contact page) and help you become familiar with how to use your Drupal Gardens website.
Write a blog entry: • Navigate to the Content overview page by clicking Content in the administration menu:
• The administrative overlay will open - Clicking on most administrative and edit links on your site will open the Drupal 7 overlay: a panel floating above the page you are on displaying your site's administrative interface. Make the changes to configuration and content you need, save them, then close the overlay by clicking the "X" on the top right and you'll be right back where you were before the overlay opened.
• Click "Add new content":
• Click "Blog entry":
â&#x20AC;˘ Add a title and body text - Use Drupal Gardens' built in WYSIWYG text editor to compose your first blog entry. Feel free to experiment with various functions and options. If you are familiar with HTML, below the Body entry field you can disable the text editor ("Disable rich-text"), change the text format and enter HTML directly.
Add an image to your content Note: Do you want images on every node you create? - The method described here is flexible and allows you to add images anywhere to any node of any content type. If you want a certain content type to always have an image (this allows you to generate and add thumbnails to teasers and more), you can customize a content type to always include one or more images or create a new, custom content type. For more information, see: Custom content types • Click the "add image" button in the WYSIWYG toolbar.
• Upload an image from your computer - Click "Upload" then the "Browse" button to select a file from your computer. Once you have selected it, click "Submit" to add it to your site's media library.
• Select the image from your media library by clicking it, then click "OK" at the bottom of the media browser panel.
• Choose image size and enter alternate text then click "OK" to embed the image in your blog entry.
â&#x20AC;˘ Image embedded in node body:
Tag your node Tags categorize your content, help visitors find related information easily, and allow you to create pages based on tags. For example, you can create a news page of blog entries tagged with "news". Separate multiple, individual tags with commas: "summer, vacation, lobster, car trip". User comments and other settings Drupal Gardens content types all have a set of default behaviors that make them suited to a particular purpose. For example, "Blog entry" and "Article" nodes will appear by default on your front page, but you could specify that a particular one should not (and appear on a "News" page instead). You could also specify that blog entries nodes never appear on your front page. The default settings can be changed on an individual, per node basis or globally for all nodes of a content type. Keep the standard settings for the blog entry you have just written (at least for now): • Menu - No menu item will be created. Blog entries don't usually need a permanent menu item. They appear on the front page by default (see Publishing options below) and can be found chronologically and by their tags. • Book outline - This node will not be included in a book. • Revisions - No record of revisions will be kept if you edit this node. • URL path - A "path alias" will be automatically created for this node based on its title. In this case: http://example.com/content/what-i-did-summer. • Comments - Site visitors may add comments to this post if you allow that on your site (see: user roles and permissions). • Author - You (the current user) will be listed as the author of this blog entry. • Publishing options - The node will be published and appear on the front page of your site.
Publish your blog entry Click "Save" and your blog entry is Posted!
Edit a node, change its teaser ... Edit or delete your blog entry If you need to change something about a node you have already posted, simply move your mouse over the small gear symbol that appears to the right of the title, click on the option you need in the drop-down menu.
Teaser and full node view The version of the example blog entry in the screenshot above shows its "teaser". If there were more blog entries, their teasers would be displayed one below the other down the front page, in reverse chronological order (newest on top). Clicking the title opens the "full" version - the entire blog entry displayed on its own page. Change the teaser By default, node teasers are generated automatically for you. If you want a specific section of your post as a teaser, click "Edit". On the node edit form, click the "Edit summary" link right above the body editing field and WYSIWYG toolbar. There you can paste a specific section of your blog entry into the summary field, or write a completely new text to be the teaser for your blog entry. Show the full version of nodes instead of teasers You can change a content type's default to show full blog entries (or other content types) instead of just teasers on your front page or other lists. Edit the content type's display settings: â&#x20AC;˘ Navigate to Structure > Content types â&#x20AC;˘ Click "manage display" for the content type you wish to change
• Set the teaser format to "Default" instead of "Summary or trimmed"
Make a static "about us" page The "Basic page" content type is what you need for static pages on your website. • Click "Add content" in the gray shortcut bar - Click "Basic page" under Add new content. For more about the shortcut bar, see below.
• Give your "about us" page a title and body text, just like your first blog entry. • Basic pages do not have taxonomy tags activated by default - Generally a static page will have a fixed menu entry for users to find it, while other kinds of pages (blog entries, forum posts, etc.) are categorized with tags so that they can be grouped, sorted and displayed in various, dynamic ways. • Add an "About us" menu item - If you want this page to be easily found by site visitors, you should give it a menu item in your site's main menu: ◦ Select the "Menu settings" panel
◦ Check the "Provide a menu link" check-box ◦ Add the menu link title "About us" ◦ Select the Parent item "<Main menu>"
• Other settings - You will notice that the standard settings for the "Basic page" content type are slightly different from those of Blog entries (see above): ◦ Comments are not enabled. ◦ Basic pages are not promoted to the front page of your site.
Make a contact page Navigate to Structure > Contact form to configure your site-wide contact form.
Add one or more contact categories Click "Add category" - For each contact category that your create, you must specify the following: • Category - the name that appears in the drop-down selector on your contact page • Recipients - one or more e-mail addresses that messages in this category will be sent to • Auto-reply - (optional) This will be sent immediately to users who send contact messages in this category. • Weight - Contact categories will be sorted and listed alphabetically by default. Categories with lighter weights (lower numbers) will "float" above those with heavier weights (higher numbers). • Selected - One contact category can be selected by default on the contact form.
Add a "Contact" menu item If you want your site visitors to be able to contact you easily, you'll want "Contact" to appear in your site's main menu. By default, the contact form's menu item is
deactivated and listed in the "Navigation" menu, not the main menu. Let's activate it and move it to the main menu: • Navigate to Structure > Menus • Click "list links" for the Navigation menu • Click "edit" for the menu item "Contact"
• Check the "enable" check-box • Change the "Parent link" to "Main menu" • Click "Save"
Here is the Contact link in your main menu!
And here is your contact form at http://example.com/contact
Add custom text to your contact form To add text or images to your contact form, you'll need to create a custom block and place it on the contact page: • Navigate to the Blocks administration page at Structure > Blocks • Click "Add block" • Create and configure the custom block: ◦ Block description - This description is shown on the Block administration page. For this example: "Contact form text" ◦ Block title - This title is displayed to users wherever the block is displayed. For this example: "Get in touch with the example.com team" ◦ Block body - This text is displayed to users wherever the block is displayed. For this example: "Thank you for your interest in our site and services. For the best possible service, select the contact category below that best matches your needs. - The example.com team."
• Region settings - Select the "Page content" region of your front-end theme. This is the block region where the block will be displayed. See the Compact Drupal Glossary for more on regions.
• Visibility settings - under "Pages", click the "Only on the listed pages" radio button and enter "contact" (the path to the contact form) in the text box. • Click "Save block"
Here's the contact form with your custom text:
Edit existing content, blocks or menus "Gear" symbol - When you are logged in to your Drupal Gardens site as an administrator, editing existing site content couldn't be easier! Simply mouse over the title of any page, the header of any block or and you will see a "gear" symbol:
Click the gear symbol to open a drop-down menu of dynamic editing and configuration options relevant to the site element in question. Click the option you need to be taken to the appropriate editing or administration page to make changes. Node -
Standard block -
Menu -
Content type settings overview At the bottom of the content creation page for every content type, you can specify various settings for the content node you are creating. You can either accept the content type's default settings, or modify them for the specific node you are creating. You can edit each content type's default settings: click "edit" next to the specific content type you wish to edit at Structure > Content types.
Menu Settings • Provide a menu link - Check this check-box to create a menu item for the content node you are creating. This makes sense for relatively static content like an "about us" page. Blog posts, photos in photo galleries and other, more ephemeral content can be sorted into dynamic lists, blocks and pages and linked to in other ways rather than creating a specific menu item for each one. • Menu link title - This text appears as this content's menu item. • Parent item - If you have one or more menus activated on your site, you may select which one the new menu item should appear in. Menus can be configured on the Menus page at Structure > Menus and activated and positioned on your site via the Block page at Structure > Blocks. See the Menus and navigation and Blocks sections for more information • Weight - Menu items are sorted and displayed alphabetically by default. Giving them relative "weights" allows you to sort them as you need. A "lighter" item with a lower number will "float" higher in a list than a "heavier" item with a higher number (and hence a heavier "weight"). In horizontally displayed menus, items' "weights" determine the sorting from left to right, "lighter" to the left "heavier" to the right.
Book outline • Book - Select an existing book on your site for the new node to be a part of or "<create a new book>" to make the new node the top-level node of a new book. ◦ Select "<none>" to save the node outside of book hierarchies. • Parent item - If the book you are adding a page to already has pages, you can select any existing page to be the new node's "parent". This makes the parent page a chapter or section header. • Weight - By default, chapters, sections and pages will be sorted and displayed alphabetically by node title within their hierarchical level. You may change this order by giving one or more children of any parent a "weight"
value: A "lighter" item with a lower number will "float" higher in a list than a "heavier" item with a higher number (and hence a heavier "weight"). • See also: Organizing your content in books.
Revision information • Create new revision - Check this check-box and enter a revision log message to keep track of important points in your site's or content's development. Your Drupal website keeps all content revisions, allowing you to track approvals, launch versions, editorial policy, and so on.
URL path settings • Automatic alias - Check this check box to have your Drupal site generate a human-memorable and search-engine-friendly URL (address) for the content
node you are creating. Any given node on a Drupal site has a URL something like http://example.com/node/128573 - this is neither memorable for site visitors, nor can search engines extract useful information from this when indexing your website. Drupal Gardens uses the Drupal Path and Pathauto modules to provide URL aliases (an alias is a 2nd URL where your content can be found) for content. For example a blog post called "What I did during summer vacation" will be aliased to something like http://example.com/what-i-did-my-summervacation. You can see and change the settings used to do this by clicking "automated alias settings" in the URL path settings form or navigating directly to /admin/ config/search/path/pathauto in your Drupal Gardens site. â&#x20AC;˘ URL alias (set a page address manually) - You may choose to add a URL alias of your choice, by unchecking the Automatic alias" check-box and entering an alias such as "about". Your page will then be available at http://example.com/about.
Comment settings â&#x20AC;˘ Comment settings open/closed - On content types such as a static "about us" page, you probably don't want site visitors to be able to leave comments but on other content like blog posts and forums topics, you probably do. â&#x20AC;˘ Can anonymous visitors leave comments? - You can decide this for yourself by deciding which user roles should be allowed to leave comments. Give the "Post comments" permission to those you wish to allow to contribute. See User roles and permissions - access to functionality and content for more information.
Authoring information • Authored by - Enter your username for it to be displayed on the node you are creating. If you leave this field blank, the node will appear as authored by "anonymous". • Authored on - In most cases, you can simple leave this blank and the current date and time will be displayed. You may also enter a date and time of your choosing. • Date/time formats - Depending on where you and your site visitors live, you may need to use a particular time/date display format. Several are available by default on the Types tab of the Date and time page at Configure > Date and time; simply select the appropriate long, medium and short display formats. If none of these formats suits your needs, you may create custom formats by clicking "Add format" on the Formats tab of the Date and time page at Configure > Date and time. • How do I stop the authoring information from being displayed at all? You can stop the "submitted by Username on date" information from appearing on specific content types. You may wish to have this information displayed on blog posts, but not on your static pages. Navigate to the Content types page at Structure > Content types, clicking "edit" for the content type you wish to change and checking or unchecking the "Display post information" check-box in the "Display settings" panel at the bottom of the page.
Publishing options â&#x20AC;˘ Published - Nodes that are "published" are visible to all site visitors whose roles have the "Access content" permission. Nodes that are not published are only visible to their author (but the author must have a role with the "View own unpublished content" permission). See User roles and permissions access to functionality and content for more information. â&#x20AC;˘ Promoted to front page - Using the standard configuration, your Drupal Gardens site's front page is a "river of news" (blog-style) chronological list of content that is marked "Promoted to front page". This is a good setting for blog posts and similar content, but not for content like an "about us" page or other content without a chronological frame of reference. â&#x20AC;˘ Sticky at top of lists - On the standard front page, in forums and other situations in which content is presented in reverse chronological order, setting a node to be "sticky at top of lists" places it at the top of the page in question for as long as it remains "sticky". This functionality is commonly used for important announcements on the front page of a website or to present moderation and behavior guidelines in a user forum.
Default content type configurations Article: information and settings Add an article - Click Content then "Add content", then "Article" - See also Add content - basic tutorial (add an "about us" page) for a complete description of how to add standard content. A standard Article node has: • Title (compulsory) • Tags • Body text (and an optional summary) Standard settings for the Article content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Revision information) • no URL alias (see also: URL path settings) • user comments open (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published, promoted to front page (see also: Publishing options) Edit the default settings for the Article content type at Structure > Content types, click "edit" for the Article content type. Basic page: information and settings Add a Basic page - Click Content then "Add content", then "Basic page" - See also Add content - basic tutorial (add an "about us" page) for a complete description of how to add a Page node. A standard Basic page node has:
• Title (compulsory) • Tags • Body text (and an optional summary) Standard settings for the Basic page content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Re • vision information) • no URL alias (see also: URL path settings) • user comments closed (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published (see also: Publishing options) You can edit the default settings for the Basic page content type at Structure > Content types, click "edit" for the Basic page content type. Blog entry: information and settings Add a Blog entry - Click Content then "Add content", then "Blog entry" - See also Add content - basic tutorial (add an "about us" page) for a complete description of how to add standard content. A standard Blog entry node has: • Title (compulsory) • Tags • Body text (and an optional summary) Standard settings for the Blog entry content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Revision information) • no URL alias (see also: URL path settings) • user comments open (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published, promoted to front page (see also: Publishing options) "Recent blog posts" block - A block of recent blog entries is available by default on the Blocks pages at Structure > Blocks. Edit the default settings for the Blog entry content type at Structure > Content types, click "edit" for the Blog entry content type. Book page: information and settings Add a Book page - Click Content then "Add content", then "Book page" - See also Add content - basic tutorial (add an "about us" page) for a complete description of how to add standard content.
Although the "Book page" content type is specifically intended for use in hierarchically organized "books" of content, any content type can also be included in books on your site. For more information, see : Organize your content in books) A standard Book page node has: • Title (compulsory) • Tags • Body text (and an optional summary) Standard settings for the Book page content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Revision information) • no URL alias (see also: URL path settings) • user comments open (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published, promoted to front page (see also: Publishing options) Edit the default settings for the Book page content type at Structure > Content types, click "edit" for the Book page content type. Forums and forum topics: information and settings 1) You must add forums and or containers before you can create forum topics - You need somewhere to put forum topics before you can create them. • Navigate to the List tab at Structure > Forums • Create forums and containers - Containers can contain multiple containers and/or forums. Forums may contain one or more forum topics. ◦ Click "Add container" or "Add forum" ◦ Forum/Container name - This name will apear on admin and userfacing forum pages. ◦ Description - Explain what the forum is for. This text will appear in the user-facing forum pages. ◦ Parent - Forums or containers are grouped by their "parents". Containers can be parents of both forums and other containers. The highest level parent is called <root>. ◦ Weight - By default, forums and containers will be sorted and displayed alphabetically within their group. You may change this order by giving one or more children of any parent a "weight" value: A "lighter" item with a lower number will "float" higher in a list than a "heavier" item with a higher number (and hence a heavier "weight"). For example, a website about pets might have forums structured like this: • Dogs (container - parent of Breeds, Care, and Best walking parks) ◦ Breeds (container - parent of Dachshund, German shepherd, and Collie) ▪ Dachshund (forum) ▪ I love my wiener dog (forum topic) ▪ Speed training for Dachshunds (forum topic) ▪ German Shepherd (forum)
▪ Big dogs and little kids (forum topic) ▪ Need advice on breeding lines (forum topic) ▪ Collie (forum) ▪ The bridge has collapsed! (forum topic) ▪ Little Jimmy needs help! (forum topic) ◦ Care (forum) ▪ Anybody know a good poodle salon? (forum topic) ◦ Best walking parks (forum) • Cats (container) ◦ ... • Birds (container) ◦ ... • Pet and owner care (container) ◦ House cleaning products (forum) ▪ Anybody have tips for cleaning up after puppies? (forum topic) ◦ Vet recommendations (forum) ▪ Dr. Hund is great with cats. (forum topic)
2) Forum settings - You can set several aspects of how your forums work on the Settings tab at Structure > Forums: • Hot topics threshold - Set the minimum number of replies needed to be classified "hot". The more people reply to a forum discussion thread, the "hotter" the topic is. The hottest topics in your forums float to the top of their forum containers. • Topics per page - Default number of forum topics to display per page. You might prefer to keep this number low to keep everything on forum pages "above the fold" (user will be presented with shorter pages that they can page through to see more topics) or set this number higher to put more of your forums on a single, longer page.
• Default order - Sort forum topics by date (newest or oldest first) or by "posts", that is by the amount of activity in the forums (most or least active first). 3) Add a forum topic - You must create forums and/or forum containers (see above) before creating Forum topics. Click Content then "Add content", then "Forum topic" See also Add content - basic tutorial (add an "about us" page) for a complete description of how to add standard content. A standard Article node has: • Subject (compulsory) • Body text (and an optional summary) • Tags Standard settings for the Article content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Revision information) • no URL alias (see also: URL path settings) • user comments open (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published (see also: Publishing options) Edit the default settings for the Article content type at Structure > Content types, click "edit" for the Article content type. Poll: information and settings Add a poll - Click Content then "Add content", then "Poll" - See also Add content basic tutorial (add an "about us" page) for a complete description of how to add standard content. A standard Poll node has: • Question (compulsory) • Choices (2 by default - if you enter two, a link appears to add more) - each choice has a vote count box that allows you to "pre-seed" choices with votes. • Poll status: closed / active - use this setting to manually close or reopen an existing poll. • Poll duration: select how long a poll should run from the drop-down list. Standard settings for the Poll content type (see Node settings overview for more information): • not in any menu (see also: Menu settings) • not in any book (see also: Organize your content in books) • do not create new revision on edit (see also: Revision information) • no URL alias (see also: URL path settings) • user comments open (see also: Comment settings) • "authored by" current user (see also: Authoring information) • published, promoted to front page (see also: Publishing options) Edit the default settings for the Poll content type at Structure > Content types, click "edit" for the Basic page content type.
Custom and customized content types What is a content type? What are fields? Drupal Gardens comes with a set of standard content types (Article, Blog entry, Book page, Forum topic, Page, Poll). Each content type holds certain kinds of information and has settings that make it suited to a particular purpose. Different content types can appear in different publishing contexts on a website and are sortable by different criteria. For example, the Drupal Gardens standard content type "Blog entry" hold three pieces of information (title, body, tags) and has a set of default settings including open comments and being published to the front page. Technically, a content type is a standardized data model – the collection of data fields (aka "fields": title, body text, etc.) that make up any given node (Drupal's basic unit of content). Drupal nodes are always of a given content type. Fields hold data and can extend what any content type (or comments attached to that content type) does – add images, files (attachments), more text, lists or references to other content. Why custom (or customized) content types or comments? Site administrators can edit content types' and their comments' standard settings and define custom content types at Structure > Content types. You can customize existing content types and their comments by changing their settings and adding or removing fields. You can also create entirely new content types for specific purposes. But why? Good reasons to customize a comments, content type or make new ones altogether: • Add images to content - If you want to add images to most or all of your blog entries, for example, you could add an image field to it instead of adding inline images. ◦ Create teaser images - Adding an image field allows you to use different image variations to be displayed in teaser, full node and other display options. • Vertical organization of your site content - Make dynamic pages or blocks of different content types and add menu items for those pages (see: Simple views). • Contributor access - Make individual content types for different authors or types of contributor and give them write and edit access to their content type only. (see: User roles and permissions). • Visitor access - Make certain content types available only to logged in ("authenticated") users or only to users with certain user roles. (see: User roles and permissions). • Downloads - Add files to nodes for your site visitors to download. Restrict access to this content type by user role if the material isn't for the general public. • Tailored data models - All content types, blog entries, forum posts, etc. are different because they fulfill different needs. Make a round peg for a round hole by creating exactly the content type your site needs. Data entry: Field Widgets Wait ... what's a widget? - Drupal field widgets are the entry tools used to get data into any given field: text boxes, radio buttons, drop down select lists, etc. When you select a field, you also select the widget you or your users will use to interact with it. Since different data fields take different kinds of input, each field has its own selection
of one or more widgets available (a file upload field needs an upload widget, for example, while a text field needs a text input widget). Widgets available in Drupal Gardens: • Autocomplete widget (tagging) - For tagging content from an existing taxonomy vocabulary, this widget suggests existing vocabulary terms while you are typing them in, helping helps avoid repetition and misspellings in tagging taxonomies. • Check boxes/radio buttons - Select a value for fields with multiple, pre-defined options. • File (media) - This field is currently under development. • File - Upload widget for attaching files to nodes. • Image - Upload widget for attaching images to nodes. • Select list - A drop-down list to select a value for fields with multiple, pre-defined options. • Single on/off checkbox - For Boolean (yes/no) fields. • Text area (multiple rows) - A larger text entry area. Used by the "Long text" field type • Text area with summary - A text entry area with optional, definable summary (teaser) text. This is the field used for the body of content types like Blog entry and Article. • Text field - A simple text entry area.For certain kinds of fields, its input value will be validated during node submission (an integer field will only take a whole number, for example). Fields Here's a quick run down of the fields available in Drupal Gardens and the widgets for each one: Default existing fields - These are pre-configured and in use on your Drupal Gardens site. You can add them to your own custom content types, too. • Term reference taxonomy_forums (Forums) - Forums in Drupal are organized by taxonomy vocabularies. If you have forums activated and forum containers in place, adding this field to a content type with a "select list" widget would allow you to add nodes of this type directly into a forum on your site. ◦ Available widgets: select list, check boxes/radio buttons, autocomplete widget (tagging) • Term reference taxonomy_tags (Tags) - Adding this field to your content types allows you to tag it using the same pre-configured tagging vocabulary as Articles, Blog entries and Forum topics and Polls on your site. ◦ Available widgets: select list, check boxes/radio buttons, autocomplete widget (tagging) New fields - Add new fields to new or existing content types. You may create new fields of all of the following types and configure them to work with any widget available for them. Field types and widgets: • Boolean (yes/no) - Simple yes/no, on/off data field. ◦ Available widgets: Select list, Check boxes/radio buttons, Single on/off check box • Decimal - Numeric value (decimal)
◦ Available widget: text field • File - Attach files for user download ◦ Available widgets: File, [File (media) under development] • Float - Numeric value (floating point http://en.wikipedia.org/wiki/Floating_point) ◦ Available widget: text field • Image - Attach and display images on nodes. ◦ Available widget: Image • Integer - Numeric value (whole number) ◦ Available widget: Text field • List, List (numeric), List (text) - Fields for various types of lists ◦ Available widgets: Select list, Check boxes/radio buttons • Long text - Add texts of one or more paragraphs to nodes. ◦ Available widgets: Text area (multiple rows) • Long text and summary - Add texts of one or more paragraphs to nodes. The summary appears in the node teaser display and can be separately edited or set to be the first X characters of a node (set under "Display settings" for each content type navigate to Structure > Content types, click "edit" next to the content type in question). ◦ Available widget: Text area with summary • Multimedia asset - Currently under development ◦ Available widget: File (media) • Term reference - Associate nodes with taxonomy terms. Depending on the vocabularies you have in place and the functionality you build in, adding a particular vocabulary and tag this can put a given node into a forum (because Drupal forums are organized by taxonomy terms), add a node to a dynamic page (simple view) containing nodes tagged with a particular term, add it to search results for terms and more. ◦ Available widgets: Select list, Check boxes/radio buttons, Autocomplete term widget (tagging) • Text - Add short texts to nodes. ◦ Available widget: Text field
Add a custom content type (example) Here's an example of adding a new content type for teams in a company sports league. • Navigate to the Content types page at Structure > Content types • Click "Add new content type" and define your new content type: ◦ Add a name and description - These are Displayed on the Add new content page at Structure > Content, "Add new content". ◦ For the example, "Team listing" and "Register your team for the company league."
◦ Submission form settings - These determine the appearance of a content type's node creation/editing page. ▪ Title field label - a label for the title field of these nodes ▪ For the example, "Team name". ▪ Body field label - a label for the body field of these nodes ▪ For the example, "Team description". ▪ Preview before submitting - Set whether content creators can or must preview the nodes of this content type before submitting them. ▪ For the example, optional. ▪ Explanation or submission guidelines - Any text you put here will appear above the node creation/editing page for this content type. This is a good place to put any instructions you may have for your content creators. ▪ For the example, "Register your team and players for the upcoming season. May the best team win!"
◦ Publishing options ▪ Default options - These determine what happens by default when submitting nodes of this content type. They can be changed on an individual, per-node basis. ▪ Published - Nodes that are "published" are visible to all site visitors whose roles have the "Access content" permission. Nodes that are not published are only visible to their author (but the author must have a role with the "View own unpublished content" permission). See User roles and permissions for more information. ▪ Promoted to front page - Using the standard configuration, your Drupal Gardens site's front page is a "river of news" (blog-style) chronological list of content that is marked "Promoted to front page". This is a good setting for blog posts and similar content, but not for content like an "about us" page or other, static content without a chronological frame of reference. ▪ Sticky at top of lists - On the standard front page, in forums and other situations in which content is presented in reverse chronological order, setting a node to be "sticky at top of lists" places it at the top of the page in question for as long as it remains "sticky". This functionality is commonly used for important announcements on the front page of a website or to present moderation and behavior guidelines in a user forum. ▪ Create new revision - If checked, your Drupal Gardens website keeps revision records of all changes to nodes of this content type. Users making changes to these nodes are able to enter a log message to help track approvals, launch versions, editorial policy, important points in your site's or content's development, and so on. ▪ Multilingual support - Enable this to be able to mark a node as being in a particular language available on your site. Enable with
translation to be able to create translated versions of content of this type.
◦ Display settings ▪ Display author and date information ▪ Disabled for the example content type. ▪ Length of trimmed content (teaser length) - If using the field type "Long text and summary" as the body of nodes of this content type, this determines the default length of the node summary (usually shown in the teaser view of a node and also changeable on a node-bynode basis).
◦ Comment settings ▪ Threading - Show replies under the comments they pertain to. ▪ Comments per page - How many comments to display per page. ▪ Default comment setting for new content - Can be set to open, hidden or closed. ▪ Anonymous commenting - If the content type you are editing is enabled for Comment notify subscriptions, set whether anonymous site visitors may leave their e-mail address on their comments (and therefore whether they can subscribe to comment notifications). ▪ Preview comment - Set whether site visitors can or must preview their comments before posting them.
◦ Menu settings ▪ Available menus - Choose in which menus links to nodes of this content type may be included. ▪ Default parent item - When making a menu link for nodes of this content type, it will be included under this item by default, but others may be selected from the available menus on an individual, node-bynode basis.
• Click "Save content type" - If you don't feed further features or custom fields. • OR click "Save and add fields" - If you want to add custom data fields to this content type at this time. You can always add or remove fields and edit other aspects of any content type by navigating to Structure > Content types and clicking its "edit" link. Add fields to a content type or its comments (example) When created, a content type and its comments only have a title and a body. You can add and arrange fields on both. Adding fields to content types - The following example covers adding fields to a
content type using the functionality located on the "Manage fields" and "Manage display" tabs. Adding fields to comments - To customize comments for any given content type, the same method applies as shown below, but on the content type's "Comment field" and "Comment display" tabs. Let's add two more fields to the example "Team listing" content type that we added above: • Image field - for a team mascot/avatar to be displayed on teasers and team pages • Text field - for the team's motto Add fields to a content type • Navigate to Structure > Content types and click its "edit" link, then click on the "Manage fields" tab.
• Image field - team avatar
◦ Add image field ▪ Use the "Add a new field" row of the Manage fields tab ▪ Label the field ▪ "Label" is what will appear on the content creation page ▪ "Field name" is for the system to keep track of it. It may contain only letters, numbers and underscore characters. ▪ Field type and widget - Select the image field type and the image widget ▪ Click "Save" ◦ Field settings
▪ Public files - If you choose public file storage for images or other attachments, the files are managed by the web server users can download the files directly based on their URLs. Drupal manages files saved in non-public directories, making it harde, but not impossible for users to download them. ▪ Default image (optional) - You can upload an image to be displayed on Team profile nodes without their own avatars. ▪ Click "Save field settings" ◦ Content type-based field settings - After saving the basic properties of the new field (previous step), you are taken to the settings page that controls all aspect of the new field when used on the content type you have assigned it to. ▪ Label - This labels the field on the content creation page. If different, the label you enter here overrides the label originally entered on the Manage fields tab previously. ▪ Help text - Instructions for users regarding this field. Text you enter here will appear below the field on the content creation/editing page by default.
▪ Allowed file extensions - Define which file types users may upload. ▪ File directory - Keep all files associated with this field in their own directory on your server's file system. Enter a directory
name here for it to be created. Directory names may not include slashes, spaces or special characters. ▪ Maximum image resolution - Images larger than these dimensions will be automatically resized. Leave blank for no restrictions. ▪ Set to 300 x 300 pixels for the example field. ▪ Minimum image resolution - Images smaller than these dimensions will be rejected by your site. Leave blank for no restrictions.
▪ Maximum upload size - The system default (256MB) is more than large enough for the images on our example content type. For other field types (file attachments, for example), it might be necessary to increase this limit. ▪ Enable Alt field (accessibility) - This text is displayed if the intended image cannot be displayed for any reason. It is also often read by screen readers. ▪ Enable Title field (accessibility) - This text is presented as a hovering "tool tip" in most browsers. ▪ Progress indicator - Choose what to display to indicate the image upload is in progress.
▪ Field settings - these mirror (with the addition of the "Number of values" setting) the field settings as encountered when creating the new image field (see above). ▪ Number of values - How many images can be attached to this field. ▪ Click "Save settings"
• Text field - team motto ◦ Navigate to Structure > Content types and click its "edit" link, then click on the "Manage fields" tab.
◦ Add text field - Use the "Add a new field" row of the Manage fields tab ▪ Label the field ▪ "Label" is what will appear on the content creation page ▪ "Field name" is for the system to keep track of it. It may contain only letters, numbers and underscore characters. ▪ Field type and widget - Select the text field type and the text widget ▪ Click "Save" ◦ Field settings - The maximum number of keystrokes this field may contain. ◦ Click "Save field settings" when configured to suit your needs.
◦ Content type-based field settings - After saving the basic properties of the new field (previous step), you are taken to the settings page that controls all aspect of the new field when used on the content type you have assigned it to. ▪ Label - This labels the field on the content creation page. If different, the label you enter here overrides the label originally entered on the Manage fields tab previously. ▪ Required field - Making this a required field forces users to enter an allowed value for it when creating or edit a node of this content type. ▪ Size of text field - Display width of text entry box on the node creation/editing page. Not to be confused with the maximum length of the entry allowed in this field! ▪ Text format - Whether users must enter plain or formatted text in this field. ▪ Help text - Instructions for users regarding this field. Text you enter here will appear below the field on the content creation/editing page by default. ▪ Default value (optional) - You can enter a text to be displayed on Team profile nodes without their own avatars.
â&#x2013;Ş Field settings - these mirror (with the addition of the "Number of values" setting) the field settings as encountered when creating the new image field (see above). â&#x2013;Ş Number of values - How many images can be attached to this field. â&#x2013;Ş Click "Save settings"
Arrange fields on a content type or its comments (example) With two new fields added, the "Manage fields" tab of the Team listing content type looks like this. The fields on these nodes will be displayed in the order shown:
To arrange them in a different order, simply drag one by the "+" handle to where you need it. When you are done, click "Save".
Manage content type display (example) Define node display - You can define how nodes of any content type are displayed as teasers, in full, in print, in RSS feeds, search indexes, and search results. To define which fields are displayed (and how they are displayed) in various contexts, navigate to the "Manage display" tab of the content type in question (Structure > Content types, click "Manage display"). Here are the basic settings for the example content type "Team listing": â&#x20AC;˘ Teasers
• Full
◦ Avatar image will be displayed as a thumbnail without a label ("Team avatar" in this case). The thumbnail image is also a link to its Team listing node. ◦ Team motto will be displayed without a label ("Team motto" in this case) ◦ Team description - The summary (the first 600 characters) will be displayed ◦ Avatar image will be displayed with a label ("Team avatar" in this case) ◦ Team motto will be displayed with a label ("Team motto" in this case) ◦ Team description - The default (full) text will be displayed
Custom content type, creation, displays (example) Create a new team node (the Avatar is 300x 300 pixels, the Team description text is longer than shown):
Teaser view of the new node - note: • unlabeled thumbnail version of avatar • unlabeled team motto • summary version of the Team description
Full view of the new node - note: • full size avatar image displayed with label "Team avatar" • team motto displayed with label "Team motto" • full Team description text displayed
Add block and page views of a content type Make custom, dynamic pages of any given content type using Simple views. back to top
STRUCTURE The structure of your website should be determined by what your site is for, what message you want to get across, what content you want to highlight, and so on. The way you add and place various ways to get your content - menu links, blocks, a search box, etc. - will determine how and what visitors will find on your site. The following can he help you consider how to structure your website: â&#x20AC;˘ What do you want to say? - The information you want to present on your site will determine what content types you need to present it in, whether in the preconfigured Drupal Gardens content types or in new, custom content types.
• What should visitors find? - Most websites fundamentally have two kinds of pages: single pieces of content (blog post, "about us" page, etc.) and lists of content (chronologically ordered blog pages, forums, articles groups by subject, etc.). You can present links to both in your site menu and navigation.
Structural elements - overview • Block - A container for static or dynamic content. See Blocks ◦ The location of any given block is determined by which block region you place it in on the Blocks page at Structure > Blocks. • Block regions are defined by your front-end theme. See Block regions ◦ The location of any given block region is determined by the layout you choose in the ThemeBuilder for any given page of your site. • Content area - The Drupal block that displays your main page content. • Content type - Content types are collections of data fields (title, text, image, etc.) and settings (display, comment, menu, etc.). Drupal Gardens come with five standard content types and you can also create your own, custom content types to suit your site's needs. • Field - Data fields ("fields") can be attached to Drupal content to extend them. There are fields to hold various kinds of text, number, taxonomy terms, and more. • Menu/Navigation - You can add links to static and dynamic pages in one or more menus on the Menus page at Structure > Menus. To place them in your page layout, assign them a block region on the Blocks page at Structure > Blocks. • Page - Your website's pages are made up of one or more blocks laid out in block regions. Pages can be dynamic (the standard front page, for example, or custom pages created by Simple Views) or static (for example, an "about us" page created as a "Basic page" node). • Page Layout - The arrangement of block regions on a page. See: Layout tab in the ThemeBuilder documentation. • Theme - In Drupal, the "theme" is the combination and placement of visual elements on your website; the arrangement of blocks in various regions, different layouts on different pages, the selection of colors, fonts and graphics. In Drupal Gardens, the ThemeBuilder lets you choose and customize your site's look directly in your browser.
Menus and navigation Make a menu link for new or existing content When creating new content or when editing existing content, you can add it to a menu (or remove it). Add menu item for content • Check "Provide a menu link" check-box - Check this check-box to create a menu item for the content node you are creating or editing. • Menu link title - This text appears as this content's menu item. • Parent item - If you have one or more menus activated on your site, you may select which one the new menu item should appear in. Menus can be configured on the Menus page at Structure > Menus and activated and positioned on your site via the Block page at Structure > Blocks. See Blocks sections for more information
â&#x20AC;˘ Weight - Menu items are sorted and displayed alphabetically by default. Giving them relative "weights" allows you to sort them as you need. A "lighter" item with a lower number will "float" higher in a list than a "heavier" item with a higher number (and hence a heavier "weight"). In horizontally displayed menus, items' "weights" determine the sorting from left to right, "lighter" to the left "heavier" to the right. Remove menu item for content â&#x20AC;˘ Uncheck "Provide a menu link" check-box on the editing page for the content in question and save the node.
Blocks What is a block? A block is a container for static or dynamic content that can that can be assigned to any block region in a site theme that typically appear in the sidebars, header, or footer of a site. Standard Drupal Gardens blocks include: Page content, User login, Main menu, Recent comments, and the Who's new block. Some modules make new blocks available when they are activated. Administrators can add new custom blocks containing static or dynamic content. Blocks can be created, enabled, disabled, moved to different block regions and configured from the Blocks page, Structure > Block. What is a block region? A block region (or just a "region") is an area defined by the theme into which blocks can be placed. Drupal Gardens themes come with a number of block regions. You can manage and place blocks in various regions on the Blocks page at Structure > Block.
Display your theme's block regions All current Drupal Gardens themes contain the same selection of block regions. Visit the Drupal Gardens theme region display site to see them: • http://regions.drupalgardens.com/
Display the regions on your own site - To see the block regions of your own site, follow these instructions: • Navigate to the Blocks page at Structure > Blocks • Click the "Demonstrate block regions" link - This will take you to a page with a URL like this: ◦ http://example.com/#overlay=admin/structure/block/demo/acq_sparks_1 The regions you see on that page are those of the administrative overlay and not all the regions available in your theme.
• Remove "/#overlay=" from the URL and reload the page to see the regions of your current front-end theme ◦ http://example.com/admin/structure/block/demo/acq_sparks_1
Create and place a new block To add a simple block to your website follow the instructions below. Standard blocks - Note that many kinds of blocks, many of them dynamic (i.e. "Recent comments", "Recent blog posts") or special ("User login", "Search"), come included in Drupal Gardens and that activating some modules will also make more blocks available. Custom dynamic blocks previewing content as node titles and/or teasers can be created using Simple views. Once you have created a new, dynamic block with Simple views, return to the Block page at Structure > Blocks to activate it and place it in a region. Add a • • •
static block Navigate to the Blocks page at Structure > Blocks Click "Add new block" Content and settings ◦ Block description - This is displayed on the block administration page ◦ Block title - This is displayed to site visitors
◦ Block body - Use Drupal Gardens' built in WYSIWYG text editor. Feel free to experiment with various functions and options. ◦ Text format - If you are familiar with HTML, below the Body entry field you can disable the text editor ("Disable rich-text"), change the text format and enter HTML directly. ◦ Region settings - Set the block region where the block should appear on your site. You can also set this directly on the main Blocks administration page. See also Display your theme's block regions. ◦ Visibility settings - Fine-grained block placement controls. ▪ Pages - You can define which pages the block should or should not be displayed on by selecting the appropriate radio button. Specify one page per line by their paths. The '*' character is a wildcard. The path "blog" would display the block on the page http://example.com/blog and the path "blog/*" would display it on every blog page. To display the block only on the front page (or on every page except the front page, depending on your choice of radio button), enter "<front>". ▪ Content types - Select one or more of your site's content types to have the block shown only on pages of the selected content type(s). If you don't select any content types, the block's display will no be limited by content type (i.e. it will be shown on all pages that meet your other display condition regardless of content type). Show this block only on pages that display content of the given type(s). If you select no types, there will be no typespecific limitation. ▪ Roles - Select one or more roles to have the block shown only to users with the selected role(s). If you don't select any roles, the block will be visible to all users. ▪ Users - Set whether users can set this block's visibility on their user account page. • Click "Add block" Move a block Select a block region from the drop-down under "Region" for any block on the Blocks page at Structure > Blocks
Make a block only appear on certain pages See: Make a message or banner appear only on selected pages. Hide/Disable a block Set region to <none> for any block on the Blocks page at Structure > Blocks to deactivate it. Example: Hide the User login block - The User login block is presented by default to all anonymous site visitors (those not registered and logged in to your site). On the Blocks admin page at Structure > Blocks you can disable the User login block from your current front-end theme (as opposed to the admin area theme) by changing its Region setting to "<none>" and clicking "Save blocks" at the bottom of the page.
Create dynamic pages and blocks - Simple Views When your site starts to fill up with content, you will probably want visitors to be able to find specific content, posts or information without having to page through all the pages on your site. Activating the search block is one solution, but you can also make dynamic pages and blocks featuring specific information you want users to find and see. What are dynamic pages? You can think of a "dynamic page" as a filtered list of content from your site. It can be filtered to show specific content like articles tagged with a specific term. The page is "dynamic" because new content that matches the filter will be added to the page as it is created. Using Simple Views, you can select what content to present and what order it should be presented in. What are dynamic blocks? Dynamic blocks can present a certain number of node titles and/or teasers as a preview or highlight of content you wish to promote.
There are three kinds of elements needed to build simple views: • Filter criteria - "Display" and "Limit to tags" determine what content will be included in a simple view. • Display settings - "Title", "Sorted", "As a", and "Show" determine how the selected content will be presented. • Functional elements - "Path", "Add an RSS feed", "Expose a block" Build a view • Navigate to Simple Views at Structure > Simple views • Click "Add view" and design your Simple view: ◦ Title (display) - Page or block title displayed to site visitors ◦ Path (URL) - URL of the simple view page: "lobster" would create the page at http://example.com/lobster. ◦ Display (filter criterion) - Select from all standard and custom content types on your site. "All posts" would include content of all content types in your simple view. ◦ Sorted (display) - The display order of the content in your simple view: ▪ newest first ▪ oldest first ▪ by title (alphabetically) ▪ by number of hits (how many times a node has been visited) ◦ As a (display) - How to display the content: ▪ List of full posts - shows complete nodes ▪ List of teasers - shows titles and teasers ▪ List of titles - show titles only ▪ Table with overview data - Overview table ◦ Limit to tags (filter criterion) ◦ Show (display) - How many items to display per page ◦ Add an RSS feed - Make an RSS feed of your simple view available. The RSS feed of the path "lobster" (http://example.com/lobster) would be http://example.com/lobster/feed. ◦ Expose a block - Makes a block of your simple view available. Go to the Blocks page at Structure > Blocks to activate it and place it in a block region on one or more pages or your site. ▪ Show - How many items to display in the block. ▪ As a (display) - How to display the content: ▪ List of full posts - shows complete nodes ▪ List of teasers - shows titles and teasers ▪ List of titles - show titles only ▪ Table with overview data - Overview table
Edit or delete existing Simple Views Once your view has been created, it is added to the list of views at Structure > Simple views and can be edited or deleted any time. Create a link or menu entry to a view Click on the view's link in the "Path" column to see the view and its URL. Add that URL to a navigation menu of your choice.
Organize your content in books "Books" in Drupal are sets of nodes that have been hierarchically organized into sections (chapters) and an order (like pages in a book). Book navigation - Books have a built-in hierarchical navigation. On any book page, there is a link to its "parent" node and links to the previous and next page. Any page can be a "parent" to "child" nodes below it. Top level nodes are "books" containing lower-level chapters, sections, and pages. Add a content type other than "book page" to a book Although the content type Book page is specifically intended and enabled for use in hierarchically organized "books" of content, any content type can also be included in a book on your site. • Navigate to Content - click the "Books" tab, then the "Settings". • Check the check-box of the content type you want to enable for books under "Content types allowed on book outlines" (those allowed to be bookand chapter headers). • Check the check-box of the content type you want to be the default content type created when clicking the "add a child page link" on a book page under "Content types for child pages". • Click "Save configuration".
Book settings when creating content The following settings apply to content types that are permitted to be book nodes (see above): • Book - Select an existing book on your site for the new node to be a part of or "<create a new book>" to make the new node the top-level node of a new book. ◦ Select "<none>" to save the node outside of book hierarchies. • Parent item - If the book you are adding a page to already has pages, you can select any existing page to be the new node's "parent". This makes the parent page a chapter or section header. • Weight - By default, chapters, sections and pages will be sorted and displayed alphabetically by node title within their hierarchical level. You may change this order by giving one or more children of any parent a "weight" value: A "lighter" item with a lower number will "float" higher in a list than a "heavier" item with a higher number (and hence a heavier "weight").
Site-Internal Links - tips • Always use "open" internal links: When creating links from one pages of your Drupal Gardens site to another, use "open" paths that begin with a "/" slash like this: <a href="/path/to/content">some text</a> ◦ Drupal will automatically interpret these as being internal links and add the current domain name. ◦ If you ever change your domain name within Drupal Gardens or export your site and republish it under a new URL, these links will all still work. • Do not use full paths like this: <a href="http://yoursite.com/path/to/content">some text</a> or this <a href="http://yoursite.drupalgardens.com/path/to/content">some text</a> ◦ If you change your domain name, these links will no longer work. back to top
USERS User registration Registration page - People may register on your site by visiting the http://example.com/user page of your site (substituting your site's URL for "example.com"). Approval setting - On the Account settings page at Configuration > Account settings you can define whether their accounts need approval from a site administrator before they can access content and functionality only available to authenticated (i.e. loggedin) users. Welcome e-mails - You can customize the e-mails your site sends out when users register for your site and are approved or denied in the e-mails panel at the bottom of the page.
User roles and permissions - access to functionality and content What site visitors and registered users may see and do on your Drupal Gardens website is determined by the combination of their "user role(s)" and the permissions assigned to the role(s) they possess.
User roles User roles are controlled on the page at People > Permissions tab, "Roles" link
Drupal Gardens comes with four standard roles (anonymous, authenticated, site owner and administrator) and more can be added to suit your needs and workflow. Typical custom user roles include: editor, author, themer, content creator, editor, site manager, moderator and so on. Users may be assigned any number of roles. Standard user roles • Anonymous - All site visitors not logged into your site have this role. The permissions assigned to "Anonymous" determine what they can see and do on your site. Give this role as few permissions as possible while still allowing these visitors access to, for example: content, leave comments and use your contact form. • Authenticated - All site visitors who are registered users on your site and logged in have this role. • Administrator - This is a special "super-user" role. It is always assigned every permission for every module activated. Administrators have full access to all available functionality on your site. Only assign this role to other users whom you trust implicitly. • Site owner - This role is equivalent to the Drupal-standard "Administrator" role as long as your site is running in Drupal Gardens. If you export your site and install it outside of Drupal Gardens, the Drupal-default "Administrator" role will continue to receive all permissions, but the Drupal-Gardens-specific "Site owner" role will no longer do so.
User permissions User permissions are controlled on the page at People > Permissions tab, "Permissions" link
Drupal Gardens comes with a set of core access permissions. Most optional modules also add permissions to this page when they are activated. Assign permissions to user roles by checking their check-boxes in the appropriate roles' columns. Edit permissions for a single role - If you have a lot of roles on your website, the "edit permissions" link next to each role on the user roles page is a comfortable way of changing the permissions. The link leads to a page where only the chosen role is listed. Important: â&#x20AC;˘ SECURITY - Many of the permission settings have serious security implications. Check each one carefully and only give sensitive and security-relevant permissions to users you trust. It is generally considered sensible to maintain as restrictive a set of permissions as possible that still allows your site to function as you intend. â&#x20AC;˘ Permissions are cumulative - Users assigned multiple roles will have all of the permissions included in any of their roles. Permissions define what users are permitted to do, not what they are forbidden to do.
â&#x20AC;˘ Site owner and Administrator roles are always assigned all permissions available on your site while it is in Drupal Gardens. If you export your site and install it outside of Drupal Gardens, the Drupal-default "Administrator" role will continue to receive all permissions, but the Drupal-Gardens-specific "Site owner" role will no longer do so.
Create custom user roles and assign them permissions Overview: • Name the new role in the text-entry box at the bottom of the user roles list. • Click "Add role" • Configure the role's permissions (see also: User permissions) Example: create a "blogger" role for guest authors on your site. • Name the new role - Enter "blogger" in the available text field • Click "Add role"
• Click "Edit permissions" next to the newly created role.
• Assign permissions to the new role - Give the role a set of permissions like the following. • Suggested permissions - (change as appropriate to your site, content types and workflow) Note: Permissions are cumulative and all custom roles automatically have all permissions assigned to the "Authenticated" user role (to all logged in users). Any permissions you give to other roles are always in addition to those (see also: User permissions). ◦ Comment ▪ View comments ▪ Post comments without approval ▪ Edit own comments
◦ Comment Notify ▪ Subscribe to comment notifications ◦ Node ▪ View content revisions ▪ Create new Blog entry content ▪ Edit own Blog entry content ▪ Delete own Blog entry content ▪ Create new Poll content ▪ Edit own Poll content ▪ Delete own Poll content ◦ Poll ▪ Vote on polls ▪ View voting results ◦ Statistics ▪ View content access statistics ▪ View content hits
Give other users access to your site while it is in maintenance mode If you want your collaborators to be able to access and modify your site while it is in maintenance mode, but not to have the full access of the Administrator role: • Create a new user role (i.e. site tester, themer, author, etc.) • Assign permissions to the role as needed and include "Access site in maintenance mode" permission. • Add the new role to the tester users it by editing their profile page. See User roles and permissions for more information
User avatars Users can add an "avatar" to their profile - a picture to represent themselves on your site. Site administrators can set these to be shown on nodes and comments users create and upload a site-wide default avatar for those users without their own, personal avatars. Add or change personal user avatar Users can add or change their personal avatar by editing their profile page located at the "/user" URL (http://example.com/user) or by clicking the "Hello [username]" link at the right of the administrative menu bar, then clicking the "edit" link.
Default site-wide avatar For users who have no personal avatar, Drupal Gardens includes a default site-wide avatar image.
Custom site-wide avatar Replace the default site-wide avatar with one of your choice: • • • • •
Deselect "Use the default avatar" check-box Click "Browse" Select an image from your file system Click "Save configuration" at the bottom of the page Once the image is uploaded, its path is displayed, enabling you to use the image in other contexts on your site. • Replace your default avatar by clicking "Browse" under "Upload custom avatar image" on this page.
Site-wide avatar settings • Avatar display - You may set user avatars, including the side-wide default avatar, to be displayed on nodes, comments or both. • Check the check-boxes that suit your site's needs and click "Save configuration". • Deselecting both check-boxes turns off the display of user avatars entirely.
back to top
LAUNCH YOUR SITE! Check, test double check. Click through your site and perform basic checks that everything works as it should: • Do all links and menus work? Do they send you where they should? • Is your contact form correctly configured? Do the e-mails it generates arrive where they should? • Is your content all there? Static pages ("about us", etc.), front page, blog posts, etc.? • Is everything spelled right? Fix any broken links or other problems you find before you launch your site.
Did you add custom CSS in the ThemeBuilder? Check your site in multiple browsers. If you added custom CSS to your site's theme on the "Advanced" tab of the ThemeBuilder, be sure to check in several different web browsers that your site looks as you expect. Internet Explorer - Note that Drupal Gardens is not compatible with Internet Explorer 6 or earlier.
Create site-tester role, give access to offline mode and let test. Now you should let someone your trust (or several people) else click through your site to find any problems you may have missed. Ask your tester(s) to perform the basic checks as listed above and to keep an eye out for anything else that might be unwanted, unplanned or broken. Create a user role called "tester": • Navigate to the User roles page at People > Permissions tab, "Roles" link. • Enter the role's name in the text-entry box at the bottom of the user roles list.
• Click "Add role" • See User roles for more information. Configure the tester role's permissions: • Navigate to the User permissions page at People > Permissions tab, "Permissions" link. • Add permissions to the "tester" role - Check the check-boxes next to the permissions that will allow these users to see and do what normal site visitors should be able to do (for example: access content, make comments, etc.), click "Save permissions" to commit your changes. • See User permissions for more information. Fix any broken links or other problems you find before you launch your site!
3, 2, 1 ... Launch! Take your site out of maintenance mode. • Navigate to the Maintenance mode page at Configuration > Maintenance mode • Un-Check the check-box labeled "Put site into maintenance mode". • Click "Save configuration". See Maintenance mode - Keep your site offline until you are ready to launch for more information. back to top
MODULES A Drupal module is a collection of code that enables specific functionality – a self-contained functional component of the Drupal system. Drupal Gardens comes with a selection of preinstalled modules.
Activate/Deactivate modules Activate and deactivate modules on the Modules page at Modules. Check the activation check-box of a module and click "Save configuration" at the bottom of the page. If the module you are activating depends on another module for its functionality - in Drupal terms a "dependency" - you will be shown a message about this and any other necessary modules will also be activated at the same time. Check user permissions - Most modules create a set of permissions when activated. Every time you activate a module, check the user permissions page at People > Permissions tab, "Permissions" link, to make sure you, your collaborators and your site visitors are either permitted or blocked access to module functionality as appropriate. Module blocks - Some modules make new blocks available when they are activated. Check the Blocks page at Structure > Blocks.
Configure modules Administer by module - The easiest way to get an overview of any of your modules configuration check the "Administer by module" page, which give links to each activated module's configuration page, permissions page and so on.
To get to it, click the "Administer" link at the top left of any administrative page. You will be taken to the administrative overview where you can choose the "by module" tab.
Configure the Mailing list module Collect site visitor e-mail addresses - This simple module allows you to collect email addresses and export them for use in e-mail applications. â&#x20AC;˘ Activate the Mailing list module - Navigate to Modules, check the Mailing list module check-box, click "Save configuration" at the bottom of the page. â&#x20AC;˘ Add one or more mailing lists - Navigate to Structure > Mailing lists, click the "Add" link, name your list and click "Save".
• Customize the sign-up confirmation message by clicking on the "Settings" link and saving any changes you make. In any message, the "%mail" token will display the e-mail address the user entered to sign up and the "%name" will show the name they enter in the sign up form.
• Export mailing list - Download a CSV file of usernames and e-mail addresses to manage and use your mailing list in e-mail, spreadsheet and other applications. • Other functionality ◦ List e-mails - show names and e-mails signed up for a mailing list. ◦ Add e-mail - manually add an e-mail to a mailing list ◦ Import e-mails - import e-mails into a mailing list (for future functionality additions) ◦ Rename list - rename a mailing list ◦ Delete list - delete a mailing list - Important: this also deletes all the names and e-mail addresses signed up for the mailing list
Configure the Comment Notify module The Comment Notify module allows site visitors to follow discussions happening on your site without having to log in and check individual threads one by one. By leaving a comment on a node, users can subscribe to e-mail notifications when new comments are left by other users. Enabling subscriptions - Subscriptions are made possible for any given role by a combination of Comment Notify module settings, content type settings, and permissions. Perform the following steps in this order: 1) Comment Notify module settings • Enable notification - On the Comment notify settings page at Configuration > Comment notify, enable comment notification on the content types of your
choice.
• Global comment notification settings ◦ Available subscription modes - Define what type(s) of subscriptions are available to users. Select one or both check-boxes from "All comments" and "Replies to my comment". ◦ Default state for the notification selection box - For both anonymous and registered users, select from "No notifications", "All comments", and "Replies to my comment" ◦ Automatic comment subscriptions can be activated by checking the check-box labeled: "Subscribe users to their node follow-up notification emails by default." Users can change this setting globally in their profile or on specific nodes when posting comments. ◦ E-mail to commenters and node authors - These fields contain the templates for e-mails that will be sent when comments are made on content users have subscribed to. There are separate templates for node authors and commenters. ▪ Text replacement tokens - In both e-mail templates, you will notice placeholders in square brackets like [user:name] and [node:title]. When subscription e-mails are generated, these so-called "tokens" are replaced with the appropriate information for the content in question. Note - The final set of tokens for the Drupal 7 version of this module has not been finalized and fully implemented. Some of the following tokens might not work: ▪ [comment:name] - username of the user who posted the comment ▪ [comment:unsubscribe_url] - an auto-unsubscribe link for the comment thread ▪ [comment:url] - a link to the comment ▪ [node:summary] - The "teaser" of the node commented on ▪ [node:title] - The title of the node commented on ▪ [site:name] - The name of your site (set at Configuration > Site information) ▪ [site:url] - The URL of your site ▪ [user:name] - The username of the author of the node commented on 2) Content type settings - Edit the content type(s) for which comment notification
subscriptions are enabled by navigating to the Content types page at Structure > Content types and clicking the "edit" link for the content type(s) in question. On the comment settings panel at the bottom of the content type edit page: • Default setting for new content - Make sure the content type(s) on which you intend to allow user comments and comment subscriptions have this set to "Open" under "Comment settings".
3) Permissions - On the permissions page at People > Permissions tab, "Permissions" link, give the following permissions to the user roles to allow them to subscribe to comment notifications: • Node: View published content • Comment: View comments • Comment: Post comments (with or without approval, whichever suits your site's workflow best) • Comment notify: Subscribe to comment notifications
Permissions note - user roles: • Anonymous user subscriptions - For anonymous (non logged-in) site visitors to be able to subscribe to comment notifications, one additional permission is necessary: ◦ Edit the content type(s) for which comment notification subscriptions are enabled by navigating to the Content types page at Structure > Content types and clicking the "edit" link for the content type(s) in question. ◦ On the comment settings panel at the bottom of the content type edit page, select either "Anonymous posters may leave their contact information" or "Anonymous posters must leave their contact information".
• Authenticated user subscriptions - Enabling comment notification subscriptions for the "Authenticated" user role enables subscriptions for all logged in users, whatever other roles they may have.
â&#x20AC;˘ Role-specific user subscriptions - Instead of allowing all logged in users to subscribe to comment notifications as described above, you can instead give the same permissions to one or more specific user roles. back to top
Registering and configuring custom domain names You can give your Drupal Gardens website any domain name that you own or control. If you don't already have the domain name you'd like to use, first, you'll need to buy an available domain, and then point ("map") it to your Drupal Gardens website. 1. Buy your domain name - When you have found an available domain name, you need to purchase it via a "domain registrar" service. In some cases, it can take up to 48 hours for your purchase and domain registration to be completed. 2. "Map" your domain to your Drupal Gardens site. If you already own or control the domain name you want to use, point your domain name to Drupal Gardens. Follow your domain registrar's instructions to change your domain name's "CNAME record" to point to your Drupal Gardens site's canonical domain name, that is the full name of your site, something like anysite.drupalgardens.com. In some cases, it can take up to 48 hours for domain forwarding changes to take effect. Is my domain mapped correctly? Check your CNAME record Once you have followed the steps outlined here, you can check that your domain name's CNAME record is set up correctly and pointing to Drupal Gardens: 1. Navigate to http://www.zoneedit.com/lookup.html 2. Enter your domain name in the "DNS lookup" box #1 3. Set the drop down menu (box #2) from to "CNAME" 4. Click "Lookup" 5. If the record is set up correctly, the result will be yoursite.drupalgardens.com. Drupal Gardens support cannot assist you until the records are set and propagated.Once the CNAME record is set and correct, it can still take up to 48 hours for the records to be propagated and the Drupal Gardens servers to be able to 'find' your CNAME and be able to activate it for your account. Check and, if necessary, repeat the steps you took to map your domain to your Drupal Gardens site. You may also wish to contact your domain registrar or DNS provider for assistance.
Forward your top-level domain to Drupal Gardens 1. Buy a domain name from a domain registrar service, for example: mydomain.com. 2. Find out how to manage your domain name's DNS - In most cases, you can access DNS controls by logging in to your domain registrar's website. Contact your
3. 4.
5. 6.
domain registrar (or DNS provider if you use a separate service) for information if necessary. Create the "www" sub-domain of your top level domain (www.mydomain.com) following your domain registrar's instructions. Point the "www" sub-domain to your Drupal Gardens site (using CNAME) Use your provider's DNS manager to create a "CNAME record" (or "CNAME entry") for a sub-domain of your top-level domain name that points to your Drupal Gardens site. â&#x2014;Ś For example, if your Drupal Gardens site is yoursite.drupalgardens.com, the CNAME entry for a sub-domain like www.mydomain.com should point to yoursite.drupalgardens.com. â&#x2014;Ś Note: Not all domain registrars offer DNS services, and not all DNS services allow CNAME record changes. Be patient - It can take up to 24 hours for forwarding and CNAME entries to propagate across the Internet. Add the "www" sub-domain to your Drupal Gardens site 1. Log in to your Drupal Gardens website. 2. Click "My sites" in the administration menu bar.
3. Select "Manage domains" from your site's "Actions" dropdown menu.
4. Enter your sub-domain name (like www.mydomain.com) into the "Add a domain" field.
5. Note: If your domain's CNAME record has not been created properly or if it has not yet fully propagated, you will not be able to add it to your Drupal Gardens site. Wait some time and try again. 7. Your "www" sub-domain will now direct visitors to your Drupal Gardens website and all its URLs will be listed, for example, as www.mydomain.com/nicecontent, instead of yoursite.drupalgardens.com/nice-content. 8. Forward your top-level domain to your "www" sub-domain - Most people want their site address to work both with and without the prefix "www". Once the sub-domain, www.mydomain.com is pointing to your Drupal Gardens site, you can forward the top-level domain (mydomain.com without the "www" in this case) to the "www" sub-domain pointing to your Drupal Gardens site. Visitors can then find your site whether they include "www" in front of the domain name or not.
Map a sub-domain only (not "www") If you already have a site running at mysite.com, you can run a campaign site, a blog, forums or something else in Drupal Gardens using a sub-domain of your main domain name like product.mydomain.com, blog.mydomain.com, forums.mydomain.com or similar. 1. Create a sub-domain - Some domain registrars require you to set up sub-domains separately (some do this automatically when you create a CNAME record for a subdomain). Create a sub-domain in your domain's DNS records like blog.mydomain.com. 2. Point the sub-domain to your Drupal Gardens site (using CNAME) - Use your provider's DNS manager to create a "CNAME record" (or "CNAME entry") for a subdomain of your top-level domain name that points to your Drupal Gardens site. â&#x2014;Ś For example, if your Drupal Gardens site is yoursite.drupalgardens.com, the CNAME entry for a sub-domain like blog.mydomain.com should point to yoursite.drupalgardens.com. â&#x2014;Ś Note: Not all domain registrars offer DNS services, and not all DNS services allow CNAME record changes. 3. Be patient - It can take up to 24 hours for this CNAME entry to propagate across the Internet. 4. Add your sub-domain to your Drupal Gardens site 1. Log in to your Drupal Gardens website. 2. Click "My sites" in the administration menu bar.
3. Select "Manage domains" from your site's "Actions" dropdown menu.
4. Enter your sub-domain name, blog.mydomain.com into the "Add a domain" field.
5. Note: If your domain's CNAME record has not been created properly or if it has not yet fully propagated, you will not be able to add it to your Drupal Gardens site. Wait some time and try again. 5. Your "www" sub-domain will now direct visitors to your Drupal Gardens website and all its URLs will be listed, for example, as www.mydomain.com/nicecontent, instead of yoursite.drupalgardens.com/nice-content.
Set up domain mapping on GoDaddy The following example explains the domain forwarding procedure on GoDaddy.com. The exact controls and terminology may differ at other domain registrars. Screenshots in these instructions appear below the step they illustrate. â&#x2014;Ś Navigate to godaddy.com and login â&#x2014;Ś Click the "Domains" menu item, then "Manage Now" under "Manage My Domains" (screenshot below):
â&#x2014;Ś Select a top-level domain (yoursite.com) - Click the domain name you want to use in Drupal Gardens to go to its management page.
â&#x2014;Ś Forward top-level domain yoursite.com to www.yoursite.com - On the Domain Management page, click the "Forward" link (a curved green arrow icon) and select "Forward Domain". Forward your top-level domain, yoursite.com to www.yoursite.com:
â&#x2014;Ś Is it done yet? - This may take a few minutes to reset. When the process is has been completed, you will see under "Domain Information" on the main Domain Manager page that your domain is now being forwarded to www.yoursite.com.
â&#x2014;Ś Click "Total DNS Control" under "Total DNS" on the Domain Management page.
â&#x2014;Ś If your domain name was previously pointed at another server or service, you may have to clear any changes to its "CNAME", "MX" or other records. GoDaddy provides "Reset to Default Settings" buttons for this purpose. Even if you are not sure whether you have made changes to these settings in the past, clicking reset won't cause any harm!
â&#x2014;Ś Set "A Record" to GoDaddy forwarding IP address - For a GoDaddyregistered domain to be forwarded to another domain name, its "A Record" must point to the following IP address: 64.202.189.170
▪ Click the edit link under "A (Host)" ▪ Enter "@" under "Host name" ▪ Enter 64.202.189.170 under "Points To Ip Address"
◦ Forward www.yoursite.com to your Drupal Gardens site ▪ Click the edit link for "www" under "CNAMES (Aliases)" ▪ Enter "www" under "Enter an Alias Name" ▪ Enter your drupalgardens domain name (anysite.drupalgardens.com)
â&#x2014;Ś Be patient - It can take from 30 minutes up to several hours for domain forwarding changes to take effect. â&#x2014;Ś Add domain name to your Drupal Gardens site - Once the changes above have been propagated, you can add your custom domain name to Drupal Gardens. Important: you must add the "www" version of your domain name to your Drupal Gardens domain since it is the "www" CNAME record that is pointing to Drupal Gardens, not your top-level domain name, which is forwarded to the "www" version: 1. Log in to your Drupal Gardens website. 2. Click "My sites" in the administration menu bar.
3. Select "Manage domains" from your site's "Actions" dropdown menu.
4. Enter your domain name prefixed with "www" www.mydomain.com into the "Add a domain" field.
5. Note: If your domain's CNAME record has not been created properly or if it has not yet fully propagated, you will not be able to add it to your Drupal Gardens site. Wait some time and try again.
Add new CNAME Records for sub-domains You can also point a "sub-domain" of your domain name to your Drupal Gardens site. For example, you could run yoursite.com on any web platform or service
and a sub-domain on Drupal Gardens or even multiple Drupal Gardens websites as sub-domains of a single domain name. â&#x2013;Ş In this example, if your domain name is yoursite.com, goodstuff.yoursite.com will now point to mysite.drupalgardens.com. â&#x2013;Ş Since the sub-domain is pointed directly to your Drupal Gardens site, you can add it as-is (without "www") to your Drupal Gardens site in the domain manager.
back to top Have feedback on the documentation? Post it in the Drupal Gardens user forums.