📈 Notes from WW standup 6 December
Summary
Meeting Purpose
Discuss ongoing website development for Wordworks, addressing design decisions, project management, and functionality concerns.
Key Takeaways
Meeting Purpose
Discuss ongoing website development for Wordworks, addressing design decisions, project management, and functionality concerns.
Key Takeaways
- Stock to Shop integration postponed to phase 2; current monthly cost clarified at R988
- Design refinements needed for header navigation, resource pages, and impact visualization
- Project management challenges identified; need for improved documentation and communication
- LMS development progressing; content upload process to be clarified
TopicsStock to Shop Integration
- Decision made to postpone implementation to phase 2 (3-6 months post-launch)
- Initial setup fee: R5,000Monthly cost: R988 (based on current PLU count, ~30-50)
- Cost increases to R1,300/month for 500-2000 PLUs
- Jane to confirm with Colleen regarding budget approval
Website Design Refinements
- Header navigation: Need to address loss of main menu items when in resources section
- Suggestions:Replace submenu with resource-specific optionsAdd breadcrumb navigationMake logo clickable for home navigation
- Resources page:
- Needs differentiation from homepage, quicker access to contentImpact visualization:
- Reconsider complex map implementation
- Focus on infographics or simpler provincial coloring
- Integrate with project data for pop-up information
Project Management Challenges
- Concerns about time-consuming meetings and information gathering
- Need for clearer task differentiation in Basecamp
- Suggestion: More visual demonstrations of progress during standupsIan to review and share documentation of decisions made
LMS Development
- Content upload process to be clarifiedJane seeking understanding of task breakdown (content vs. design vs. development)Ian to provide access to LearnDash setup for team exploration
Translation Management
- Weglot plugin suggested as a potential solution
- Features: Google Translate baseline, custom lexicon, collaborative editing
- Team to further discuss implementation details
Next Steps
- Jane to email Colleen (cc: Rowan, Tahiri, Gabriel) regarding Stock to Shop budget approval
- Ian to update project documentation and share with team
- Team to refine header navigation design and functionality
- Reconsider map implementation; explore alternative impact visualization optionsIan to provide
- LearnDash access for content team
- Continue LMS development and clarify content upload process
- Schedule follow-up on translation management solution