diff --git a/.claude/settings.local.json b/.claude/settings.local.json deleted file mode 100644 index bdf5683..0000000 --- a/.claude/settings.local.json +++ /dev/null @@ -1,18 +0,0 @@ -{ - "permissions": { - "allow": [ - "WebFetch(domain:github.com)", - "WebFetch(domain:resume.liukersun.com)", - "Bash(npm run dev)", - "Bash(test:*)", - "Bash(for file in makeblock.png hit.png bytedance.png xiasha.png neau.png)", - "Bash(do if [ ! -f \"$file\" ])", - "Bash(then cp me.png \"$file\")", - "Bash(fi)", - "Bash(done)", - "Bash(ls:*)", - "Bash(npm uninstall:*)", - "Bash(npx knip)" - ] - } -} diff --git a/LICENSE b/LICENSE deleted file mode 100644 index f709ac2..0000000 --- a/LICENSE +++ /dev/null @@ -1,21 +0,0 @@ -MIT License - -Copyright (c) 2024 Dillion Verma - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. diff --git a/README.md b/README.md deleted file mode 100644 index d25feab..0000000 --- a/README.md +++ /dev/null @@ -1,47 +0,0 @@ -
-Portfolio -
- -# Portfolio [![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https%3A%2F%2Fgithub.com%2Fdillionverma%2Fportfolio) - -Built with next.js, [shadcn/ui](https://ui.shadcn.com/), and [magic ui](https://magicui.design/), deployed on Vercel. - -# Features - -- Setup only takes a few minutes by editing the [single config file](./src/data/resume.tsx) -- Built using Next.js 14, React, Typescript, Shadcn/UI, TailwindCSS, Framer Motion, Magic UI -- Includes a blog -- Responsive for different devices -- Optimized for Next.js and Vercel - -# Getting Started Locally - -1. Clone this repository to your local machine: - - ```bash - git clone https://github.com/dillionverma/portfolio - ``` - -2. Move to the cloned directory - - ```bash - cd portfolio - ``` - -3. Install dependencies: - - ```bash - pnpm install - ``` - -4. Start the local Server: - - ```bash - pnpm dev - ``` - -5. Open the [Config file](./src/data/resume.tsx) and make changes - -# License - -Licensed under the [MIT license](https://github.com/dillionverma/portfolio/blob/main/LICENSE.md). diff --git a/content/api-design-principles.mdx b/content/api-design-principles.mdx deleted file mode 100644 index f4f15cd..0000000 --- a/content/api-design-principles.mdx +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "REST API Design Principles That Stand the Test of Time" -publishedAt: "2024-12-12" -updatedAt: "2024-12-12" -author: "John Doe" -summary: "Learn how to design APIs that developers love to use and are easy to maintain." -image: "https://images.unsplash.com/photo-1558494949-ef010cbdcc31?w=800&h=192&fit=crop" ---- - -# REST API Design Principles That Stand the Test of Time - -Great APIs feel boring in the best way: predictable, consistent, and easy to reason about. When the surface area is simple, teams ship faster and clients break less often. - -This is a lightweight checklist you can keep in mind while designing new endpoints or reviewing an existing API. - -## Core principles - -- Use clear, consistent **resource names** (think nouns). -- Keep behavior aligned with **HTTP semantics** (read vs write). -- Return **consistent response shapes** so clients don’t guess. -- Prefer **sane defaults** with optional query parameters for filtering/sorting. - -## A simple checklist - -1. Pick stable resource paths (plural nouns are a common convention). -2. Use a small set of status codes consistently. -3. Document pagination and what “next/previous” means. -4. Be explicit about authentication and authorization requirements. -5. Add brief examples in docs for the “happy path” and common errors. - -## Wrap-up - -If you optimize for consistency first, your API will be easier to document, easier to test, and easier for others to adopt. diff --git a/content/building-design-systems.mdx b/content/building-design-systems.mdx deleted file mode 100644 index 01ff2e8..0000000 --- a/content/building-design-systems.mdx +++ /dev/null @@ -1,146 +0,0 @@ ---- -title: "Building Scalable Design Systems with React and Tailwind" -publishedAt: "2024-12-01" -updatedAt: "2024-12-01" -author: "John Doe" -summary: "A comprehensive guide to creating maintainable design systems that scale with your team and product." -image: "https://images.unsplash.com/photo-1558655146-9f40138edfeb?w=800&h=192&fit=crop" ---- - -Design systems are the backbone of consistent user interfaces. Here's how to build one that scales. - -## Why Design Systems Matter - -A well-crafted design system provides: - -- **Consistency** across all products -- **Faster development** with reusable components -- **Better collaboration** between designers and developers -- **Reduced technical debt** over time - -## Core Principles - -### 1. Start with Tokens - -Design tokens are the atomic values of your system: - -```typescript title="tokens.ts" -export const tokens = { - colors: { - primary: { - 50: '#eff6ff', - 500: '#3b82f6', - 900: '#1e3a8a', - }, - neutral: { - 0: '#ffffff', - 100: '#f5f5f5', - 900: '#171717', - }, - }, - spacing: { - xs: '0.25rem', - sm: '0.5rem', - md: '1rem', - lg: '1.5rem', - xl: '2rem', - }, - radii: { - sm: '0.25rem', - md: '0.5rem', - lg: '1rem', - full: '9999px', - }, -} as const; -``` - -### 2. Build Primitive Components - -Start with the basics: - -```tsx title="Button.tsx" -import { cva, type VariantProps } from "class-variance-authority"; - -const buttonVariants = cva( - "inline-flex items-center justify-center rounded-md font-medium transition-colors", - { - variants: { - variant: { - primary: "bg-primary text-white hover:bg-primary/90", - secondary: "bg-secondary text-secondary-foreground hover:bg-secondary/80", - ghost: "hover:bg-accent hover:text-accent-foreground", - }, - size: { - sm: "h-8 px-3 text-sm", - md: "h-10 px-4", - lg: "h-12 px-6 text-lg", - }, - }, - defaultVariants: { - variant: "primary", - size: "md", - }, - } -); - -interface ButtonProps - extends React.ButtonHTMLAttributes, - VariantProps {} - -export function Button({ variant, size, className, ...props }: ButtonProps) { - return ( -