Anna Kelian

Just a question: Why was the decision made to use HSL for color settings instead of RGBA or hex? Was there a specific advantage to choosing HSL over these other formats?

The summary box is a fantastic addition, but there are a few enhancements that could make it even more powerful and user-friendly:

1. Overview for Sections Within an Article. Currently, the summary box provides a single overview at the top of the article. It would be incredibly useful to add the ability to create overviews for individual sections (under headings) within the same article. This would provide more context and improve navigation for users. Is this something that could be implemented?
    
2. Links and Images in the Summary Box. The summary box currently doesn’t support links or images, as well as lists which limits its versatility. For example, we often use the summary to give an overview of the product an internal document pertains to. However, we’d like to include links to more in-depth walkthroughs, especially when the article primarily focuses on internal troubleshooting processes. Typically, we end the summary with something like: “Learn more about this: …”—but we can’t include the actual link. Adding this feature would be immensely helpful. Also, adding lists would be helpful for listing what an article covers.
    
3. Callouts. It would be great to have predefined callouts (e.g., info, alert, tip, or warning) that can be easily added from the same menu as the summary box.
    
4. Buggy Behavior When Pasting Text. The summary section sometimes behaves unpredictably when pasting text. This often freezes the entire page, forcing us to reload and lose changes. Addressing this bug would improve usability and prevent frustration.

1. Something is overriding Table CSS
   Maybe it's the

   tags around tables, I'n not sure but something is overriding table CSS and formatting. This behavior is causing unexpected styling issues. So some tables inherit the table css from our template while others don't even if we remove all custom styles from the table in the editor. Example, by default all rows in our tables have a top border styling if the border is not customized in the editor. This works for some tables and not other in the EAP which makes us believe some other html or css is overriding it for some tables.

2. Padding Issues
   Tables frequently lack padding, especially in the Knowledge app within Zendesk Support. This results in a cramped appearance and impacts readability. It is tedious to go into each table to add the paddings in manually. Note that updating the style sheet doesn't impact tables in the Knowledge app in Support. So this has to be added from your end.
3. Default Table Width
   Seems like tables aren’t set to 100% width by default, which means we need to manual go in and change this.
4. Custom CSS for Table Cell Properties
   Custom code for table cell properties, such as borders, seems to be missing. Is there a way to reintroduce support for custom CSS to handle these formatting needs? For example, we used to add a left margin for some tables and now that is not possible.

In the Knowledge app within Zendesk Support, images wrapped around text don’t display correctly. Instead of being wrapped, they should appear at 100% width by default. This would ensure consistent and correct formatting without requiring manual adjustments.

When images are wrapped around text, they have a lower z-index than the text, making them unclickable. This interferes with our custom code that enlarges images on click. While we’ve applied a workaround using custom code, it would be much better if this issue could be resolved natively to avoid the need for customization.

It’s often difficult to determine which heading style is applied or whether a heading is bolded, as these settings are now hidden. This requires us to click into the formatting bar each time to check the applied heading style or bold formatting, which slows down the workflow.