Today we are talking about Accessibility from the sales process to delivery with Kat Shaw.
For show notes visit: www.talkingDrupal.com/395
TopicsNic Laflin - www.nLighteneddevelopment.com @nicxvan John Picozzi - www.epam.com @johnpicozzi Kat Shaw - drupal.org/u/katannshaw @katannshaw
MOTW CorrespondentMartin Anderson-Clutz - @mandclu Gesso A Sass-based, Webpack-based, and Storybook integrated accessible starter theme.
We're excited to announce the latest release of DXPR Builder, version 2.2.3! In this update, we've added several new features and enhancements that will improve your experience as an editor while building web content with DXPR Builder. Let's take a closer look at what's new in DXPR Builder 2.2.3.
We've introduced two new keyboard shortcuts to make it easier for you to undo and redo actions. You can now use Ctrl/Cmd+Z to undo an action and Shift+Ctrl/Cmd+Z to redo an action. This will help you save time and work more efficiently.
We've upgraded our history state management system to allow you to undo and redo actions even after saving your work. This means that you'll have access to all previous states, even if you've already saved your work. This is a great feature that will help you work with greater confidence.
We've expanded our user-profile feature to include page templates and global user template selection. This means that you can now save user templates globally and apply them to specific user roles, as well as select specific page templates for user roles. This is a powerful feature that will help you streamline the content creation process when you have users in different roles editing different sections of the website.
We've enabled cloning functionality for tabs and collapsible panels (toggles). This means that you'll be able to clone these elements without any issues. This is a small improvement that will save you time and effort.
We've enhanced our local video element with improved file validation and clearer upload error messages. This means that you'll have a better experience when uploading videos to your site. You'll be able to quickly identify and fix any issues that arise during the upload process.
That's it for this release of DXPR Builder! We hope you find these updates helpful and that they make your experience with our web content editing platform even better. As always, we welcome your feedback and suggestions for future updates. Thanks for using DXPR Builder!
Drupal updates create opportunities for everyone to participate in the open web.
Just because I share content online doesn't mean I want to share control over it. My website is a perfect example of what I mean. I take photos nearly everywhere I go: To date…
If you have a current Drupal site (built in Drupal 8 or later) you no longer need to entirely rebuild your site -- ever again. That doesn't mean it couldn't use a freshening up now and then.
We have several clients revamping their home pages, along with key landing pages. As part of this refresh, they are getting new designs in place, new messaging, new content. And they would like to launch the new design, and content, all at once.
Drupal's path system gives authors the ability to override the path of an item of content. Whilst the internal path of a page might be "/node/1" the external path can be anything you want, and can be set when editing the item of content.
The addition of the Path Auto module makes this change of path easy for your users by using patterns and automatically generating paths based on the data contained within the content item. You might want to use a path that contains the type of entity being presented, what category it was added to, and even the title of the item of content.
This system creates powerful search engine friendly URLs that can add keywords to the paths that Drupal uses to find content.
When building custom entities there are a few things you need to do in order to add Path Auto functionality. It must contain a 'canonical' link that points to the entity and be a fieldable entity with a field called 'path'. A canonical link always points to the basic path of the content entity, which would be "/node/1" for all content type entities.
Outside of the Path Auto module there are a number of internal classes called parameter converters that implement the core \Drupal\Core\ParamConverter\ParamConverterInterface interface and are used to convert an argument within a path into an entity object. This object is then passed upstream to the form or controller that will be using the entity.
Without the parameter converter in place you would have to accept a value to the form or controller that you would then have to convert into an entity of some kind. This can add a lot more code to the those classes that wouldn't be needed as they need to know how to load the entity and also what to do if the entity doesn't exist.
In this article I will create a content entity and then show how to generate custom paths to that entity in via a custom parameter converter class.