π± Learner deep dive
Sample learner dashboard, journey, guardrails and group request flow.
Open learner pageDEMO MODE β sample data only
This expanded tour shows how a learner, teacher, group, team and community partner might use VerdiaWorld. It is static and safe: no account is created, no backend data is written and no real learner information is collected.
Full program walkthrough
The aim is to help a school, group, family or community partner understand the program before asking for access.
Profile, level, seeds and simple first actions.
2How learners move from solo to teacher-guided groups.
3Pending actions, approvals and safe supervision.
4Teacher-guided discussion rather than unmanaged chat.
5Invite another group into a moderated discussion path.
6Same challenge for the whole group.
7Short checks that reinforce shared learning.
8Ideas are checked before group visibility.
9Track idea, plan and completed real-world outcome separately.
10Accessible summaries for teachers and community partners.
11Questions to answer before starting a pilot.
12Turn interest into a safe first enquiry.
VW-DEMO-5 deep dive links
The walkthrough is now supported by three deeper sample pages for clients who want to inspect the learner, teacher and outcome sides separately.
Sample learner dashboard, journey, guardrails and group request flow.
Open learner pageSample pending actions, approvals, review queues and session tools.
Open teacher pageSample matrix separating idea, plan and completed real-world outcome.
Open outcomes pageRole views
Suggests ideas, answers scenarios and sees personal progress.
Reviews actions, approves membership and guides discussions.
Works around a shared place, topic or class challenge.
Connects multiple groups around a wider purpose.
May join a moderated discussion or support real-world outcomes.
1. Start as a learner
The learner does not need to understand the whole system at once. They see who they are, whether they are solo or in a group, what their progress means and what they can do next.
2. Join or request a group
Learners can find a suitable group, but access should wait for the responsible teacher or adult to approve.
3. Teacher approval / pending actions
This is the control centre: membership approvals, contribution review, scenario activity, partner requests and outcome checks.
Buttons with waiting actions should be visibly highlighted for the teacher.
4. Group discussion flow
βWhich part of the creek path feels hottest, and what could our group suggest that helps people, water and wildlife?β
5. Partner group invitation
The aim is to get groups talking across places and perspectives while keeping the conversation appropriate and supervised.
6. Scenario session
βYour local creek path gets very hot in summer. What could your group suggest that would help people, water and wildlife?β
The group works from the same learning challenge.
Responses can be checked before broader use.
The session becomes part of the group story.
7. Quiz session
A teacher can use short quiz sessions to test understanding and create a simple record of group learning.
8. Contribution review
Review protects the learning space and helps the teacher guide the group towards constructive action.
9. Idea β planned action β completed outcome
This distinction matters. A good idea is valuable, but it is not the same as a completed real-world outcome.
Suggest native shade planting.
Counted as ideaTeacher and group check safety and feasibility.
Counted as planned actionPlanting day completed and recorded with notes.
Counted as completed outcome10. Printable reports
Reports should help a school, family or community partner understand what was discussed, what was planned and what was completed.
11. Pilot readiness checklist
Who reviews membership, ideas and discussion?
Which class, club, family group or community group starts first?
Which age level should scenarios and language fit?
What single topic will the group explore first?
What must not be entered into the platform?
What counts as completed action rather than only an idea?
12. Request pilot
Use the pilot page to prepare an email enquiry. The form is static and does not write data to the backend.