search

18F / dtmo-ei

Other
1 stars 2 forks source link

JTR Recommendation #90

Open colinmurphy01 opened 4 years ago

colinmurphy01 commented 4 years ago

As a deliverable from our work with the JTR, we intend to provide the following: • A prototype of a subsection of the JTR leveraging the following tools (Akoma Ntoso, XSLT, HTML + USWDS) • Documentation of • This prototype + its recommended components • A recommendation for an XML editor • User Test findings from Editing Scenarios using an XML editor • Outline of short-term needs for JTR migration + Longer Term Considerations

heymatthenry commented 4 years ago

I don't think Lime is going to be a fit for the DTMO/DHRA team. I spent most of the morning unsuccessfully trying to get it to run. It hasn't been updated in a year, and some of its dependencies (and dependencies of dependencies) are broken. I'm sure we could get it running by pinning the right versions of the various levels of npm modules, but 1) I wouldn't recommend a tool that requires so much yak shaving to our partner; and 2) it's not a great use of limited time at this stage.

colinmurphy01 commented 4 years ago

Working Doc for recommendation: https://docs.google.com/document/d/1NASueA1VC0zrrorYCH68sorCeKfZedv0-NSivUc4qms/edit?usp=sharing Visuals hosted here: https://docs.google.com/presentation/d/1rQzzeCmM_exNAztAqrS53xPbiOG9AW6Or07rQQV4xO0/edit?usp=sharing

Meeting today with JTR Team to align on deliverable and overview recommendation.