Fraser Wilson

Problem

Students often manage deadlines across multiple subjects with fragmented tools, making it hard to track task state, due dates, and upcoming workload in one focused academic flow.

Solution

I built Chelix as a board-based planning system where each board maps to a subject and each task includes status, dates, notes, ordering, and lifecycle controls (restore/delete) designed for real study planning.

Key Features

• Authenticated multi-user experience with email/password login and Microsoft Entra SSO.
• Subject-based boards with create, rename, delete, and strict per-user ownership.
• Task CRUD with To do/Doing/Done statuses, notes, due dates, and ordering.
• Timeline view across boards for upcoming deadlines and planning visibility.
• Soft-delete, restore, permanent delete, and automatic retention-window cleanup.
• Weekly/biweekly schedule planner with copy-to-multiple-days workflow persisted per user.

Impact

Chelix demonstrates full product ownership from architecture to UX polish. It validates secure user-level data isolation, reliable task lifecycle design, and productivity-focused interactions that reduce planning friction for deadline-driven users.

Resume-Ready Highlights

• Designed and delivered Chelix end-to-end as a solo full-stack product using React 19 and ASP.NET Core 8.
• Implemented JWT + Microsoft Entra OAuth authentication with strict per-user data ownership boundaries.
• Built board-based subject management and task lifecycle tooling (soft-delete, restore, retention cleanup).
• Developed a cross-board timeline and schedule planner to improve deadline visibility and weekly planning.
• Containerized local infrastructure with Docker Compose (PostgreSQL + pgAdmin) and production-ready env configuration.
• Documented APIs with Swagger/OpenAPI to accelerate testing, integration, and maintainability.

Lessons Learned

Secure data ownership rules must be designed early at model and API layers. Small UX details such as restore flows, timeline visibility, and schedule copy-actions materially improve daily usefulness. Designing retention/cleanup from the start keeps task-heavy systems maintainable over time.

Problem

Traditional CMS authoring can be slow when source content already exists in documents and needs consistent structure, clean rendering, and secure publishing controls.

Solution

Fractured_Blogs ingests DOCX and PDF files, extracts content while preserving hierarchy, and renders the output in a responsive site design backed by authenticated author-only publishing flows.

Key Features

• Document-first authoring via DOCX/PDF upload instead of manual CMS editing.
• Structured extraction and rendering that preserves heading/content organization.
• Secure upload and publish pipeline for controlled content releases.
• Microsoft Entra sign-in with author-only access to publish workflows.
• Responsive UX with light/dark themes for polished reader experience.
• Production infrastructure deployed on Railway with domain forwarding and DNS configured.

Impact

Fractured_Blogs reduces publishing friction by turning existing documents into web-ready content without sacrificing structure, design quality, or security in the release process.