Curation wizard issues to write up

[andymeneely]

Ok so with version 2.3 of the website today I've got the curation tool posted in production. There are a bunch of things I want to write up in separate issues but I'll start the brainstorming here. The checklist is for when I create an issue for it.

• FOUC when opening a curation. #1165
• null as a string is appearing in various places #1166
• Fix and VCC commits should link to that commit on github. We can use the project commit url. #1182
• Repeaters should have delete buttons so you can remove an option #1181
• YML output should be styled to look like code. Bonus points if we can do syntax highlighting #1180
• Maybe instructions built into the page? An accordion entry with instructions on what to do that you can collapse. The project yml can have a bunch of useful links that people can use to investigate. #1179
• YML output page should have a link to GitHub pull request #1167
• We should be able to populate the curation tool with answers from a GH pull request (this is a bigger feature) #1178
• Should be able to delete a curation from the front page #1175
• Maybe have a way to go back to the front page without refreshing? #1168
• Would it make sense to have /curate be the "select a CVE" page, and then the rest of the tool be /curate/CVE-1234-5678? Maybe that's a big refactor but it might reduce the need for ajax calls #1177
• Refactoring: replace ajax calls with fetch #1176
• The "find a vulnerability to create" from select2 doesn't ignore leading and trailing whitespace so copy-paste fails sometimes #1169
• The "Yes/No" buttons could be prettier #1170
• We need to convert the json template to YML and put them in vulnerabilities #1183
• The order of questions gets messed up when we use the shared.json thing. So maybe we have shared.json work as a dictionary, and then kernel.json could have a "use this from shared" key #1171
• I had a lot of trouble getting Related to work as a repeater. Wouldn't it be easier to have the repeater info right in the json instead of using a parent tree? #1172
• Image link isn't fingerprinting to get from the cdn - use image-url() instead of url() in the scss file. The file art.scss is a good reference for what this looks like. #1173
• curationSummary at the bottom of the main page seems out of place #1174

Check the following:

• I have checked the VHP backlog for something similar: https://github.com/VulnerabilityHistoryProject/vulnerability-history/issues

[andymeneely]

@brianravi I've assigned the issues that are top priority to you - if it's not assigned to you it's not as high a priority (or I don't think we have time)