thecommunitydigitallibrary / cdl-platform Goto Github PK

Haven't been able to reproduce yet, but clicking around in the search result visualization for a bit sometimes leads to an application error.

Will try to reproduce and add more. Happens on dev and in prod.

When a user opens the extension and either (1) views/searches for results, or (2) starts to edit a submission, all is lost of the extension is closed. Not only does this make for a poor user experience, but it also adds unnecessary API calls when a user clicks a search result (opens a new page, then the extension closes).

To fix this:

1. Add a submission cache in the browser where the draft of the submission is saved in browser
2. Add a result cache in the browser where the most recent search result page is saved in browser

In both cases, can save according to the URL of the webpage as the key of the cache.

The website supports submissions without a source URL (e.g., a note by itself, not about a website). But the batch-upload feature still checks to makes sure a URL is present, and will fail otherwise.

Instead, the batch upload should allow for an empty source URL field on submissions.

The website's submission page should probably use empty space more efficiently by

1. Minimize the buttons (edit, delete, share, etc.)
2. Make the submission note content larger (examples from Confluence, notion)
3. Provide a toggle to show the graph, replies, etc.

1. The logout and leave community are the same symbol but different actions. Can change the leave community icon to something else.
2. On a submission page, can change the reply and feedback feature icons to make them clearer.
3. Rename "Feedback" to "Report Issue".
4. Rename "Share URL" to "Copy URL"

Also, can add hover text for icons. For example,

• Reply --> "Create a submission in reply to this submission"
• Feedback --> "Send a message to the TextData development team about an issue with this submission".

Currently, the extension submission process differs from the website submission process - the extension does not support markdown editing / formatting on submission.

To fix: update the extension to be able to support markdown editing when creating a submission.