Add a structured editor for links #21

New Issue

bvisness · 2022-05-21T23:22:45Z

bvisness commented

2022-05-21 23:22:45 +00:00

Currently to edit profile or project links, you have to use an ad-hoc text format like so:

However, the links are actually stored in a proper database table behind the scenes, and we only use this format because at some point we were too lazy to write a proper structured editor for this. But parsing this is annoying and it's a weird format for users to learn. We should make a proper editor!

Stuff it should do:

Allow for nice editing of link and title without requiring plain text input
Allow for adding / deleting links
In real time, automatically recognize the same common link formats that the backend recognizes, and disable the title field in this case. For example, sharing a link to your GitHub profile should disable the title field and change the text to "GitHub". (This would be a good case for WASM, to ensure that the frontend and backend always agree.)

This editor UI should be isolated in a template so that we can easily include it in both the user and project settings.

Currently to edit profile or project links, you have to use an ad-hoc text format like so: ![image](/attachments/80187c5d-953a-4021-8434-a7c9bffbd8eb) However, the links are actually stored in a proper database table behind the scenes, and we only use this format because at some point we were too lazy to write a proper structured editor for this. But parsing this is annoying and it's a weird format for users to learn. We should make a proper editor! Stuff it should do: - Allow for nice editing of link and title without requiring plain text input - Allow for adding / deleting links - In real time, automatically recognize the same common link formats that the backend recognizes, and disable the title field in this case. For example, sharing a link to your GitHub profile should disable the title field and change the text to "GitHub". (This would be a good case for WASM, to ensure that the frontend and backend always agree.) This editor UI should be isolated in a template so that we can easily include it in both the user and project settings.

image.png

86 KiB

This repo is archived. You cannot comment on issues.