Skip to main content
Need help with GitFolio? This guide shows you where to find support and how to get assistance from the community.

​
Before Asking for Help

Before reaching out, try these steps:
1

Check the Documentation

Review our comprehensive guides:
2

Search Existing Issues

Your question might already be answered:
  • Browse GitHub Issues
  • Check closed issues for resolved problems
  • Search for keywords related to your issue
3

Review the Source Code

The codebase itself can be informative:
  • Look at existing templates for examples
  • Check component implementations
  • Read inline code comments

​
Support Channels

​
GitHub Issues

Best for:
  • Bug reports
  • Feature requests
  • Technical problems
  • Build or setup issues
Create a new issue on GitHub with a clear title and detailed description.
When creating an issue, include:
  • Clear title - Summarize the problem in one line
  • Description - Explain the issue in detail
  • Steps to reproduce - How to recreate the problem
  • Expected behavior - What should happen
  • Actual behavior - What actually happens
  • Environment details:
    • Node.js version (node --version)
    • pnpm version (pnpm --version)
    • Operating system
    • Browser (if applicable)
  • Screenshots - Visual issues benefit from images
  • Code snippets - Relevant code that demonstrates the issue
  • Error messages - Complete error logs

​
GitHub Discussions

Best for:
  • General questions
  • Design discussions
  • Feature ideas
  • Community conversations
  • Showing off your work
Start a discussion in the appropriate category for broader community engagement.

​
Pull Request Comments

Best for:
  • Questions about specific code changes
  • Clarification on review feedback
  • Implementation discussions
  • Code-specific questions

​
Reporting Bugs

When you encounter a bug:
Make sure the issue is reproducible:
  • Clear your cache and try again
  • Test in a fresh clone of the repository
  • Verify your dependencies are up to date
  • Check if it happens in different environments
Collect relevant details:
# Check versions
node --version
pnpm --version
git --version

# Get build output
pnpm run build 2>&1 | tee build.log

# Check for errors
pnpm run lint
Simplify the problem:
  • Remove unrelated code
  • Isolate the specific component or feature
  • Create a minimal example that shows the bug
  • Test that the minimal example still reproduces the issue
Use this template:
## Bug Description
[Clear description of what's wrong]

## Steps to Reproduce
1. Clone the repository
2. Run `pnpm install`
3. Run `pnpm run dev --filter=renderer`
4. Navigate to [specific page]
5. [Action that triggers the bug]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- Node.js: v20.x.x
- pnpm: 10.23.0
- OS: macOS 14.0 / Windows 11 / Ubuntu 22.04
- Browser: Chrome 120 (if applicable)

## Screenshots
[If applicable]

## Additional Context
[Any other relevant information]

​
Requesting Features

Have an idea for GitFolio?
1

Check Existing Requests

Search issues and discussions to see if someone else has suggested the same feature.
2

Describe the Use Case

Explain:
  • What problem does this solve?
  • Who would benefit from this feature?
  • How would it work from a user perspective?
  • Are there examples of this in other projects?
3

Propose Implementation (Optional)

If you have technical ideas:
  • How could this be implemented?
  • What changes would be needed?
  • Are there any technical challenges?
  • Would you be willing to contribute the implementation?
4

Submit the Request

Create a GitHub issue with the “Feature Request” label or start a discussion.

​
Getting Code Review Help

If you’re stuck during code review:
If review comments are unclear:
  • Ask for clarification directly in the PR
  • Request specific examples
  • Ask about the reasoning behind suggestions
  • Be respectful and open to learning
If you’re unsure about changes:
  • Make your best attempt at addressing feedback
  • Comment on what you’re uncertain about
  • Ask for a second opinion
  • Request a re-review when ready
Look at merged PRs:
  • Find similar changes that were accepted
  • Study how feedback was addressed
  • Learn from successful contributions
  • Apply those patterns to your work

​
Community Guidelines

When seeking support:

​
Be Respectful

  • Treat everyone with kindness and respect
  • Assume good intentions
  • Be patient - maintainers and contributors are volunteers
  • Thank people for their help

​
Be Clear

  • Use descriptive titles
  • Provide complete information
  • Format code with syntax highlighting
  • Use screenshots when helpful

​
Be Patient

  • Responses may take time
  • Maintainers have other commitments
  • Don’t bump issues immediately
  • Follow up politely if needed

​
Be Collaborative

  • Share solutions you find
  • Help others when you can
  • Contribute back to the community
  • Document your learnings

​
Common Issues & Solutions

Issue: Dependencies won’t installSolutions:
# Clear pnpm cache
pnpm store prune

# Remove node_modules and lock file
rm -rf node_modules pnpm-lock.yaml

# Reinstall
pnpm install

# Verify Node version
node --version  # Should be 20+
Issue: Build fails with errorsSolutions:
# Clear Turborepo cache
rm -rf .turbo

# Clear Next.js cache
rm -rf apps/renderer/.next

# Rebuild
pnpm run build

# Check TypeScript errors
pnpm run lint
Issue: Dev server won’t startSolutions:
  • Check if port 3000 is in use
  • Verify environment variables
  • Check console for errors
  • Try killing all Node processes and restarting
# Kill Node processes (macOS/Linux)
pkill -f node

# Restart dev server
pnpm run dev --filter=renderer
Issue: Changes don’t reflect in browserSolutions:
  • Hard refresh browser (Cmd/Ctrl + Shift + R)
  • Restart dev server
  • Clear browser cache
  • Check if you’re editing the correct file
  • Verify file watchers aren’t maxed out (Linux)
Issue: Type errors in your codeSolutions:
  • Import types from @workspace/types
  • Check TypeScript documentation
  • Look at existing templates for examples
  • Use proper type annotations
  • Don’t use any - use specific types

​
Response Time Expectations

Typical response times:
  • GitHub Issues - Usually within a few days
  • Pull Requests - Initial review within a week
  • Discussions - Community responses may vary
  • Critical bugs - Higher priority, faster response
All maintainers and contributors are volunteers. Please be patient and understanding with response times.

​
Contributing to Support

Help others in the community:
  • Answer questions in discussions
  • Help troubleshoot issues
  • Review pull requests
  • Improve documentation
  • Share your experiences
Every contribution helps make GitFolio better!

​
Emergency Contact

For urgent security issues:
Do NOT report security vulnerabilities in public issues. Contact the maintainers privately through GitHub or the email in the repository.

​
Additional Resources

​
Get Involved

The best way to get support is to be part of the community:
  • Star the repository on GitHub
  • Watch for updates and discussions
  • Participate in conversations
  • Share your templates and experiences
  • Help other contributors
Together, we’re building something great for developers worldwide!

Build docs developers (and LLMs) love

Get started for freeTalk to us