Skip to content
Ayush RoyEditorial portfolio system
HomeAboutProjectsExperienceSkillsGamesContact
Resume
Continue to next

Guided journey

Continue the intentional walkthrough instead of jumping randomly.

Next: About
Founder of Yor Zenith - Full Stack Developer Intern CandidateAyush Roy

Portfolio, profile, case studies, games, achievements, and dashboard surfaces now share one editorial system rooted in the hobbies design language.

Explore
AboutProjectsExperienceSkillsContact
GamesAchievementsStatsTimelineDashboardProfileSearchOnboarding
Resources
ResumeCVBlogDevLogGalleryMediaSteamHobbiesFunValue EducationAvatar3D DemoSettingsGitHub
ayushroy.dev@gmail.com+91 8918940799linkedin.com/in/yorayriniwnl
Copyright 2026 / Built with Next.js

Studio Notes / Portfolio System

Accuracy Is Part of the Interface

A portfolio works better when missing information stays labeled and real signals stay visible.

← All Notes
Build Log2026-04-10·4 min read
build-logportfoliodesignux

The Default Mistake

The default portfolio strategy fills every gap. If a project doesn't have a deployment URL, link to something adjacent. If a role doesn't have a strong outcome, describe the process as if it implies one. If a skill hasn't been used in a year, list it anyway and hope no one checks.

This strategy feels safe because it makes the page look complete. It is not safe. A reader who presses on any fabricated claim finds nothing behind it. The emptiness is more damaging than a labelled gap would have been.

Labelling What Is Missing

The alternative is to treat missing information as a design problem rather than a credibility problem. A placeholder is not a failure — it is a signal that the section is under construction.

This portfolio uses explicit placeholder labels. Sections without verified data are marked. Projects that are in progress are described as in progress. Experience items that cannot be verified with documentation are flagged with a distinct visual treatment.

The result is a site that a reader can trust further than they can currently verify, because they can see exactly where the unverified parts are.

Visibility as Interface Decision

"Accuracy is part of the interface" is not a philosophical position. It is a practical one.

An interface that surfaces its limitations is easier to use than one that hides them. A map that marks unexplored territory is more useful than one that invents terrain. A portfolio that shows which projects have public repos and which don't is easier to evaluate than one that omits the distinction.

The design work here was in deciding what to show, not just how to show it. Color tokens for verified versus placeholder. Card variants that communicate status. A reading flow that leads with the strongest signals rather than burying them.

What Gets Removed

Accuracy also means removing things. Three projects were cut from the initial list because the descriptions couldn't be backed by anything concrete. A skills section was consolidated because the original version listed technologies that had only been touched in tutorials.

Cutting is harder than labelling, but it produces a more credible result. A shorter, accurate list reads better than a longer padded one.

The Standard Going Forward

Every new piece of content added to this portfolio will follow the same standard: real evidence or an honest placeholder. Nothing in between.