Tailor your backend to meet the clients needs
Out of the box, the Drupal backend interface compares to a jumpsuit with an expensive toolbelt full of equipment. Tailored for the needs of site-builders and developers, the Drupal backend is a great costume for day-to-day work. It is not something you would wear to cocktail parties, though. Each client has its own demands In this presentation we will look for ways to tailor the backend to meet the clients' needs. A custom tailored backend has a huge return on invest. The client feels comfortable with the backend. Allow them to get the best, with the tools they need. Training workshops will be easier, allowing you to focus on what's important Reduce the amount of support to give, after your project is delivered Blow the clients mind when they first visit the site, they will be more forgiving about remaining issues This presentation shows modules (multiple_value_widget, display suite, field_group, formbuilder, views_megarow ...), admin themes (shiny, adminimal), tips, tricks, and even some code snippets for further enhancements of the backend. (No coding experience is required) For Drupal 8, the one-size-fits-all backend has already been greatly improved. Some example's will be given on how Drupal 8 accomplishes certain tasks, and how we can use them in Drupal 7. After this presentation, i advise you to invest one day of the project's lifecycle on backend usability. Let your end-client brag about their tailor made backend at the next cocktail party, and get a great chance at working with their friends.
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Tailor your backend to meet the clients needs
Similar to Tailor your backend to meet the clients needs (20)
Recently uploaded
Recently uploaded (20)
Tailor your backend to meet the clients needs
- 1. TAILOR THE BACKEND TO MEET THE CLIENTS NEED
- 2. IMAGINE.
- 7. IMAGINE. EASY? HAPPY? PROUD?
- 8. STEVEN VAN DEN HOUT @stevenvdhout
- 11. DEFAULT BACKEND GREAT FOR DEVELOPERS
- 12. BACKEND EXPERIENCE CLIENTS ARE PEOPLE TO
- 13. CLIENTS WANT
- 14. CLIENTS WANT DESERVE • The best tools • Easier trainings • Reduced support • Minds blown
- 15. DRUPAL FRAMEWORK TO BUILD CMS
- 16. ONE SIZE FITS ALL BUT NEVER REALLY SUITS
- 17. TAILOR MADE SUITS YOU IN EVERY WAY
- 18. NO BENJAMINS WASHINGTONS WILL DO
- 19. ONE DAY TO SPEND ON BACKEND UX
- 20. GETTING STARTED.
- 21. ADMINIMAL THEME & MENU http://dgo.to/adminimal_theme http://dgo.to/adminimal_admin_menu
- 23. FAST PERMISSION ACCESS http://dgo.to/fpa
- 24. ADMIN MENU SEARCH MOSTLY FORGOTTEN, COMES IN HANDY
- 25. CONTENT LISTING.
- 26. CONTENT LISTING DEPENDING ON THE WEBSITE SIZE
- 27. WEBSITE SIZE NUMBER OF CONTENT CONTENT LISTING THE SIZE OF THE WEBITE vs NUMBER OF EDITORS
- 28. SMALL SITES VBO ADMIN VIEWS
- 29. MEDIUM SITES CATEGORIZE ADMIN MENU
- 30. LARGE SITES PERSONALIZED WORKBENCH USER PAGES
- 31. SEARCH API SOLR FOR THE HEAVY LIFTING
- 33. DRUPAL 8 THE FUTURE IS NEAR DRUPAL 8 VIEWS IN CORE SEARCH API
- 34. NODE FORMS MAKE THE DIFFERENCE
- 35. CKEDITOR ONLY THE BASICS
- 37. DISPLAY SUITE USE DS LAYOUTS ON FORMS
- 38. CONDITIONAL FIELDS USING DRUPAL STATES API
- 40. MULTIPLE VALUE WIDGET http://dgo.to/multiple_value_widget
- 42. TEASER FIELD & MAXLENGTH http://dgo.to/maxlength
- 43. TAILOR MADE REUSABLE COMPONENTS
- 44. ADVANCED FIELDSET MOVE THE VERTICAL TABS
- 46. URL PATH SETTINGS HOW PANOPOLY DOES IT
- 48. MODERATION STATE MOVE TO THE ACTION BAR
- 50. END RESULT JUST A SIMPLE FORM
- 51. INLINE ENTITY FORM http://dgo.to/inline_entity_form
- 52. CONTENT ELEMENTS AN EASY APPROACH TO COMPLEX FORMS
- 54. DRUPAL 8 THE FUTURE IS NEAR DRUPAL 8 INLINE EDIT CKEDITOR IMPROVED FORM
- 56. ADMIN MENU AND PERMISSIONS
- 57. ADMIN MENU SOURCE http://dgo.to/admin_menu_source
- 61. IMAGINE.
- 62. IMAGINE. EASY?
- 65. IMAGINE. EASY? HAPPY? PROUD?
- 66. QUESTIONS?