Supporting all these channels as output sources for an article makes our platform useable in many different contexts, which is great. For example, if you create an article with a red text that has to be rendered properly in our Article Editor, Help Center article templates (with CSS styling), the legacy Mobile layout of a our Help Center, the Knowledge Capture Application, the Mobile SDK that customers integrate with, the Web Widget and for customers that consume article content via the Article API. From our perspective, what we allow into an article via the Article Editor has to be compatible with a number of different publishing destinations. It's not quite as simple as what parts of TinyMCE we do and don't strip out. ![]() Will Markdown be available at some point? Or better yet, plugin support for additional editor features (code/syntax styling)?ĭo you have any suggestions/workarounds that lend themselves to a good workflow in Help Center regarding this type of formatting? Since we're hoping to leverage the Help Center's "Self Service" model more, we really need these features if we want to supply pro-quality support pages that are truly helpful, without it being so cumbersome for our agents to create them. Currently, I don't even seen where you can use preset header styling. ![]() Because our support frequently involves reading/writing code (both inline and block style), the Markdown capability in tickets has been great, and we wish this were an option in the Help Center. I want to stress that I'm not advocating for the previous article editor. Now, the only option is to open up the "Source Code" pop up and edit the HTML, a rather tedious process that seems to format things inconsistently in relation to the previous method. Previously, the WYSIWYG drop-down menu for "Preformatted" would allow us to set in grey-boxed code blocks. However, one feature has been removed and will undoubtedly cause some serious pain points for our agents in easily creating help articles: formatting options, specifically for source code. From what I can tell, the new WYSIWYG interface for drafting/editing articles has been cleaned up and hopefully is less buggy than the previous version (e.g., text randomly getting displayed with blue backgrounds). ![]() I'm currently testing out the new Help Center before we migrate over.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |