This page collects selected case studies showing how I turn messy systems, workflows, and user problems into clear documentation.
Each case study focuses on how I understand the problem, organize the information, document the process, and make the system easier to follow.
Short on time? Start with the enrollment system case study. It shows the strongest mix of systems documentation, user research, workflow mapping, and technical explanation.
<aside> 💡
Focus:
Systems documentation, UI/UX, BPMN workflow mapping, database planning, and user-centered design.
Summary:
A capstone project focused on turning a manual school enrollment process into a clearer online workflow. I studied the existing process, mapped the system flow, designed user-facing screens, and documented how the structure behind the system works.
What this shows:
I can understand a real-world process, organize messy workflows, and create documentation that supports both users and administrators.
Best viewed for:
Process documentation, systems thinking, user-centered design, workflow mapping, and structured technical documentation.
</aside>
<aside> âš¡
Focus:
Technical documentation, accessibility, deployment workflow, maintainability, and decision documentation.
Summary:
A personal webfolio project built with HTML, CSS, JavaScript, GitHub, Netlify, and a custom domain. This case study documents how the site works, how it was deployed, and why each technical decision was made.
What this shows:
I can explain technical choices clearly, document a simple system, and make a website easier to understand, maintain, and update.
Best viewed for:
Technical writing, website documentation, accessibility notes, deployment process, and decision-based documentation.
</aside>
<aside> 💼
Focus:
Client-facing documentation, handoff, content structure, and technical explanation for a non-technical user.
Summary:
A portfolio website created for a creative professional who needed a working webfolio for his work, services, and story. This case study focuses on structuring the site, explaining the process, and helping the user understand enough to take ownership of it.
What this shows:
I can communicate technical and creative information clearly to someone without a technical background and create explanations that make a system easier to understand, edit, and maintain.
Best viewed for:
Client handoff, non-technical explanation, portfolio content structure, and user-focused documentation.
</aside>
<aside> 💰
Focus:
Help center documentation, plain-language writing, troubleshooting, onboarding, and user-focused support content.
Summary:
A self-initiated documentation project based on public GCash Jr. help information. This case study shows how I turned support topics into a clearer parent-friendly guide with checklists, numbered steps, FAQs, and troubleshooting sections.
What this shows:
I can write for actual users, not just people who already understand the system.
Best viewed for:
Help center writing, user guides, plain-language documentation, troubleshooting content, and task-based information structure.
</aside>