Wordworks

✊ Notes from Design walk-through - 28 November 2024

Once the prototype is finalised, we need to critically review the prototype so we can finalise and properly brief dev on final decisions
We will flag any gaps with the team
 
Home page
NEED TO NOTE THAT WE COMMITTED TO THIS:
Featured story, - needs to pull in by selection or allow for a specific post to be built
Needs excerpt to pull through to the home page vs pulling in, same for the title
Fall back is automated
 so if there's nothing specific, the latest post (or whatever we decide is best) should auto pull through

All decisions we make a suggest need to consider low band-worth users

Fathom notes:

The following summary and action items were generated by AI
Summary
Meeting Purpose
Walkthrough and review of Wordworks website design prototype with Matogen, Wordworks, and Unfold teams.

Key Takeaways
Design prototype is nearly complete, with final refinements and style guide to be finished by end of day
Resource pages will use accordion structure, with potential for additional overview/landing pages
User permissions and viewing/downloading options for resources still being finalized
Search functionality and user journeys to be further refined based on team feedback

Topics
Resource Page Structure
Accordion structure for program resources retained
Considering additional landing/overview pages to provide high-level program info
Will link to existing program info pages rather than creating new ones
Resource files will have individual pages in backend, but may not be publicly visible

Resource Viewing/Downloading
Discussing options for previewing vs downloading resources
Considering embedded preview of first 10 pages as compromise
Need to balance accessibility with protecting proprietary content
May use different permissions for viewing vs downloading

Search Functionality
Search box on program pages uses predefined list rather than open search
Team still determining ideal search capabilities and granularity
Will track and refine search requirements as development progresses

Navigation and Menu Design
Top menu may need adjustment to reduce space when scrolling
Considering options like condensing, dropdown, or fading away
Team will prototype different options to find best balance

Content Management
News/blog section simplified due to current capacity constraints
Using flexible "Stories" category to accommodate various content types
Can add more specific categories later as needed

Forms and Sign-up Process
Multiple forms created for individual/school sign-up, training requests, etc.
Some discussion around mass communication options (e.g. WhatsApp)
Sign-up confirmation screen to auto-dismiss after 5 seconds

Design Components and Style Guide
Style guide with buttons, headings, etc. to be completed today
Will provide logos, graphics, and other visual elements
Team can request any missing components during development

Next Steps
  • Unfold to finalize prototype and style guide by end of day
  • Unfold to prepare visual assets folder for developers
  • Matogen to review completed prototype and provide any final feedback
  • Teams to continue refining user journeys and search functionality
  • Development to begin based on finalized prototype

Action Items
  • Create program info pages w/ visual components for each program resource type - Jacqui Botha
  • Research & propose solution for embedding PDFs w/ controlled viewing (e.g. first 10 pages only) - Xoliswa Shandu
  • Review prototype file; identify & document missing user journeys/flows; share findings with Jackie & Jane - Ian Parsons, Xoliswa, Robyn
  • Complete style guide & component pack incl. headings, buttons, states, cards; prepare logos & graphic elements; add to dropbox folder - roule le roux