### Install Dependencies and Setup Environment

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/CONTRIBUTING.md

These commands install project dependencies using npm and copy the example environment file to create a local configuration. This is essential before making any code changes.

```bash
npm install
cp .env.example .env.local
```

--------------------------------

### Initialize Development Environment

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/README.md

Commands to clone the repository, install necessary dependencies, configure environment variables, and start the local development server.

```bash
git clone https://github.com/OliFarhaan/backend-portfolio.git
cd backend-portfolio
pnpm install
cp .env.example .env.local
pnpm dev
```

--------------------------------

### Build and Start Application (Bash)

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/README.md

These commands are used to build the project for production and then start the server. This is a common deployment step for Node.js applications, particularly when not using a platform like Vercel that handles builds automatically.

```bash
pnpm build
pnpm start
```

--------------------------------

### Define Portfolio Data Structures

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/README.md

Examples of JSON schemas used within portfolio.json to define projects, work experience, personal details, and social links.

```json
{
  "name": "My Project",
  "description": "Short tagline for the project",
  "tech": ["Spring", "Redis", "Docker"],
  "url": "https://github.com/username/my-project",
  "points": [
    "Built feature X that does Y.",
    "Implemented Z for better performance."
  ]
}
```

```json
{
  "company": "Acme Corp",
  "role": "Software Engineer",
  "period": "Jan 2025 — Present",
  "location": "Remote",
  "tag": "Founding",
  "points": [
    "Led the backend architecture for the core product.",
    "Built CI/CD pipelines using GitHub Actions."
  ]
}
```

```json
{
  "personal": {
    "footerName": "Your Name",
    "repoUrl": "https://github.com/username/repo"
  }
}
```

```json
{ "label": "GitHub", "url": "https://github.com/username" }
```

--------------------------------

### Run Development and Build Commands

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/CONTRIBUTING.md

These npm scripts are used to run the development server for visual checks, build the project for production, and check for linting errors. They are crucial for verifying changes before committing.

```bash
npm run dev
npm run build
npm run lint
```

--------------------------------

### Commit Changes with a Message

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/CONTRIBUTING.md

This command stages changes and commits them with a descriptive message. Following conventional commit message formats (e.g., 'fix:', 'feat:') is recommended for clarity.

```bash
git commit -m "fix: description of what changed and why"
```

--------------------------------

### Create Git Branch

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/CONTRIBUTING.md

This command creates a new Git branch for your changes. It's a standard practice to name branches descriptively, often prefixed with 'fix/', 'feat/', or 'chore/'.

```bash
git checkout -b fix/description-of-change
```

--------------------------------

### Change Monospace Font Import (Next.js)

Source: https://github.com/olifarhaan/backend-portfolio/blob/main/README.md

This snippet shows how to import and configure a Google Font in a Next.js application. It specifies the font variable name, subsets, and weights. To change the font, replace 'Fira_Code' with a font from Google Fonts and update the variable name if necessary.

```tsx
import { Fira_Code } from "next/font/google";

const firaCode = Fira_Code({
  variable: "--font-fira-code",
  subsets: ["latin"],
  weight: ["300", "400", "500", "600", "700"],
});
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.