From 45462945e46613fdf0f3e64b663058476e7b0fe0 Mon Sep 17 00:00:00 2001 From: raulsagrado <119356996+raulsagrado@users.noreply.github.com> Date: Mon, 16 Mar 2026 14:49:05 -0400 Subject: [PATCH] Update um.html user documentation --- docs/um.html | 638 ++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 477 insertions(+), 161 deletions(-) diff --git a/docs/um.html b/docs/um.html index c4292fb..60e3067 100644 --- a/docs/um.html +++ b/docs/um.html @@ -1,208 +1,524 @@ - - -WIN Student Goal Tracker - User Manual + + + + + WIN Student Goal Tracker - User Manual - + .btn-primary{ + background:var(--primary); + color:#fff; + } + + .btn-primary:hover{ + background:var(--primary-dark); + } + + .btn-secondary{ + background:#fff; + color:var(--text); + } + + .btn-secondary:hover{ + background:#eef2ff; + } + + main{ + max-width:1100px; + margin:0 auto; + padding:1.25rem 1rem 3rem; + } + + .layout{ + display:grid; + grid-template-columns:1fr; + gap:1rem; + } + + @media (min-width: 980px){ + .layout{ + grid-template-columns:280px 1fr; + align-items:start; + } + + .toc{ + position:sticky; + top:1rem; + } + } + + .card{ + background:var(--card); + border:1px solid var(--border); + border-radius:16px; + box-shadow:var(--shadow); + padding:1.25rem; + } + + .toc h2, + .content h2{ + margin-top:0; + } + + .toc ul{ + list-style:none; + padding:0; + margin:0; + } + + .toc li + li{ + margin-top:.55rem; + } + + .toc a{ + color:var(--text); + text-decoration:none; + } + + .toc a:hover{ + color:var(--primary); + } + + .toc .small{ + color:var(--muted); + font-size:.95rem; + margin-top:1rem; + } + + .content section + section{ + margin-top:1rem; + } + + .section-title{ + font-size:1.35rem; + margin:0 0 .5rem; + } + + .muted{ + color:var(--muted); + } + + .grid{ + display:grid; + grid-template-columns:1fr; + gap:1rem; + } + + @media (min-width: 760px){ + .grid.two{ + grid-template-columns:1fr 1fr; + } + } + + .info-list, + .content ol, + .content ul{ + padding-left:1.2rem; + } + + .info-list li, + .content li{ + margin:.3rem 0; + } + + .callout{ + border-left:4px solid var(--primary); + background:#eff6ff; + padding:1rem; + border-radius:12px; + margin-top:1rem; + } + + .callout.success{ + border-left-color:var(--success); + background:#f0fdf4; + } + + code{ + background:#eef2ff; + padding:.15rem .4rem; + border-radius:6px; + font-family:ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace; + font-size:.95em; + } + + .steps{ + margin-top:.75rem; + } + + .kpis{ + display:grid; + grid-template-columns:repeat(2,1fr); + gap:.75rem; + margin-top:1rem; + } + + @media (min-width: 760px){ + .kpis{ + grid-template-columns:repeat(4,1fr); + } + } + + .kpi{ + background:#f9fafb; + border:1px solid var(--border); + border-radius:14px; + padding:1rem; + text-align:center; + } + + .kpi strong{ + display:block; + font-size:1.25rem; + margin-bottom:.25rem; + } + + .footer{ + text-align:center; + color:var(--muted); + padding:2rem 1rem 3rem; + font-size:.95rem; + } + + .back-link{ + margin-top:1.25rem; + display:inline-flex; + align-items:center; + gap:.5rem; + } + - +
+

WIN Student Goal Tracker

+

+ User manual for teachers and program staff using the WIN platform to manage + students, goals, benchmarks, and progress events. +

-
-

WIN Student Goal Tracker

-

User Manual

-
+
+ + Open Live Application + + + Back to Project Home + +
+
-
+
+
+ -

Overview

+
+
+

1. Overview

+

+ The WIN Student Goal Tracker is a web-based application designed to + help teachers and program staff organize student progress in a + structured way. Users can review assigned students, create or review + goals, define benchmarks, and document progress events over time. +

-

-The WIN Student Goal Tracker is a web-based system designed to help instructors, -program coordinators, and support staff track student goals, progress, and -critical incidents for adult learners with intellectual and developmental -disabilities. -

+
+
+ Students + Managed by teacher +
+
+ Goals + Tracked per student +
+
+ Benchmarks + Milestones per goal +
+
+ Events + Progress history +
+
-

-The system centralizes student goal management, progress tracking, and reporting -to support educational programs and improve visibility into student development. -

+
+ This manual focuses on the current application workflow shown in the + deployed prototype and implemented interface. +
+
+
+

2. Accessing the Application

+

+ To begin, open the login page at + https://win.opelly.me/login. +

-

Primary Users

+
+
    +
  1. Enter your assigned email address.
  2. +
  3. Enter your password.
  4. +
  5. Click Sign in.
  6. +
+
-
    -
  • Program instructors
  • -
  • Program coordinators
  • -
  • Support staff working with student development programs
  • -
+
+ After a successful login, the system will take you to the program + selection screen. +
+
+
+

3. Selecting a Program

+

+ After authentication, the system displays the list of programs + available to the logged-in user. +

-

System Workflow

+
    +
  1. Review the available program cards.
  2. +
  3. Select WIN Program – Teacher (Primary).
  4. +
  5. The application will open the main dashboard for that program.
  6. +
+
-
    -
  1. User logs into the system.
  2. -
  3. User selects or creates a student profile.
  4. -
  5. User creates one or more goals for the student.
  6. -
  7. User periodically updates progress for each goal.
  8. -
  9. User logs incidents if relevant to the student's progress.
  10. -
  11. Dashboard and reports display progress and completion status.
  12. -
+
+

4. Student Dashboard

+

+ The main dashboard displays the students assigned to the current + teacher or user. +

+
+
+

Information shown on each student card

+
    +
  • Student identifier
  • +
  • Expected graduation date
  • +
  • Number of goals
  • +
  • Number of progress events
  • +
  • Last activity date
  • +
+
+
+

Navigation

+
    +
  • The left sidebar lists students for quick access.
  • +
  • Clicking a student opens that student’s detail view.
  • +
  • The dashboard serves as the main starting point for daily use.
  • +
+
+
+
-

Core Features

+
+

5. Adding a Student

+

+ Teachers can add a new student record directly from the dashboard. +

-
    -
  • Student profile management
  • -
  • Goal creation and tracking
  • -
  • Progress update logging
  • -
  • Incident tracking and documentation
  • -
  • Instructor dashboard for monitoring progress
  • -
  • Structured reporting of goal completion
  • -
+
    +
  1. Click + Add a Student.
  2. +
  3. Enter the Student Identifier.
  4. +
  5. Enter the Expected Graduation Date.
  6. +
  7. Click Add Student to save the record.
  8. +
+

+ Once saved, the new student appears in the dashboard and sidebar. +

+
-

Typical Instructor Tasks

+
+

6. Viewing Student Goals

+

+ Selecting a student opens the goals view for that student. Goals are + the main tracking objects used to measure student development and + progress. +

-

Create a Student Profile

+

Goal details may include

+
    +
  • Goal category or label
  • +
  • Goal description
  • +
  • Associated benchmarks
  • +
  • Related progress events
  • +
-
    -
  1. Navigate to the student dashboard.
  2. -
  3. Select "Create Student".
  4. -
  5. Enter student information.
  6. -
  7. Save the student profile.
  8. -
+
+ Users can use this page to quickly review whether a student is making + progress and what supporting events have been documented. +
+
+
+

7. Managing Benchmarks

+

+ Benchmarks break a goal into smaller, measurable steps. This makes it + easier to see incremental progress over time. +

-

Create a Goal

+

To add a benchmark

+
    +
  1. Open the selected student’s goal.
  2. +
  3. Go to the Benchmarks section.
  4. +
  5. Enter the benchmark description.
  6. +
  7. Click Save.
  8. +
-
    -
  1. Select a student from the dashboard.
  2. -
  3. Click "Add Goal".
  4. -
  5. Enter goal title and description.
  6. -
  7. Define the target timeline.
  8. -
  9. Save the goal.
  10. -
+

Example benchmark

+

Complete Computing for Good

+
+
+

8. Recording Progress Events

+

+ Progress events document meaningful activities, milestones, or notes + related to a student’s goal. +

-

Update Goal Progress

+

Each progress event should capture

+
    +
  • A brief description of the activity
  • +
  • The user who recorded the event
  • +
  • The date of the event
  • +
-
    -
  1. Open the student profile.
  2. -
  3. Select the goal being tracked.
  4. -
  5. Add a progress update or note.
  6. -
  7. Update completion status if applicable.
  8. -
  9. Save the progress update.
  10. -
+

Example

+

Took C4G – loved it!

+
+ Progress events create a historical record that can support follow-up, + reporting, and program evaluation. +
+
-

Log an Incident

+
+

9. Typical Workflow

+
    +
  1. Log into the application.
  2. +
  3. Select the appropriate program.
  4. +
  5. Review the list of assigned students.
  6. +
  7. Add a student if needed.
  8. +
  9. Open a student record.
  10. +
  11. Review or create goals.
  12. +
  13. Add benchmarks to define milestones.
  14. +
  15. Record progress events as the student advances.
  16. +
+
-
    -
  1. Navigate to the student profile.
  2. -
  3. Select "Log Incident".
  4. -
  5. Enter incident details and description.
  6. -
  7. Save the incident record.
  8. -
+
+

10. Usage Notes

+
    +
  • Keep student identifiers consistent to avoid duplicate entries.
  • +
  • Update progress events regularly so the record stays current.
  • +
  • Use benchmarks to make large goals easier to track.
  • +
  • Review student cards often to spot inactivity or missing updates.
  • +
  • Log out when finished using the system on a shared device.
  • +
+ Back to Project Home +
+
+
+
-

Prototype Version

- -

-The current version of the system exists as a user interface prototype created -in Figma. The prototype is used to evaluate usability and gather feedback from -stakeholders before full system implementation. -

- - -

Stakeholder Evaluation

- -

-Stakeholders are invited to test the prototype and complete a short usability -survey evaluating how easy it is to perform common tasks within the system. -

- - - -

-Feedback collected from this evaluation will guide improvements to the final -system design. -

- - -Back to Project Home - - - -
- +