-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Figma wireframes for the template builder #30
Comments
Notes regarding building templates from the Edinburgh meetings: We will utilize section and question banks to allow users to submit groups of questions all at once and edit and define preferences.
|
@mariapraetzellis @briri @jupiter007 @fraserclark @andrewebdev here are some thoughts about how to break down the larger Template Builder process into more digestible chunks for wireframing and reviewing. I'm basing this on the bullet points in the description of the card, with an eye on related functionality and the relative scope of each bullet point, as well as how much discussion I think each bit of functionality will generate:
|
Thanks @cazinc I think that sounds like a good way to break things apart. Are you thinking they should be tackled in the order in which you've listed them here? |
Zach says we should do these in the order he mentions above. We can do user testing between sprints 2 & 3. Brian & Juliet will work on the build-out of 1&2 after user testing & while Zach works on 3&4. @cazinc can you make tickets for these sprints?
|
Hi @mariapraetzellis given that this breakup into separate cards could end up making this bit of wireframing run over 4 x 2 week sprints, Fraser plan to tackle these together, cutting the total time in half. Does that sound OK? Assuming it does, we are actually thinking that (for our purposes mostly!) it would make more sense to tackle them in reverse order: 4 → 3 → 2 → 1. We also think it might be easier for the testers if they test once all 4 sprints are done instead of in the middle, as that should result in more of a "finished project" and a bit more context within which to test things. Again - sound OK? I think in terms of timings, with us both working together, the schedule would be the same (i.e. after 2 sprints). |
We have an initial draft of the Template builder finished. There is a few discussions points which we can talk through on Thursday. Video Walkthrough https://www.loom.com/share/6a7b1bcdda9644f197bcd042f8eddc62?sid=bd70411b-076c-47ab-926d-b21a7c8987b8 Figma Prototype Mode Discussion
Let me know us your thoughts/first impressions and look forward to chatting it through on Thursday. @jupiter007 @mariapraetzellis @briri @cazinc @PaulaReeves @andrewebdev |
@fraserclark Thanks so much for the video! It made reviewing the wireframes much easier & great to see all the work you got through on this. Here's our notes on the wireframe for the template builder:
Additional comments
|
Thanks @mariapraetzellis - just to clarify some of the confusion, "New or Existing template" Sorry if this wasn't clear, I offered 2 alternatives in the Figma The first being this model of selection The second I offered at the end of the video As we built these, we weren't sure if the choice should be like the first one where its very clear "create from an existing template(eg duplicate in some way)" or start completely from scratch As we talked more, it felt like you almost never want people to build from scratch, unless they really know what they are doing. So the second option was trying to highlight the "hierarchy" and clear up perhaps some confusion on duplicating a template- the choice is either create using a previously created template OR build from a template made by DMP Tool, and finally "build from scratch" |
Notes on our discussion from the team meeting: We've decided to record version history when a user publishes a template, rather than every time it is saved. Comments are optional. @fraserclark will modify the wireframes. Move questions over when selecting existing sections. Anatomy of a question:
|
Hey all, Thanks for writing up those notes @mariapraetzellis Figma link is same as before and it's interactive - I will clean things up a little, but wanted to get something started, while it was fresh in my mind Start screen Updated add new section Publish button We have a summary of what happens/consequences of publishing (I just put in some dummy content for now), we have an optional change log section History simplified Anatomy of a question Sharing/collaborator I have updated this too, but still very early. |
Hi @fraserclark thanks for the updates. Here's my comments:
|
Fraser has address 5/6 changes from above. He will address #6,Sharing: this looks good so far. I'll have some text tweaks when it's ready., by Thursday. |
We have addressed the last of the changes from above. We are listing all "collaborators" over 2 lists. The first being the people in your organisation, so its very transparent who has access to edit. And then underneath having additional external collaborators along with the invite a new person I know there is some chat on the template picker card issue #31 about "maintainer" being visible, which I would expect to have some kind of control in this section too, but will update once that has been resolved Let us know your thoughts, @jupiter007 @mariapraetzellis @briri @cazinc @PaulaReeves @andrewebdev |
Rather than including a list of all administrators (which could be very long), we will include this message: "All administrators at ORGANIZATION NAME have access to edit this template." I think the second question regarding "maintainer" is no longer relevant since we've decided to utilize "Last edited by" instead. The "Last edited by" should be visible on this page. |
@cazinc Have we resolved this issue? Are the notes from the comment above addressed in the wireframes? |
Yes @mariapraetzellis should be - screenshot attached just to double check. If you're happy with that it should be all good. |
I've written a few of my own comments here. They're all very minor, like wording changes or clarification points, no significant changes. |
As discussed I've setup a dedicated card for feedback now: #625 |
The Template Builder is the section of the application that allows administrators to create new templates and customize existing templates. Functionality needed for this area:
High-level functions
Template level functions
Section level functions
Questions
Additional requirements are described in the work plan and Edinburgh meeting notes
The text was updated successfully, but these errors were encountered: