Will the keyboard language change depending on the language of the interface?
May be OS dependent, not sure
Can blocks be merged? What would be advantage?
Can move blocks around, can cut and paste from one block into another, perhaps no advantage to merging
How about the option for a global delete? And deleting multiple blocks?
The delete button on corner of the block is easy to accidentally hit
Probably better to hide delete in another menu, provide ability to select all or multi-select and then delete
Encourage alt-content adding right at the point of adding blocks/entering content
Don’t want to surprise users at the end with the need to go back and add a bunch of content
Perhaps once they select something outside of the current block?
The critical moment for adding alt content is when author publishes the story, but we don’t want to wait until then to flag it
We can gate it at the point of publishing, but provide encouragement/highlight it at the point of authoring
Also, don’t necessarily want to edit your story in a linear way - add some content here, move on, go back and add other content etc. - so we want to allow the author to move around in this way, not restrict it
Change “Done” to something more relevant - something that indicates what will come next - Continue? Other?
“Next” could be changed to Preview
Make the flow non-linear in general - allow author to bounce around between
Metadata (title, author, keywords etc)
Then Publish page (tells you/summarizes what you need to do/complete before publishing)
Transcribing recorder -
How to choose language?
Just transcribe automatically and then allow edit or delete
Takes you to a whole new interface?
Less modal and sequenced
Transcript created as soon as stop button is selected?
Need a “done” button or record/pause/end options
Audio story blocks - should show description and transcript fields right away
Is there a way we can clarify the story structure non-visually? Using headings? Or label each block?
We can label what each block is (this will likely be the case in the markup anyway, i.e. “text block”, “image block” etc)
Should we provide ability to add more descriptive headers - to each block? Or to group a whole section together? And to make (non-visual) navigation easier?
Is our goal to provide support for navigation during authoring, or during viewing (or both)
Minimum viable should prioritize the ability to go back and edit or remove a story
What if there are typos, or someone wants to remove a story for various reasons?
The learning reflections site will be used in co-design sessions and will be more guided and therefore manageable
Also without account management there is no way to see all of my stories at once, because I can’t retrieve them
Could it be based on state ownership of the device?
What about situations where one device is being shared/passed around?
What are the “lowest-cost” options to allowing post-authoring editing?
Could possibly also use a token