The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Fortune, Pieter, and myself have released an improvement to capabilities (tags) and how they can be used in the DAL.
What was it before?
The concept of tags was limited to only “Capabilities” assigned to an instance or an agent. These capabalities had to be tied to a billing rate. There was no easy way to change the tags, their name, color, or hierarchy, or create new ones. This had to be done by an engineer writing a database script.
What is it after?
A very basic management interface (for admins) to add and rename and move tags around, and also a place to create “Verticals” to be assigned to instances for analytics.
Why does it matter?
Operations can more easily update and create systems of categorizing and connecting Instances and Agents with a common naming system. Including creating a category of tags that are actually “Verticals” for improving the analytics on instances that are done for particular types of clients. These categories and tags can change over time as needs change, without requiring intervention from an engineer. The flexibility of a tag based associations will make it a very powerful tools as we continue to discover the best way to track and assign work on the DAL.
Near Future Roadmap
- Associating tags with a Client. (Especially for signaling credential needs)
- The ability for certain admins to delete tags that aren’t currently being used for billing.
- Support for more deeply nested tags.