APEX Portfolio v2 — Purpose & Design Intent

Why This System Was Built

Before v2, student-associates tracked their APEX portfolio progress in v1 — a localStorage-only system. That meant their data existed only on one browser on one device. They couldn't access their work from home, instructors had no visibility into progress, and there was no persistent record of growth over the year. The portfolio lived nowhere meaningful.

V2 was built to fix that at the root: make the portfolio real. Real data that persists across devices. Real visibility for instructors. A real connection to Google Drive so evidence files actually live somewhere. The goal isn't a fancier UI — it's a system where the portfolio is a genuine artifact of a student-associate's year.

What the Portfolio Is For

APEX student-associates are working toward growth across five standards that span servant leadership, academic identity, career exploration, technical skills, and professional habits. The portfolio system is the place where that growth is tracked, evidenced, and reflected upon — not just graded.

The design intent is that using the portfolio should feel like professional practice, not homework. Check-ins are modeled on daily standups. Kanban boards reflect how real project work moves through stages. Drive folders are where evidence lives, not a Google Form submission. The system should reinforce APEX culture, not feel like a separate school requirement layered on top of it.

How Each Standard Maps to Its Interface

• Standards 1, 2, 5 (Servant Leadership, Beyond GPA, Professional Skills): Kanban boards — because progress through strands is nonlinear and task-like. Student-associates move artifact cards through columns as they complete work.
• Standard 3 (Career Exploration): Sidebar/process flow, not kanban — because career exploration is a journey through phases, not a task list. The interface reflects that it's iterative and reflective rather than completion-oriented.
• Standard 4 (Technical Skills): Pathway-specific — each APEX course has different technical content, so this standard cannot be generic. It's deliberately deferred until each course's specific skills are defined in collaboration with instructors.
• Check-ins (Checkin.html): Daily standup log. Builds the habit of professional reflection and gives instructors a window into how student-associates are actually experiencing their days.

The Instructor's Role in the System

Instructors are not just observers — they're participants. The instructor dashboard was built so that Russ (and eventually other APEX instructors) can see the whole cohort at a glance: who's moving through standards, who hasn't checked in recently, where the class is collectively strong or behind.

Instructor role is set manually in the Sheet — it's intentional that instructors aren't self-designating. The auto-roster feature (students are linked to their instructor automatically on signup) means instructors don't manage rosters by hand; the system handles it when students first authenticate.

Dual Enrollment

Some student-associates are enrolled in two APEX courses simultaneously (e.g., DWT + DCS). This is a real and growing pattern. The portfolio system handles it by making kanban progress course-scoped — a student's Standard 1 work in DWT is tracked separately from their Standard 1 work in DCS. When a dual-enrolled student opens a standards page, they see a course selector and can switch between their two contexts. This was a deliberate architectural decision, not an afterthought.

Google Drive: The Missing Piece from V1

The Drive integration is philosophically significant. APEX has always asked students to collect evidence — photos, documents, reflections, project files. In v1 there was nowhere for that evidence to actually live connected to the portfolio. In v2, when a student-associate logs in for the first time, the system automatically creates an APEX Professional Portfolio folder in their Google Drive with subfolders for each standard. The intent is that this folder becomes the student's actual portfolio artifact — something they own, can share with colleges or employers, and carry past their time in APEX.

Who Built It and Why It Matters

This system was designed and built by Russ Goerend, an APEX instructor at Waukee, for his own students and the broader APEX instructor community. It's not a vendor product — it's a working educator building the tool he wishes existed. That context matters when making design decisions: the system should reflect how APEX actually works, not how a generic portfolio platform assumes school works. When in doubt, defer to Russ's judgment about program culture over conventional edtech patterns.