You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using this jQuery extension to render the tooltip: https://iamceege.github.io/tooltipster/ so, maybe a theme of it can be created or just adding an extra CSS file it's enough.
The first step for this issue is to create a design document explaining what content should be included in the tooltip, considering the possibilities of having different tooltips type (as GitHub does for PR, issues, user cards, etc) and showing mock examples of they would look like.
This document will help us to know if we need to change something in the API backend or the data that we are getting right now is enough.
We probably can have two instances of this design/implementation:
make it work with what we have already to look nice, but not perfect
grow from there expanding the design and modifying the backend
There are not a lot more we can do regarding the structure of the content since we receive a HTML blob. In case we want to get the title, sections, paragraph, etc we will need to parse it on the client or modify the Read the Docs API endpoint.
There are some ideas already implemented in MediaWiki and GitHub from where we can base ours:
We are using this jQuery extension to render the tooltip: https://iamceege.github.io/tooltipster/ so, maybe a theme of it can be created or just adding an extra CSS file it's enough.
The first step for this issue is to create a design document explaining what content should be included in the tooltip, considering the possibilities of having different tooltips type (as GitHub does for PR, issues, user cards, etc) and showing mock examples of they would look like.
This document will help us to know if we need to change something in the API backend or the data that we are getting right now is enough.
We probably can have two instances of this design/implementation:
A help guide about how to write this document, could be this one: https://www.freecodecamp.org/news/how-to-write-a-good-software-design-document-66fcf019569c/
The text was updated successfully, but these errors were encountered: