feat(examples): add Ink & Code developer portfolio design system#138
Open
SulakshanCGhimire wants to merge 1 commit into
Open
feat(examples): add Ink & Code developer portfolio design system#138SulakshanCGhimire wants to merge 1 commit into
SulakshanCGhimire wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new
examples/ink-and-code/entry — a minimal developer portfolio design system.Design concept
Terminal-native minimalism for developers who let their work speak. The aesthetic mirrors how developers think: Geist (geometric sans-serif) for prose, Geist Mono for all UI chrome, labels, and tags. A single burnt orange accent on a deep warm-black canvas. No gradients, no decorative shadows — depth is achieved entirely through tonal surface layers.
Files added
DESIGN.md— design tokens (YAML frontmatter) + rationale (markdown prose)tailwind.config.js— exported via--format json-tailwinddesign_tokens.json— exported via--format dtcgREADME.md— follows the pattern of existing examplesLinter output
{
"summary": { "errors": 0, "warnings": 0, "infos": 1 }
}
Checklist
DESIGN.mdpasses linter with 0 errors, 0 warningstailwind.config.jsgenerated via CLI exportdesign_tokens.jsongenerated via CLI exportBrand & Style→Colors→Typography→Layout & Spacing→Elevation & Depth→Shapes→Components)tailwind.config.js