Getting Started
Start with PyColors in the right order. Launch a template, validate your SaaS surface, understand the system, and move toward a production-ready business foundation.
Build your SaaS in the right orderLink to section
PyColors helps developers move from idea to credible SaaS product without spending their best time on the wrong layer too early.
The product path is simple:
- launch the marketing page when you need a public offer
- validate the SaaS surface before backend complexity
- build with consistent UI foundations
- use patterns for repeated product behavior
- wire auth, billing, backend, and delivery when the business layer becomes the blocker
- launch with more confidence
This page gives you the fastest path through the PyColors documentation.
Core idea
Launch the page. Validate the product surface. Upgrade when infrastructure becomes the bottleneck.
Choose your starting pointLink to section
Choose by intentLink to section
Start with NA-AI Landing
- premium AI/SaaS landing page
- data-driven content structure
- pricing, FAQ, integrations, testimonials, and contact sections
- dark/light mode and SEO baseline
- powered by PyColors UI and PyColors Tokens
Start with Starter Free
- real SaaS screens
- dashboard and navigation
- auth, billing, admin, and settings surfaces
- mocked data and UI states
- fast demo and MVP validation
Move to Starter Pro
- real authentication
- Stripe Checkout and billing portal
- webhook-driven subscription state
- Prisma-ready backend foundation
- secure delivery after purchase
What you should do firstLink to section
Understand the product ladderLink to section
PyColors is not just a UI library. It is a path from public offer to product validation to SaaS launch:
- Templates help you launch focused marketing pages quickly
- Design System gives visual consistency
- UI gives reusable primitives
- Guides explain how to compose real interfaces
- Patterns solve repeated product flows
- Starter Free validates the product surface
- Starter Pro wires the business layer
Pick the right starting pointLink to section
Use the product that matches your current bottleneck.
Start with a template if you need a public offer. Start with Starter Free if you need product validation. Move to Starter Pro if auth and billing are already the blocker.
Run the project locallyLink to section
Start with the product surface.
Run the app locally, click through the main routes, and understand what is already shaped before changing too much.
Explore the UI foundationsLink to section
Review the primitives that power the product: Button, Input, Card, Badge, Alert, Dialog, and Table.
These components keep the product interface consistent as it grows.
Learn the patternsLink to section
Patterns show how primitives become real product flows: data tables, overlays, async actions, empty states, loading states, and error states.
This is where UI becomes product behavior.
Upgrade when wiring slows you downLink to section
When the question changes from “what should this product feel like?” to “how do I launch this with real users and payments?”, Starter Pro becomes the faster path.
Fastest path by goalLink to section
Launch a landing page
Validate an idea
Launch and monetize
The PyColors systemLink to section
Time to first resultLink to section
| Milestone | Target |
|---|---|
| Open the docs and choose a path | 5 minutes |
| Run a project locally | 10 minutes |
| Understand the main routes | 30 minutes |
| Adapt the product surface | 1–2 hours |
| Ship a first demo | Same day |
| Wire production foundations | When validation is clear |
| Launch with real auth and billing | Starter Pro path |
Time-to-value matters
The faster a builder sees a credible product surface, the faster they understand the value of PyColors.
Recommended reading orderLink to section
Free vs Pro decisionLink to section
| Question | Best path |
|---|---|
| I need a public marketing page | NA-AI Landing |
| I need to validate the product surface | Starter Free |
| I need a credible UI demo | Starter Free |
| I need real accounts and sessions | Starter Pro |
| I need Stripe Checkout and billing portal | Starter Pro |
| I need subscription state to control access | Starter Pro |
| I need secure delivery after purchase | Starter Pro |
| I need to reduce launch risk | Starter Pro |
Upgrade when wiring becomes the bottleneck
Templates launch your offer. Starter Free validates your product. Starter Pro wires your business.
Revenue-focused mental modelLink to section
PyColors is designed around a simple business principle:
Spend less time rebuilding repeated infrastructure. Spend more time on product, positioning, distribution, and customers.
That matters if your goal is to build a serious SaaS business.
The documentation should help every visitor understand:
- what PyColors solves
- where to start
- when a template is enough
- when Free is enough
- when Pro becomes the faster path
- why buying the foundation can be higher leverage than rebuilding it
What to avoidLink to section
Prefer
- choosing the right product for the current bottleneck
- running the project before refactoring
- understanding the Template → Free → Pro path
- validating product UX before deep backend work
- using patterns for repeated product flows
- upgrading when auth and billing slow launch
Avoid
- rewriting everything before understanding the baseline
- starting with billing before validating the product
- mixing UI primitives with business logic
- treating Starter Free as a complete backend
- using a template when you need real auth and billing
- waiting too long to deploy and test the product surface
Next stepsLink to section
Build fast. Validate early. Upgrade when ready.
PyColors is built to help you reduce the distance between idea, product, launch, and revenue.