Advisory Group Meeting Recording, Chat History, and Transcript

• Chat history (download)
• Transcript (download)

New Sites Since Last Monthly Meeting

• Interdisciplinary Theatre Studies (UW-Madison)

Changes and Improvements

• How to get my hands on the new TinyMCE editor?

  • Group level Document editor options:
    • Allow for switch between classic and Froala
    • Use Froala only
    • Allow for switch between classic and TinyMCE
    • Use TinyMCE only

    This group-level option is found by going to SitePref > Group Spaces > Edit and scrolling down to the "Document editor" dropdown.

  • My profile Editor mode options:
    • New editor as the default

    Whatever option you select under your profile will work in combination with the group-level setting in that space. So, if the group space is set to use Froala, your "new editor" default will open Froala; if the group is using TinyMCE, this will be the new editor that opens by default. If the group has opted to only use Froala or TinyMCE, you will not have the option to switch in that space, even if your profile is set to use the Classic editor as the default.

    Question: Could there be an option to switch between Froala and TinyMCE?
    Answer: We can make this happen if there are certain use cases for it.

    Question: Is there a way for an admin to test out TinyMCE without enabling it for my entire group?
    Answer: Unfortunately, the TinyMCE editor has to be enabled for the entire group space, so your authors would always be able to switch as well. We can look into an option to have all users in your space default to Classic to encourage them to use that instead of TinyMCE.

• Preview of what's new and improved in the TinyMCE editor

  • Custom Linkdoc - read access checking, title auto file
  • Custom Includedoc - read access checking, element specific support
    • Note that we do not display the title of the document in the editor; instead, it will be displayed as "include doc [id#]". This is because certain characters in doc titles can break the IncludeDoc parser.
  • Custom Inline Restriction
    • This can be done as a DIV or a SPAN depending on the context.
  • Custom Restore - field specific choices
    • This allows you to pick and choose specific fields from a particular revision that you would like to restore to, and you can access this directly from the toolbar/menu bar.
  • Custom Attachments
    • There is now an option in the toolbar/menu bar that allows you to access attachments stored in the doc or shared attachment folder so that you can more easily insert them into a document. This also allows you to create a new doc attachment folder if none exists and quickly upload new attachments.

    Question: Can you add an alt tag by clicking the image?
    Answer: Yes, clicking the image allows you to add an alt tag. You can also add a missing alt tag via the accessibility checker. Right now, the system defaults to inserting the file name as the alt text, but this is not ideal and should be updated.

  • Custom Shorthands - #linkdoc (id or title search), ^includedoc, [attachments, @user lookup

    • This is a brand new feature in TinyMCE. The characters listed above will trigger an auto-insertion feature.

      The user lookup feature allows you to search for specific users based on name, and clicking them will insert a mailto link. You can also search "@publish" which will bring up a list of everyone with publish rights.

      The options for LinkDoc and IncludeDoc allows you to quickly add these to your document without needing to go through the toolbar.

      The option for attachments will similarly allow you to search for attachments in the doc or shared attachment folder by the file name to drop them in place.

    • Accessibility checker  - auto trigger at activation
    • Menu and toolbar access
    • Floating toolbar
    • Editor height - min 300, max 800, bottom margin 40

    Question: Is there documentation available for using TinyMCE? That will help us with with the roll-out.
    Answer: We will be working on getting this published now that the plug-ins are working.

    Question: Will there be any disruptions when we make the setting switch if some of our authors have documents in progress that they are working on in the Froala editor?
    Answer: We do not expect any technical issues with the actual switching on the document edit screen. However, it is good to be aware that there may be cases where TinyMCE processes content differently from Froala (and the Classic editor). If you don't save, you can just back out, but if you do, you can always revert to a previous revision if needed. We've also found that the TinyMCE CSS is less invasive than Froala's, so we hope that there are fewer issues with that.

    Question: Can an email be sent out when the access changes for TinyMCE are put in that allows the admin to play around with this? I love it so far.
    Answer: Yes, we will be working on a full beta testing plan, and we will send out communication with all of the information on testing.

  • Bug fixes

    • Last reviewer name no longer (incorrectly) displayed
      • We have removed the reviewer name from the doc info table completely. Instead, you can find this information in the Comments and Events log.

  On-going and Proposed Changes

  • New WYSIWYG Editor

    • Transition from self-hosted to cloud-hosted
    • Determine what CSS resources are needed
    • Engage users and partners for testing
    • Engage early adopters
    • Phased-rollout

  • Streamlining Content Creation

    • Simply quick document creation
    • Make the document life cycle easier to grasp

  • Semantic Search

  Spotlight Time

  • Share your ideas
  • Demonstrate your tips and tricks
  • Articulate your feature requests

  Other

  • 2021 KB Advisory Group Meeting Dates

    • October 29
    • November 19
    • December 17

  • 2021 KB Cafe Dates

    • Monday, October 11
    • Tuesday, November 9
    • Wednesday, December 8