Skip to content

Latest commit

 

History

History
45 lines (26 loc) · 1.99 KB

File metadata and controls

45 lines (26 loc) · 1.99 KB

Product

Platform

web

Users

People exploring CodeKokeshi's projects and potential collaborators, with both audiences equally important.

Product Purpose

A personal portfolio for browsing CodeKokeshi's games, experiments, art, software, mods, and plugins. Visitors should be able to see the work itself, explore further, and find the creator's public profiles.

Positioning

The portfolio combines playable games and development experiments with the creator's tools, mods, plugins, and art in one place. It presents the work as it is, without needing a formal professional pitch.

Operating Context

The site is a static GitHub Pages website. Visitors browse its sections on desktop and mobile, open project details and external project pages, and can explore a separate game development timeline.

Capabilities and Constraints

  • Games and experiments should lead the portfolio.
  • Keep the existing project content, working links, browsing controls, and navigation functional through the redesign.
  • The visual language should stay consistent across sections and screen sizes.
  • The existing static HTML, CSS, and JavaScript setup remains the implementation stack.

Brand Commitments

The CodeKokeshi name and the site's personal, informal character are established. The user wants the result to feel like a portfolio rather than an article or a formal professional presentation.

Evidence on Hand

The repository contains real game videos, artwork, software screenshots, mod images, project descriptions, playable pages, and external project links. These assets are the source for the portfolio presentation; no invented project claims are needed.

Product Principles

  1. Lead with actual work, especially games and experiments.
  2. Make the range of work easy to explore without flattening every project into the same card.
  3. Let the creator's voice and projects speak without a formal pitch.
  4. Keep the experience coherent and usable on both mobile and desktop.