Implement a "Tooltip" for adding Links to an Answer on the FAQ Admin Screen.

[entrotech]

Overview

The FAQ Admin screen seems to be working well. However, some feel that the user needs additional instructions for how to enter a hyperlink to the answer text, so the designers have created prototypes for modifications that might be more helpful to the user in Issue #1479.

Action Items

• Review Issue Design: Create a tooltip for editing or adding links on the Admin FAQ Pages #1479. This is asking for a change to the link editing modal that currently uses the default modal provided by Quill (the NPM package for HTML editing).
• Review the Quill documentation and see if it is feasible to replace the default link editing dialog with something different.
• Also see if it is possible to edit a link's "target" attribute so we can achieve the desired behavior for internal ve external links as described below in the Resources section of this description.
• Present findings to the team for further actions and possible implementation.

Resources/Instructions

The links in an answer can be either internal to the TDM website and relative (like /termsandconditions, /privacypolicy, /checklist), or external to the TDM site, like https://cityclerk.lacity.org/lacityclerkconnect/index.cfm?fa=ccfi.viewrecord&cfnumber=15-0719-S19

Ideally, when an internal link is clicked, it would use the same browser instance and tab, and just navigate to the different page within the site. In HTML, this would be the default behavior if you set the target attribute of an tag to "_self".
When an external link is clicked, we would like the browser to open a new tab for the linked site - equivalent to behavior of an tag with the target attribute set to "_blank".

It is not clear if the Quill HTML editor used by the browser allows the user to effectively set the target attribute.

[Biuwa]

@mark-mxwl

Please provide an update:

1. Progress(What is the current status of your project? What have you completed, and what is left to do):
2. Blockers(Difficulties or errors encountered):
3. Availability(How much time will you have this week to work on this issue):
4. ETA(When do you expect this issue to be completed):
5. Pictures (if necessary)(Add any pictures that will help illustrate what you are working on)

[mark-mxwl]

Hi @Biuwa, thanks for checking in. Unfortunately, I have not been able to get started on this issue. My availability is very limited at the moment, so I think it would be best to let someone else take over. I'll un-assign myself, and will return this to backlog.