Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Standing up for the content creators: Site building and theming for the administrators | Drupal Presentation

1,020 views

Published on

Let us stand up together for the administrators and content creators. They are the ones who are going to spend more time on the site than anyone else after we are gone. These are the people who will stand up for us, and stand up for Drupal in the future. We must do everything in our power to make them as successful as possible.

When we develop sites in Drupal, we model the content architecture. We develop the site functionality. We weigh the balance between design and performance, mobile versus desktop, user and business goals. But oft-forgotten are those who are going to spend more time on the site than anyone else after we are gone, the site administrators and content creators.

This presentation will encompass the planning and implementation of roles, permissions, and workflows for administrative users. We will cover installing, and uninstalling modules; and organization/simplification techniques that will make the user interface streamlined, and help content creators be as productive as possible.

We will also cover ways to write training instructions that can be included in the admin interface, or kept externally on a company handbook or shared drive.

Published in: Software, Internet
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Standing up for the content creators: Site building and theming for the administrators | Drupal Presentation

  1. 1. STANDING UP FOR THE CONTENT CREATORS SITE BUILDING AND THEMING FOR THE ADMINISTRATORS Created by Jim Birch jimbir.ch/standing-up @thejimbirch Xeno Media, Inc.
  2. 2. ADMIN MENU, ORGANIZED, BUT STILL SO MANY LINKS!
  3. 3. ANOTHER VIEW, LISTING THEM ALL ON ONE PAGE
  4. 4. THAT KEEPS GOING...
  5. 5. AND GOING...
  6. 6. AND GOING...
  7. 7. AND GOING...
  8. 8. AND GOING...
  9. 9. AND THIS IS A PRETTY SIMPLE SITE!
  10. 10. SAME GOES FOR THE CKEDITOR. SO MANY OPTIONS...
  11. 11. BUT REALLY, ONLY A FEW THINGS ARE TRULY NEEDED.
  12. 12. WHO ARE OUR CONTENT CREATORS?
  13. 13. COMMON ADDITIONAL ROLES: Webmasters Editors Authors CONTENT SPECIFIC ROLES SUCH AS: Bloggers Press Releasers TASK SPECIFIC ROLES SUCH AS: Community Manager
  14. 14. PLANNING & MANAGING DRUPAL PROJECTS BY DANI NORDIN http://www.amazon.com/dp/1449305482/
  15. 15. ONCE WE KNOW WHO, WE CAN START FIGHTING FOR THEM.
  16. 16. BEFORE WE BEGIN, LET'S TALK ABOUT INSTALLING/UNINSTALLING MODULES. USING DRUSH drush dl -y module_name drush en -y module_name drush dis -y module_name drush pm-uninstall -y module_name
  17. 17. IN THE UI Turn off (disable) Uninstall (removes database bits) Delete module folder by hand/in git
  18. 18. THEMING THE DRUPAL ADMINISTRATION UI
  19. 19. CHOOSING ADMIN THEMES
  20. 20. ADMINISTRATION THEME OPTIONS Choose a separate admin theme Use your front end theme Develop your own admin theme
  21. 21. BLOCK SYSTEM APPLIES TO ADMIN THEMES TOO!
  22. 22. GLOBAL CHANGES ENABLE ADMIN TOOLBAR, DISABLE OVERLAY drush en -y admin_menu admin_menu_toolbar drush dis -y toolbar shortcut drush dis -y overlay
  23. 23. CONTENT TYPE & TAXONOMY DEFAULTS Title Label Explanation or submission guidelines (Help) Administrative Description Default Publishing State, Revisions Author, Menu, Sitemap, (other modules), etc
  24. 24. PALANTIR.NET BUILD SPEC SPREADSHEET https://www.palantir.net/blog/developing-drupal-sites-plan-or-perish
  25. 25. FIELD DEFAULTS Help text Default text format Module Settings (Linkit, Fences) Number of values for the field Images: File Directory, Types, Alt, etc
  26. 26. TITLE MODULE https://www.drupal.org/project/title Makes Title a field. Made for Translations, but great for gaining control of Title and using in Display Modes.
  27. 27. HIDE STICKY & PROMOTE https://www.drupal.org/sandbox/studiozut/2303677 Simple custom module that removes the "promote to front page" and "sticky" checkboxes from the node add and edit screens. OVERRIDE NODE OPTIONS https://www.drupal.org/project/override_node_options Use this module if you need to control these settings and more per Role.
  28. 28. SIMPLIFY https://www.drupal.org/project/simplify Hide so many of the things Globally or on each: Content type Taxonomy Block Comments User User profile
  29. 29. FIELD GROUP https://www.drupal.org/project/field_group Add organizing elements to Node Add/Edit, and Node Displays.
  30. 30. FIELD GROUP TYPES Fieldsets Horizontal tabs Vertical tabs Accordions Divs (Good for Grid Systems) HTML elements Lots of modules that extend.
  31. 31. ENVIRONMENT INDICATOR https://www.drupal.org/project/environment_indicator Not just for Developers! Use when clients have access to test & staging servers
  32. 32. DASHBOARD(S) There are many different ways to create a landing page for the logged in administrator. Default "content" screen Dashboard module Workbench Dashboard Custom Made Admin View My suggestion is to choose one way, and make it great.
  33. 33. THEMING CKEDITOR
  34. 34. COMMON TASKS Add only relevant buttons needed for the field Exclude security risks (filters) Remove markup already in templates like H1, and add formats (classes). Configure Allowed content so classes aren't stripped, set height, etc. CKEditor 4.3+ Widgets -- .Widgitizing Widgets by bneil
  35. 35. UPLOADING IMAGES IN THE WYSIWYG What types of files can be uploaded? What thumbnails are created for admin use? Where can they be uploaded? CKFINDER Set Different upload folders per Content Type. Make a Profile Type and Text Format for each Content Type. IMCE Set Different upload folders per User Role. Can do user/userid or year/month (like Wordpress)
  36. 36. PARAGRAPHS MODULE https://www.drupal.org/project/paragraphs Instead of trying to make the WYSIWYG do everything, you can add different types of fields.
  37. 37. ADMINISTRATIVE WORKFLOWS
  38. 38. SCHEDULER Each content type can be scheduled. Which need to be? Who can? Set up external Cron
  39. 39. WORKBENCH Each content type can have more statuses than Published. Workbench Moderation adds Draft and Needs Review by default, but can add custom ones you create. Workbench Access can restrict access to different sections of the site based on menu or taxonomies. Workbench Media adds integration with either the 1.x or 2.x of the Media Module!
  40. 40. DOCUMENTATION
  41. 41. INLINE Content Types, Fields, Blocks, Views, Panels, etc all provide places to enter descriptive and instructional text for administrative users Content Types and fields allow for HTML, (link to…)
  42. 42. ADVANCED HELP MODULE https://www.drupal.org/project/advanced_help For custom modules, developers can include HTML files that can be linked to from any ADMIN UI screens the module creates.
  43. 43. GOOGLE DOCS/DROPBOX/COMPANY INTRANET Keep a master copy, organized folder, shared with those who will help you maintain. Export PDF for users, shared with appropriately role'd users Authors can access author docs Editors can access author and editor docs Webmasters can access author, editor, and webmaster docs and so on.
  44. 44. TESTING AND TWEAKING Things change up to the last minute before a launch, and many times after that! Do not get stuck in the habit of just using the developer's administrator role. Use the site early and often as the Webmaster, Editor, and Author. Step through the documentation defined tasks, verify all can be done. Adjust permissions as you go.
  45. 45. HOW TO BE ANOTHER Masquerade Module Create different accounts Gmail Users can use the plus trick jim+webmaster@ jim+editor@ jim+author@
  46. 46. THE END CONTINUING THE CONVERSATION: Created by Jim Birch jimbir.ch/standing-up @thejimbirch Xeno Media, Inc.

×