Projects
Projects are the central organizing unit for your work. They bring together code repositories, files, feedback, and workflows into a single, manageable space.
What is a Project?
A project represents a distinct piece of work—a client engagement, product, or initiative. Each project can include:
- Connected GitHub repositories
- Files and folders (with hierarchical organization)
- Multiple feedback boards
- Linked workflows and tools
- AI-generated insights and reports
- Portfolio images for showcasing
Creating a Project
When you create a project, you'll provide:
| Field | Description |
|---|---|
| Name | The project's display name |
| Slug | URL-friendly identifier (auto-generated from name) |
| Description | Overview of the project |
| Client | Optional client association |
Project Settings
Visibility
Projects have two main visibility settings:
- Private - Only visible to team members
- Public - Visible on your public profile (when enabled)
Public projects showcase your work to potential clients or employers while keeping internal details private.
Feedback Visibility
Control whether your project's feedback boards are publicly accessible:
- Public feedback - Anyone can view and submit feedback
- Private feedback - Only team members can access feedback boards
This is separate from project visibility—you can have a public project with private feedback.
Tech Stack
Add skills/technologies used in the project. These appear as tags on your public profile and help categorize your work.
Result Blurb
A short (120 characters) summary of the business outcome. Example: "Reduced processing time by 40% through automation."
Custom Task Statuses
Each project can define its own Kanban workflow statuses:
- Go to project settings
- Add custom status columns (e.g., "Review", "QA", "Deployed")
- Set colors for visual distinction
- Choose a default status for new tasks
Project-level statuses override team-level defaults when viewing that project's tasks.
GitHub Integration
Connect GitHub repositories to track activity and pull in context.
Connecting Repositories
- Navigate to your project's Repos tab
- Click Connect Repository
- Select from your authorized GitHub repositories
What Gets Tracked
- Pull Requests - Open, merged, and closed PRs
- Issues - Bug reports and feature requests
- Commits - Recent activity and contributors
- Stats - Lines added/removed, commit frequency
Project Items
PRs and issues become "Project Items" that you can:
- View in a unified timeline
- Filter by status and type
- Link to insights and feedback
Files & Folders
Organize project documents, assets, and deliverables with hierarchical folder support.
Folder Structure
Create nested folders to organize files:
Project Files/
├── Designs/
│ ├── wireframes.fig
│ └── final-mockups.png
├── Documents/
│ └── requirements.pdf
└── Assets/
└── logo.svg
Folders can be nested to any depth, and you can move files between folders as your organization needs evolve.
File Features
- Upload any file type (PDFs, documents, images, spreadsheets)
- Description field for context
- Metadata tracking (size, type, upload date, uploader)
- Storage via configurable providers (S3, Vercel Blob, GCS, R2)
Team-Level Files
Files can also exist at the team level without being tied to a specific project. This is useful for:
- Shared templates
- Company-wide assets
- Cross-project documentation
Upload Limits
- Maximum file size: 25 MB
- Rate limited to prevent abuse (20 uploads per hour per user)
Feedback Boards
Collect and manage feedback from users, clients, or stakeholders. Each project can have multiple feedback boards for different purposes.
Creating a Feedback Board
Each feedback board includes:
| Field | Description |
|---|---|
| Name | Board title |
| Slug | Public URL path |
| Description | What kind of feedback to provide |
| Visibility | Public (anyone) or private (team only) |
| Purpose | Board category (see below) |
Board Purposes
Categorize boards by their intended use:
| Purpose | Use Case |
|---|---|
| General | Open-ended feedback collection |
| A/B Test | Comparing design or feature variants |
| Beta | Early access user feedback |
| Feature-Specific | Feedback on a particular feature |
| Temporal | Time-limited feedback campaigns |
Board Lifecycle
Boards progress through lifecycle states:
- Active - Accepting new feedback
- Closed - No new submissions, existing feedback visible
- Archived - Hidden from normal views
Feedback Types
| Type | Use Case |
|---|---|
| Bug | Report issues and problems |
| Idea | Suggest new features |
| Question | Ask for clarification |
Managing Feedback
- Mark items as New or Done
- Convert feedback to GitHub issues (with one click)
- Add tags for organization
- Track submitter information
Public Feedback
When a board is public:
- Logged-in users - Submissions are linked to their account
- Guest users - Can provide name and email (optional)
- Rate limiting - Prevents spam submissions
- IP address tracking for abuse prevention
Project Insights
Projects can include AI-generated insights that help communicate progress to stakeholders.
What Gets Generated
- Narrative summary - AI-written overview of project progress
- Tech stack detection - Automatically identifies languages, frameworks, and tools
- Stats snapshot - PR counts, issue counts, commit activity, contributors
- Key achievements - Highlights from recent activity
Tech Stack Detection
The system automatically detects:
- Primary languages - Main programming languages used
- Frontend - UI frameworks (React, Vue, etc.)
- Backend - Server frameworks (Express, FastAPI, etc.)
- Infrastructure - Deployment and cloud services
- Databases - Data storage technologies
Version History
Insights are versioned, so you can track how the project summary has evolved over time.
Portfolio Images
Add showcase images for your public project page:
- Cover image - Main project visual (automatically highlighted)
- Gallery images - Additional screenshots or designs
- Display order - Control image sequence
- Captions - Describe what each image shows
- Alt text - Accessibility descriptions for screen readers
Images are stored separately from project files and optimized for public display.
Linking Workflows & Tools
Connect automation workflows and tools to projects to show what powers your work.
Workflow Links
- Go to project settings or the Workflows tab
- Select workflows to link
- Links appear on both the project and workflow pages
This shows clients which automations power their projects.
Tool Links
Link tools from your tools directory to show the tech stack:
- Development tools
- SaaS products used
- Services integrated
Tool links help visitors understand your technology choices.
Best Practices
- Use descriptive names - Clear names help with searching and organization
- Add a tech stack - Improves discoverability on your public profile
- Write result blurbs - Communicate value, not just deliverables
- Organize files in folders - Prevents clutter as projects grow
- Use multiple feedback boards - Separate beta feedback from general inquiries
- Add portfolio images - Visual projects get more engagement
- Link workflows - Show the automation behind your work
Related Concepts
- Accounts & Teams - Projects belong to teams
- Feedback - Deep dive into feedback collection
- Workflows - Link automations to projects
- Tasks & Notes - Manage project tasks
- Public Profiles - Showcase public projects
Next Steps
- Workflows - Learn about automation workflows