Support & Contribute

**Describe the bug**
A clear description of what's wrong.

**To Reproduce**
1. Go to '...'
2. Click on '...'
3. See error

**Expected behavior**
What you expected to happen.

**Screenshots**
If applicable, add screenshots.

**Environment:**
- OS: [e.g., Windows 11, macOS 14]
- Browser: [e.g., Chrome 119]
- Node version: [e.g., 18.17.0]

Warning

Please search existing issues before creating a new one to avoid duplicates!

💡 Suggest Features

Have an idea for improvement?

Open a feature request
Label it as “enhancement”
Describe the feature and use case
Explain why it would be useful

Good feature request template:

**Feature Description**
Clear description of the proposed feature.

**Problem it Solves**
What problem does this solve?

**Proposed Solution**
How would this feature work?

**Alternatives Considered**
Other approaches you've thought about.

**Additional Context**
Mockups, examples, or references.

📝 Improve Documentation

Documentation is crucial! Help make it better:

Ways to contribute:

Fix typos or unclear explanations
Add missing information
Create tutorials or guides
Translate documentation
Add code examples

How to contribute:

Fork the repository
Edit Markdown files
Submit a pull request

Tip

Even fixing a single typo helps thousands of future readers!

Contributing Code

Ready to dive into the codebase? Awesome!

Getting Started

1. Fork the Repository

Click Fork on GitHub to create your copy.

2. Clone Your Fork

git clone https://github.com/YOUR_USERNAME/your-blog.git
cd your-blog

3. Create a Branch

git checkout -b feature/your-feature-name

Branch naming conventions:

feature/ - New features
fix/ - Bug fixes
docs/ - Documentation
refactor/ - Code refactoring
style/ - Code style changes

4. Install Dependencies

npm install

5. Start Development

npm run dev

Making Changes

Code Style

Follow existing patterns:

Use TypeScript for type safety
Follow Airbnb style guide
Use meaningful variable names
Comment complex logic
Keep functions small and focused

Testing Locally

Before submitting:

# Build successfully
npm run build

# Check for TypeScript errors
npm run astro check

# Preview production build
npm run preview

Warning

Make sure there are no console errors in both light and dark modes!

Submitting Changes

1. Commit Your Changes

Follow Conventional Commits:

git commit -m "feat: add amazing feature"
git commit -m "fix: resolve navigation bug"
git commit -m "docs: update installation guide"

Commit types:

feat: - New feature
fix: - Bug fix
docs: - Documentation
style: - Code formatting
refactor: - Code refactoring
test: - Adding tests
chore: - Maintenance

2. Push to Your Fork

git push origin feature/your-feature-name

3. Open a Pull Request

Go to your fork on GitHub
Click Pull Request
Fill in the template
Wait for review

Good PR description:

## Description
What does this PR do?

## Changes Made
- Added X feature
- Fixed Y bug
- Updated Z documentation

## Testing
How was this tested?

## Screenshots
If applicable, add screenshots.

## Related Issues
Fixes #123