IJOURNAL x WEBIMPACTUW · PROJECT MANAGEMENT + PRODUCT MANAGEMENT
Bridging client vision and technical execution to deliver a collaborative web experience.
Bridging client vision and technical execution to deliver a collaborative web experience.
Bridging client vision and technical execution to deliver a collaborative web experience.
iJournal x WebImpactUW
iJournal x WebImpactUW
iJournal x WebImpactUW
OVERVIEW
OVERVIEW
OVERVIEW
iJournal, a University of Washington student publication organization, partnered with Web Impact UW to transform their original static publication website into a scalable web platform that better represented its content, mission, and community. Over six moths, working alongside developers, designers, and client stakeholders, I managed project operations and communication throughout the development process to ensure the project remained organized and on schedule. Our main goal was to empower editors to independently publish content while creating a richer reading experience for students.
iJournal, a University of Washington student publication organization, partnered with Web Impact UW to transform their original static publication website into a scalable web platform that better represented its content, mission, and community. Over six moths, working alongside developers, designers, and client stakeholders, I managed project operations and communication throughout the development process to ensure the project remained organized and on schedule. Our main goal was to empower editors to independently publish content while creating a richer reading experience for students.
iJournal, a University of Washington student publication organization, partnered with Web Impact UW to transform their original static publication website into a scalable web platform that better represented its content, mission, and community. Over six moths, working alongside developers, designers, and client stakeholders, I managed project operations and communication throughout the development process to ensure the project remained organized and on schedule. Our main goal was to empower editors to independently publish content while creating a richer reading experience for students.
ROLE
Project Manager
TEAM
Jonathan P., Kim P., Nathan A.
DURATION
6 Months
SOFTWARE
Freedcamp • Next.js • Sanity CMS • MongoDB • Vercel • Framer
Freedcamp • Next.js • Sanity CMS • MongoDB • Vercel • Framer
AT A GLANCE
AT A GLANCE
AT A GLANCE
PROBLEM
As iJournal continued publishing new research and articles, their existing website made it difficult to manage content efficiently, engage readers, and scale the platform over time.
iJournal's Framer-based website made content management difficult, redirected readers to external PDF links, and lacked features for long-term growth and reader engagement.
As iJournal continued publishing new research and articles, their existing website made it difficult to manage content efficiently, engage readers, and scale the platform over time.
iJournal’s Framer-based website made content management difficult, redirected readers to external PDF links, and lacked features for long-term growth and reader engagement.
As iJournal continued publishing new research and articles, their existing website made it difficult to manage content efficiently, engage readers, and scale the platform over time.
iJournal’s Framer-based website made content management difficult, redirected readers to external PDF links, and lacked features for long-term growth and reader engagement.
CHALLENGE
Transform iJournal's static Framer website into a scalable publishing platform while preserving the organization's visual identity (+ brand guidelines). Coordinate cross-functional teams, translated stakeholder needs into development priorities, and guide product delivery over six months.
Transform iJournal’s static Framer website into a scalable publishing platform while preserving the organization’s visual identity (+ brand guidelines).
Transform iJournal’s static Framer website into a scalable publishing platform while preserving the organization’s visual identity (+ brand guidelines).
OUTCOME
Successfully launched the platform, enabling long-term editorial independence and earning the project's Best Overall Award.
Transform iJournal’s static Framer website into a scalable publishing platform while preserving the organization’s visual identity (+ brand guidelines).
Transform iJournal’s static Framer website into a scalable publishing platform while preserving the organization’s visual identity (+ brand guidelines).
FINAL DESIGN IMPLEMENTATION
FINAL DESIGN IMPLEMENTATION
WEBPAGES
PROCESS
PROCESS
PROCESS
KEY RESPONSIBILITIES
This project required balancing communication across multiple independent teams over six months. To maintain alignment, I established a consistent communication rhythm:
Weekly developer meetings focused on implementation progress, blockers, and sprint planning.
Biweekly client meetings focused on validating features, gathering editorial feedback, and refining project priorities.
Between meetings, I maintained project documentation and tracked development progress through Freedcamp to ensure every stakeholder shared the same understanding of project status.
This communication structure reduced ambiguity, accelerated decision-making, and helped maintain steady development throughout the project.
This project required balancing communication across multiple independent teams over six months. To maintain alignment, I established a consistent communication rhythm:
Weekly developer meetings focused on implementation progress, blockers, and sprint planning.
Biweekly client meetings focused on validating features, gathering editorial feedback, and refining project priorities.
Between meetings, I maintained project documentation and tracked development progress through Freedcamp to ensure every stakeholder shared the same understanding of project status.
This communication structure reduced ambiguity, accelerated decision-making, and helped maintain steady development throughout the project.
This project required balancing communication across multiple independent teams over six months. To maintain alignment, I established a consistent communication rhythm:
Weekly developer meetings focused on implementation progress, blockers, and sprint planning.
Biweekly client meetings focused on validating features, gathering editorial feedback, and refining project priorities.
Between meetings, I maintained project documentation and tracked development progress through Freedcamp to ensure every stakeholder shared the same understanding of project status.
This communication structure reduced ambiguity, accelerated decision-making, and helped maintain steady development throughout the project.
BRAND GUIDELINES / PROJECT MANAGEMENT PLATFORM
ROLE
TIMELINE
SOLUTION
SOLUTION
PRODUCT DECISIONS
PRODUCT DECISIONS
As Project Manager, I coordinated the collaboration between the iJournal executive and design team and Web Impact developers to transform the site into a scalable web app. We implemented a scalable content management workflow using Sanity CMS, enabled easier publishing, integrated reader engagement features like comments, and improved the user experience through an embedded PDF reader with page-flipping interactions.
As Project Manager, I coordinated the collaboration between the iJournal executive and design team and Web Impact developers to transform the site into a scalable web app. We implemented a scalable content management workflow using Sanity CMS, enabled easier publishing, integrated reader engagement features like comments, and improved the user experience through an embedded PDF reader with page-flipping interactions.
As Project Manager, I coordinated the collaboration between the iJournal executive and design team and Web Impact developers to transform the site into a scalable web app. We implemented a scalable content management workflow using Sanity CMS, enabled easier publishing, integrated reader engagement features like comments, and improved the user experience through an embedded PDF reader with page-flipping interactions.
CMS-POWERED PUBLISHING WORKFLOW
Editors can publish and manage articles through a centralized content management system, reducing manual updates and making long-term site maintenance significantly easier.
The new platform introduced a streamlined publishing workflow using Sanity CMS and MongoDB, allowing editors to easily upload, manage, and update articles without requiring developer intervention. We also implemented reader-focused features such as article comment sections to encourage community engagement.
INTEGRATED PUBLICATION READER
An embedded PDF viewer with page-flipping interactions keeps readers on the website, creating a more seamless and engaging reading experience than redirecting to external PDF platforms.
READER ENGAGEMENT ACTIVITY
A built-in commenting feature encourages discussion directly on articles, allowing readers to engage with content and fostering a stronger sense of community around iJournal's publications.
A built-in commenting feature encourages discussion directly on articles, allowing readers to engage with content and fostering a stronger sense of community around iJournal’s publications.
OUTCOME
OUTCOME
OUTCOME
KEY RESPONSIBILITIES
The project was recognized with the Best Overall Award, reflecting the successful collaboration between the client and development team.
01.
A headless CMS that enables editors to publish new articles without developer support
02.
An integrated PDF reader that keeps readers within the site instead of redirecting them to external documents.
03.
A built-in commenting feature that encourages reader engagement.
04.
modernized web application deployed for ongoing use by the organization.
NEXT STEPS
NEXT STEPS
REFLECTION
REFLECTION
Leading iJournal fundamentally changed how I think about product development.
Leading iJournal fundamentally changed how I think about product development.
Leading iJournal fundamentally changed how I think about product development.
Rather than viewing project management as task coordination, I learned that successful product delivery depends on creating shared understanding between people with different priorities, expertise, and expectations. The most valuable decisions were often not technical—they were communication decisions that clarified scope, aligned stakeholders, and enabled developers to work with confidence.
This experience strengthened my appreciation for product leadership as a design discipline in itself. By establishing consistent communication, documenting decisions, and translating stakeholder needs into actionable work, I helped guide a multidisciplinary team toward delivering a product that continues to support the organization beyond the project's completion.
Rather than viewing project management as task coordination, I learned that successful product delivery depends on creating shared understanding between people with different priorities, expertise, and expectations. The most valuable decisions were often not technical—they were communication decisions that clarified scope, aligned stakeholders, and enabled developers to work with confidence.
This experience strengthened my appreciation for product leadership as a design discipline in itself. By establishing consistent communication, documenting decisions, and translating stakeholder needs into actionable work, I helped guide a multidisciplinary team toward delivering a product that continues to support the organization beyond the project's completion.
Rather than viewing project management as task coordination, I learned that successful product delivery depends on creating shared understanding between people with different priorities, expertise, and expectations. The most valuable decisions were often not technical—they were communication decisions that clarified scope, aligned stakeholders, and enabled developers to work with confidence.
This experience strengthened my appreciation for product leadership as a design discipline in itself. By establishing consistent communication, documenting decisions, and translating stakeholder needs into actionable work, I helped guide a multidisciplinary team toward delivering a product that continues to support the organization beyond the project's completion.