The Future of the Rules module in Drupal 8
•Download as PPTX, PDF•
0 likes•2,031 views
This is the a briefing about all the information I could find regarding the Drupal Rules module in Drupal 8. I give a status update to on the status of development and give a sneak peak into the UI
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Future of the Rules module in Drupal 8
Similar to The Future of the Rules module in Drupal 8 (20)
Recently uploaded
Recently uploaded (20)
The Future of the Rules module in Drupal 8
- 1. And how we can help shape the story STAN ASCHER
- 2. WHO AM I? • Site Builder • Front End Developer • Themer • Talker
- 3. WHATS GOING ON HERE?
- 4. WHAT AM I TALKING ABOUT HERE • What is Rules and Why its successful • The #drupal8rules initiative • Progress so far • Sneak Peak at UI • Outside integrations • How to contribute
- 5. THE SUCCESS STORY BEHIND RULES
- 6. THE SUCCESS STORY BEHIND RULES: HELPING THE SITE BUILDER
- 7. THE SUCCESS STORY BEHIND RULES: INTERGRATIONS WorkbenchWebform Drupal Commerce Content Access FlagOrganic Groups TokenUbercartVoting Twitter FeaturesContext Message
- 8. PROGRESS : CHALLENGES AND MILESTONES
- 9. FAGO AND KLAUSI Maintainers of the Rules Modules Have lots of other Drupal Modules Contributors to Drupal 8
- 10. FUNDING GOAL & PROJECT DEVELOPMENT HOURS Drunomics and Epiqo can’t afford taking the bill for the entire project. 1048 projected hours of development Companies will charge rate of € 45/h net cost.(
- 11. WHAT’S DONE?
- 12. DRUPAL 8 CORE INTEGRATION & RULES CORE ENGINE: DONE Milestone 1 of Drupal Rules Module Beta • Rules core engine & plug-in types (Services-based architecture, interfaces, tests) • Align Rules condition & action APIs with Drupal 8 core (Dynamic action parameters & context variables) • Parameter configuration & Context mapping • Parameter value processing logic (Data processor plug-ins & Input tokens)
- 13. DRUPAL 8 CORE INTEGRATION & RULES CORE ENGINE: DONE Reusable components • Plug-in based architecture & fully object-oriented code • Rules data selector for tokens, contexts and other use cases • Typed data widgets & formatters
- 14. DRUPAL 8 CORE INTEGRATION & RULES CORE ENGINE: DONE Evolved developer experience Unified DX based on Drupal 8 plug-in system Symfony 2 event system integration Deployable configuration via the CMI • Rules will be in your .yml files • Rules will show up in your Configuration Management Interface
- 15. WHAT’S LEFT?
- 16. MILESTONE 2: RULES CORE API COMPLETION
- 17. MILESTONE 2: RULES CORE API COMPLETION Goal: Ensure the Rules APIs are ready early enough, so all other contributed modules that get ported to Drupal 8 can have Rules integrations right from beginning. • Complete Rules engine features (Metadata assertions, logging service, developer docs) • Rules plug-ins part two (Events, Loops, caching, recursion prevention, components API) • Configuration management system support (config entity, CMI support, integrity checks & config schema) • Generic rules integrations (Typed data & entity support) • Entity token support
- 18. BUT WHAT ABOUT THE SITE BUILDERS?
- 19. THE USER INTERFACE: THE RULES UI
- 20. MILESTONE 3: RULES UI FOR 8.X RELEASE (Goal: Site builders will be able to start configuring workflows on their Drupal 8 sites from November 2014 on, when Rules 8.x will be released. Rules UI (Rules settings and administration screens with Drupal 8 usability improvements) Reusable UI components (Data selector, Typed data widgets and formatters, embeddable condition and action forms) Rules scheduler Port existing Rules integrations (Comments, Nodes, Taxonomy, User, New entity types)
- 21. RETHINKING THE UI • Rules UI should not be its own beast but try to leverage as much of the patterns & UI components that we have in D8 already. • borrow add dialogs from Views UI or Block UI? • try to come up with a draggable table solution that works for nested rule configurations
- 22. D7 BROWSE RULE
- 23. D8 BROWSE RULES
- 24. RULES EDIT SCREEN OVERVIEW
- 25. RULES EDIT SCREEN OVERVIEW: ADD EVENT
- 26. RULES EDIT SCREEN: ADD EVENT
- 27. RULES EDIT SCREEN OVERVIEW: ADD CONDITION
- 28. EDITING A CONDTION GROUP
- 29. EDITING A CONDTION GROUP: CHANGE CONDITION
- 30. EDITING A CONDITION GROUP WITHIN A CONDTION GROUP
- 31. OTHER TECHNOLOGIES RULES LINK MODULE
- 32. OTHER TECHNOLOGIES MAESTRO MODULE
- 33. A WORD ABOUT DRUPAL COMMERCE 8.X Commerce Guys working to make Drupal Commerce independent of the rules module Commerce Guys Ryan Szrama says that Commerce will be able to integrate with Rules 8.x API eventually
- 34. HOW CAN WE HELP? Sign up to be a tester or developer • http://d8rules.org/support Check out the UI Brainstorm page • https://www.drupal.org/node/2251267
- 35. WE CAN HELP SHAPE THE STORY! Drupal 8 rules site Rules 8.x Issue Queue on Drupal.org Rules 8.x on github Rules 8.x Brainstorming #drupal-rules on irc
- 36. WHATCHA TALKIN ABOUT, DAVID?
- 37. WHATCHA TALKIN ABOUT, MICHEAL?
- 38. WHATCHA TALKIN ABOUT, PRINCESS?
- 39. YOU CAN MAKE A DIFFERENCE: DRUPAL IS PEOPLE! Stan Ascher - Twitter: stanascher Drupal.org - sascher
Editor's Notes
- This is the screen as known from "Rules" and "Components" tabs. It provides an overview of all rules matching the criteria The idea here is to provide a visual summary of what's configured in a rule via icons . Each rule element (event, condition, action) gets its icon and a summary if you hover over the icon . Also note that events, conditions and events all get their own geometric shape. On the right side you see a list of available operations , while they plan to leverage drop down buttons to hide away not so common operations like "disable", "export", ... They also plan implement a long overdue feature: descriptions for rule configurations. Ok, so once you edit a rule you'll get to next screen:
- Editing and adding a new rule all happens on one screen. It gives a detailed (not directly editable) overview of the whole rule: If you add or edit something you won't leave the screen - part of the screen will reload to show you the necessary form, while after submitting the form it will reload again and replace the form with the summary of the edited area. For example, when you'd click on the summary or icon of the "Post tweet" action it replaces the summary of the action with an edit form without leaving the page. Once you submit the form it brings you back an updated summary on the overview, while the whole rule won't be saved until you press "Save" at the overview page. For adding a new event, condition or action a greyed out empty element will be already visible. Clicking on it will load the add screen there. More experienced users can also hover over the small points between the icons on the left and get an "Add action" drop down there. This drop-down allows you to add an action at a certain position instead of adding it at the end and moving it around afterwards. Also, it's an "Add action" drop-down as there other not so common choices like "Add loop", but that's hidden away by the drop-down button by default.
- Editing and adding a new rule all happens on one screen. It gives a detailed (not directly editable) overview of the whole rule: If you add or edit something you won't leave the screen - part of the screen will reload to show you the necessary form, while after submitting the form it will reload again and replace the form with the summary of the edited area. For example, when you'd click on the summary or icon of the "Post tweet" action it replaces the summary of the action with an edit form without leaving the page. Once you submit the form it brings you back an updated summary on the overview, while the whole rule won't be saved until you press "Save" at the overview page. For adding a new event, condition or action a greyed out empty element will be already visible. Clicking on it will load the add screen there. More experienced users can also hover over the small points between the icons on the left and get an "Add action" drop down there. This drop-down allows you to add an action at a certain position instead of adding it at the end and moving it around afterwards. Also, it's an "Add action" drop-down as there other not so common choices like "Add loop", but that's hidden away by the drop-down button by default.
- So this is how an "add screen" for events, conditions or actions would look like - in this example we are adding a new event: So instead of the big "select box" which we have now, we'll group available events/conditions/actions by categories ("groups"). Each category will get its own icon which integrating modules can provide. (Yes, we need to come up with a style-guide here!) Once you click on a category item, the list of available items below is instantly filtered by the category. Also, we think that adding a search-box and an optional description to each listed item would make sense here. With that new screen we should be prepared for the number of available events/conditions/actions increasing significantly!
- Editing and adding a new rule all happens on one screen. It gives a detailed (not directly editable) overview of the whole rule: If you add or edit something you won't leave the screen - part of the screen will reload to show you the necessary form, while after submitting the form it will reload again and replace the form with the summary of the edited area. For example, when you'd click on the summary or icon of the "Post tweet" action it replaces the summary of the action with an edit form without leaving the page. Once you submit the form it brings you back an updated summary on the overview, while the whole rule won't be saved until you press "Save" at the overview page. For adding a new event, condition or action a greyed out empty element will be already visible. Clicking on it will load the add screen there. More experienced users can also hover over the small points between the icons on the left and get an "Add action" drop down there. This drop-down allows you to add an action at a certain position instead of adding it at the end and moving it around afterwards. Also, it's an "Add action" drop-down as there other not so common choices like "Add loop", but that's hidden away by the drop-down button by default.
- As you may know Rules supports groups of conditions and actions, i.e. condition or action plugins containing other conditions or actions - such as logical OR or AND elements or LOOPs. If you have a look back to the "Rules edit screen" you notice a condition group there which contains two conditions. In the overview this renders just as known from the "browse rules" screen, so you get an overview of what's in there. If you edit this condition group, you'll get to that screen: The list of contained items (conditions here) will move from the horizontal line to the usual vertical arrangement on the left with the summary of each item on the right - so it renders the same way as top-level conditions on the "rule edit overview" screen. Above of the contained conditions the settings of the whole condition group are rendered and may be edited with the usual approach: A click on it replaces the summary with an edit form and submitting that brings you back to an updated summary.
- As you may know Rules supports groups of conditions and actions, i.e. condition or action plugins containing other conditions or actions - such as logical OR or AND elements or LOOPs. If you have a look back to the "Rules edit screen" you notice a condition group there which contains two conditions. In the overview this renders just as known from the "browse rules" screen, so you get an overview of what's in there. If you edit this condition group, you'll get to that screen: The list of contained items (conditions here) will move from the horizontal line to the usual vertical arrangement on the left with the summary of each item on the right - so it renders the same way as top-level conditions on the "rule edit overview" screen. Above of the contained conditions the settings of the whole condition group are rendered and may be edited with the usual approach: A click on it replaces the summary with an edit form and submitting that brings you back to an updated summary.
- So, now what if you edit a condition within a condition group? We'll just repeat the pattern and turn the condition into edit mode: Of course, this could be nested arbitrarily as you can do that now. While it will work, it won't look very nicely with multiple nested groups - just as now. I do not think this is the 90% use-case to cater for, so that should be enough.
- This is Maestro
- This is Maestro