Skip to content
Ecosystem updates

Changelog

Product updates across PyColors: UI, Starters, Templates, and premium product direction. Clear versions, stable conventions, and documentation-first releases.

Changelog entries reflect shipped work and public-facing release notes. For future direction, packaging, pricing, or launch intent, use the roadmap, access, and upgrade pages.

Release philosophy PyColors ships in public through release-driven iterations. The changelog records shipped work. The roadmap tracks priority direction. The access and upgrade pages define the premium path more clearly than the changelog does.

v1.8.0Stable

Starter Pro security hardening, account security activity, premium auth UX, pricing clarity, and production-shaped app surfaces

Apr 2026 (weekly release)
View roadmap

This release materially upgrades Starter Pro from a credible auth-and-billing baseline into a much stronger launch candidate. It hardens core auth actions with rate limiting and auditing, surfaces backend-driven security activity inside settings, improves self-service account management for provider-based users, and refines authentication UX into a more premium SaaS entry experience. On the product and marketing side, it sharpens pricing and docs around real SaaS monetization, improves dashboard, admin, and projects surfaces, and makes the premium path feel more intentional, secure, and commercially credible.

Security hardening for authentication flows

  • Added configurable rate limiting for login, password reset, verification resend, password change, and password creation flows to reduce abuse and brute-force risk.
  • Introduced auditing for authentication-related actions with metadata such as IP address and user agent to improve traceability and account monitoring.
  • Adopted more generic success and error messaging across sensitive auth actions to reduce information leakage and improve security posture.
  • Extended server-side auth flows with safer operational behavior instead of relying only on UI-level validation.

Backend-driven security activity in settings

  • Integrated recent security activity directly into the backend-driven settings page so users can review sign-ins, password changes, verification actions, and related auth events.
  • Improved activity lookup to match both user ID and normalized email for better coverage of security-relevant events.
  • Made security activity rendering hydration-safe and aligned timestamps with French locale and Paris time for a more reliable and user-friendly experience.
  • Improved device and source labels by mapping localhost and unknown addresses to clearer human-readable values such as “Local device” and “Unknown device”.

Stronger self-service account management

  • Added support for users who signed up with Google or GitHub to set a local password when none exists, improving long-term account flexibility and recovery options.
  • Added a dedicated UI card for password creation with server-side validation, rate limiting, and email notification behavior.
  • Refined connected account logic so provider disconnect rules are computed more safely and always preserve at least one valid sign-in path.
  • Improved provider utility functions and primary-provider label handling to make provider-related account states clearer and more maintainable.

Premium auth UX and safer public auth routing

  • Redirect authenticated users away from login, register, forgot-password, and similar public auth pages to avoid redundant access and reduce confusion.
  • Revamped the auth layout into a more premium two-column SaaS entry surface with stronger hierarchy, product highlights, and better trust signaling.
  • Polished login, registration, forgot password, verify email, and resend verification flows with clearer helper text, better loading states, improved skeletons, and stronger user guidance.
  • Improved auth screen consistency so Starter Pro feels less like an internal implementation and more like a sellable premium product.

Pricing, billing docs, and backend narrative are clearer

  • Raised Starter Pro pricing from €249 to €299 to better align positioning with product value and premium business goals.
  • Revamped the pricing page with clearer product positioning, deeper feature explanation, stronger FAQ content, and better monetization messaging.
  • Added and refined PRO billing documentation to explain how Stripe-backed monetization works in a real SaaS context.
  • Expanded and improved the SaaS PRO docs structure with dedicated auth, billing, and backend guides so the premium offer feels more complete and implementation-ready.

App surfaces now look more production-shaped

  • Improved the user menu with a temporary pro-ready avatar experience, provider indicators, fallback initials, and a clearer signed-in account surface.
  • Refined the dashboard to communicate a more monetizable, B2B-ready SaaS product shape with stronger summary cards, surface cards, and business-oriented copy.
  • Upgraded projects list and detail pages into a more premium entity surface with search, richer detail views, not-found handling, and a stronger foundation for future CRUD, billing, membership, and analytics features.
  • Added a reusable Pro gating direction and analytics teaser on projects pages to reinforce premium upgrade logic without breaking the product flow.
  • Enhanced the admin members experience with search, stats, invitation filtering, and clearer production-oriented structure.

Marketing and navigation quality improvements

  • Improved mobile navigation accessibility by switching to a native dialog-based flow with better semantics, focus behavior, and background scroll prevention.
  • Added a more user-friendly global 404 page with clearer recovery paths and navigation options.
  • Improved app navigation by supporting badges such as “Pro”, handling external links more safely, and enforcing a required upgrade URL through explicit configuration validation.
  • Continued tightening docs ordering, release messaging, and premium-path clarity so the public product surface better supports conversion.

Project hygiene and local setup cleanup

  • Expanded ignore rules to better cover generated files, IDE metadata, and local development artifacts.
  • Clarified local database environment defaults for easier onboarding.
  • Added then removed a marketing Docker Compose setup to avoid unnecessary maintenance and keep the local development story cleaner.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.7.0Stable

Starter Pro account management, OAuth UX, connected accounts, and in-session security flows

Apr 2026 (weekly release)
View roadmap

This release pushes Starter Pro beyond the initial auth baseline into a much more credible account system. It strengthens Google and GitHub authentication across sign-up and sign-in, improves provider configuration and safer error handling, adds connected accounts management in settings, enables secure provider disconnect rules, and ships the first real in-session password change flow. On the product side, Starter Pro now feels less like an auth prototype and more like a real SaaS account surface with persistent user data, clearer account state, and safer self-service security controls.

OAuth sign-in and sign-up UX is now first-class

  • Added configurable Google and GitHub OAuth buttons for authentication with loading states and flexible provider visibility.
  • Added OAuth sign-up on the registration page so users can onboard faster without going through the email-password path first.
  • Added OAuth login options on the sign-in page with clearer separation between provider-based access and credentials-based access.
  • Refined helper text, form structure, and divider logic across registration and login so auth entry points feel more intentional and easier to understand.
  • Improved alert rendering and messaging across auth screens to guide users more clearly through available authentication options.

Safer auth configuration and account conflict handling

  • Improved provider configuration defaults and credential validation to make auth setup more robust and production-oriented.
  • Normalized auth input handling and refined user update logic during sign-in and account-link events for better consistency.
  • Improved email verification updates and profile synchronization when users authenticate through external providers.
  • Handled OAuth account conflicts with safer user-facing messaging so sign-in errors are clearer and less confusing.
  • Mapped query-parameter auth errors into readable product feedback instead of exposing vague or low-context failure states.

Connected accounts management in settings

  • Added a real connected accounts management card in security settings for Google and GitHub providers.
  • Replaced mock account settings sections with backend-driven auth data so settings now reflect the real signed-in user state.
  • Added backend logic to snapshot linked providers and expose accurate connection state in the UI.
  • Improved provider row readability and prop safety to make account management components clearer and easier to maintain.
  • Refocused settings around profile, security, provider connections, and verification state instead of placeholder organization and billing tabs.

Safe disconnect rules and password self-service

  • Added backend-driven connected account management with provider disconnect support directly from settings.
  • Enforced a critical safety rule that prevents users from disconnecting their last available sign-in method.
  • Added clearer UI feedback and guarded error handling for disconnect attempts and allowed account actions.
  • Shipped the first real in-session password change flow for signed-in users.
  • Added validation, feedback, and notification logic around password updates so account security management is now materially more complete.

Authenticated product surfaces feel more real

  • Hydrated the user menu from real server-side auth and account data instead of using a static user placeholder.
  • Improved personalization by surfacing the signed-in user name, email, and provider context in the app shell.
  • Moved mobile user navigation into a dedicated component for cleaner separation and easier future extension.
  • Improved perceived product authenticity by making account state visible across navigation and settings.

Email delivery and environment consistency

  • Corrected email sender logic for development and production modes so transactional auth emails use the right sender configuration per environment.
  • Improved environment variable usage around email delivery and trusted auth hosts to reduce setup mistakes between local and production deployments.
  • Continued tightening the production-readiness path for auth infrastructure started in the previous release.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.6.0Stable

Starter Pro auth foundation + transactional auth emails + marketing UX polish

Mar 2026 (weekly release)
View roadmap

This release moves Starter Pro from billing-first groundwork into a real authentication baseline. It adds Auth.js with Prisma-backed user, account, session, token, and auth-attempt models; brings credentials and OAuth-ready flows into the product; ships registration, login, email verification, forgot password, and reset password foundations; and connects billing flows to the authenticated user instead of a temporary development account. On the marketing side, it also improves breadcrumbs, mobile navigation behavior, footer polish, page structure, and homepage clarity for a cleaner and more reliable product experience.

Starter Pro auth foundation (Auth.js + Prisma)

  • Extended the user model with authentication-ready fields including password hash, email verification timestamp, image, and last login tracking.
  • Added Auth.js core Prisma models for accounts, sessions, and verification tokens, plus dedicated auth token and auth attempt models for security and recovery workflows.
  • Added NextAuth and Prisma adapter dependencies and introduced a full Auth.js configuration with credentials, Google, GitHub, and email provider support.
  • Switched session handling to JWT for a simpler and more consistent stateless auth architecture.
  • Extended session and JWT typings so custom user fields remain strongly typed across the app.

Real user flows: registration, login, verification, reset password

  • Added server-side registration and login actions with validation, password hashing, and clearer error handling.
  • Connected login and registration forms to real server actions with pending states, validation feedback, and improved submission UX.
  • Added the post-signup email verification prompt to guide users through account activation.
  • Implemented forgot password and reset password flows with token-based validation and user-facing reset pages.
  • Added resend verification support so users can request a new verification email if needed.

Transactional auth emails

  • Added Resend integration for transactional auth emails.
  • Introduced reusable auth email templates for email verification, password reset, and password changed notifications.
  • Replaced development-only logging of verification and reset links with real email delivery.
  • Send verification emails after registration, resend requests, and reset emails when a password recovery request is made.
  • Notify users by email after a successful password reset to improve account security awareness.

Billing integration now uses the authenticated user

  • Replaced temporary development-user billing lookups with authenticated user retrieval.
  • Enforced authentication for checkout and billing portal session creation.
  • Improved billing portal session creation by validating customer existence and portal URL generation.
  • Added helpers for current user retrieval, required authentication, and required email verification to centralize access control.
  • Clarified remaining development-only helpers while continuing the migration from dev scaffolding to production-ready auth flows.

Marketing UX and navigation polish

  • Added breadcrumb navigation to key marketing pages and improved breadcrumb UX on mobile with collapsing and overflow handling.
  • Redesigned the mobile header navigation with grouped sections, icons, badges, preserved scroll position, and better body scroll locking.
  • Fixed mobile menu scroll handling and overscroll edge cases for a more reliable menu experience.
  • Improved footer layout, header spacing, container behavior, semantic structure, 404 guidance, and CTA section responsiveness.
  • Refined the homepage and broader marketing copy for clearer messaging and stronger product discovery.

Developer experience and configuration

  • Expanded environment example documentation for auth, email, OAuth providers, and seed options.
  • Added support for auth seed fixtures and improved seed refresh behavior through upserts.
  • Added bcryptjs for password hashing and improved schema support for auth and security indexing.
  • Updated generated type import paths to align with the current Next.js development structure.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.5.0Stable

Blog platform + billing maturity + marketing clarity

Mar 2026 (weekly release)
Read the blog

This release significantly expands PyColors as a SaaS builder ecosystem by introducing a full blog platform with SEO-first architecture, improving billing reliability and Stripe integration, and refining marketing surfaces for clarity, navigation, and conversion. It strengthens both the distribution engine (content + SEO) and the monetization foundation (billing + PRO access).

Blog platform (SEO + content engine)

  • Introduced a full blog system with dynamic article pages, categories, tags, and structured navigation.
  • Added blog landing page with featured and latest articles to improve content discovery and engagement.
  • Implemented tag and category archive pages with SEO metadata and improved navigation.
  • Added JSON-LD structured data, Open Graph images, RSS feed, and sitemap integration for stronger SEO.
  • Introduced reusable blog components: article header, cards, pagination, related posts, author badge, and CTAs.
  • Added “On this page” navigation and improved reading experience with styled prose and layout consistency.

Billing system maturity (Stripe + lifecycle)

  • Implemented full Stripe checkout flow with customer creation, session handling, and plan validation.
  • Added Stripe webhook processing with subscription and invoice synchronization.
  • Introduced webhook event tracking with status lifecycle (RECEIVED, PROCESSED, FAILED) and idempotency safeguards.
  • Improved billing page UX with real subscription data, invoice history, trial messaging, and contextual alerts.
  • Added billing portal integration and management actions (cancel, resume, manage subscription).
  • Enforced PRO access for protected routes with subscription validation logic.

Marketing clarity & navigation refactor

  • Refactored major marketing pages (About, Upgrade, Starters, Guides, UI, Access, Templates) with improved structure and breadcrumbs.
  • Added Blog to main navigation and improved discoverability of learning content.
  • Improved waitlist and upgrade flows with clearer value proposition, pricing communication, and CTAs.
  • Refined SEO metadata handling with centralized constants and absolute URL utilities.
  • Improved sharing UX (LinkedIn, X, copy link) with better encoding and feedback.

DX, architecture & reliability improvements

  • Introduced Zod for schema validation and safer data parsing.
  • Improved Prisma setup with singleton client, env validation, and schema tooling.
  • Upgraded Prisma and Node compatibility for improved stability.
  • Refined monorepo and app-level .gitignore for better project hygiene.
  • Improved CI environment consistency (Node version, DB env setup).

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.4.0Stable

Starter Pro foundation + billing engine groundwork

Mar 2026 (weekly release)
View roadmap

This release moves PyColors from PRO positioning into real premium product implementation work. It lays the technical and product foundation for Starter Pro with the first billing architecture, Prisma subscription schema, pricing surfaces, and stronger marketing, SEO, and trust messaging. Starter Pro is not publicly launched yet, but the premium system is now materially taking shape.

Starter Pro foundation in progress

  • Bootstrapped Starter Pro from the Starter Free base with dedicated branding, package metadata, navigation, sidebar copy, and proprietary licensing.
  • Prepared Starter Pro as a production-oriented SaaS app with dashboard, auth, settings, billing, and admin-ready product surfaces.
  • Added a dedicated pricing page with clearer offer structure, FAQ, guarantees, and improved upgrade entry points while the product remains in active development.

Billing engine groundwork

  • Introduced the first billing module architecture with centralized exports, typed billing plans, Stripe subscription status mapping, custom billing errors, and a service + repository foundation.
  • Added Stripe server integration, lazy client initialization, strict server-side environment validation, and example environment configuration.
  • Added API routes for checkout, billing portal access, plan changes, cancellation, resume, and Stripe webhook handling to establish the first billing workflow.

Prisma subscription data model

  • Added an initial Prisma billing schema covering users, customers, products, prices, subscriptions, invoices, and usage tracking.
  • Introduced Prisma tooling, scripts, singleton database client setup, and seed workflows to support development and future production billing logic.
  • Standardized Prisma commands with explicit schema paths and improved environment handling across development tasks.

Marketing, SEO, and trust improvements

  • Improved metadata, sitemap priorities, structured data, breadcrumb JSON-LD, and SEO-oriented navigation across marketing and docs pages.
  • Refined changelog, roadmap, footer, About, open-source, upgrade, access, waitlist, license, terms, and privacy messaging for clearer open-core and premium product direction.
  • Improved not-found UX, footer readability, docs layout structure, and MDX rendering for better documentation and ecosystem navigation.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.3.0Stable

SaaS knowledge layer + PRO funnel

Mar 2026 (weekly release)
Explore guides

This release turns PyColors.io into a much stronger SaaS learning and conversion surface. It ships a full Guides layer, adds Patterns, Examples, and Access pages, introduces PRO upgrade and waitlist flows, and refines navigation and ecosystem messaging to make the path from learning to upgrading much clearer.

Guides layer shipped

  • Added a dedicated Guides landing page to position PyColors as a SaaS knowledge base for builders.
  • Shipped structured SaaS guides covering Next.js product foundations, dashboard UX, authentication flows, billing UX, admin panel design, and team & organization systems.
  • Introduced a reusable guide page shell and an inline “On This Page” navigation component for clearer reading and stronger content consistency.

Product discovery & ecosystem navigation

  • Added new marketing pages for Patterns, Examples, and Access to clarify the PyColors ecosystem and guide users through learning, validation, and upgrade paths.
  • Updated primary navigation to better reflect the new content structure: UI, Patterns, Examples, Guides, and Starters.
  • Improved content discoverability and onboarding by making educational, product, and upgrade resources easier to browse.

PRO upgrade funnel

  • Added a dedicated Upgrade to PRO page outlining the product direction, roadmap logic, pricing structure, value proposition, and FAQ.
  • Added a PRO waitlist page with early interest capture and pricing visibility to support premium demand before launch.
  • Enhanced site header with clearer PRO upgrade CTAs and badges across desktop and mobile.

Messaging, positioning & conversion clarity

  • Refined Starter, upgrade, and ecosystem messaging to better distinguish product surface validation from production wiring.
  • Improved footer structure and brand context to reinforce PyColors as a structured SaaS ecosystem rather than a simple UI library.
  • Strengthened the progression logic across the site: Guides → Patterns / Examples → Starter Free → Starter PRO.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.2.2Stable

Trust foundation: Terms + Privacy

Feb 2026 (weekly release)
Read the license

This release completes the trust baseline required for commercial distribution. It adds Terms of Service and a Privacy Policy, updates the footer trust section, and clarifies how commercial templates like NA-AI relate to the broader PyColors licensing model.

Legal baseline shipped

  • Added /terms (Terms of Service) to define website, repository ecosystem, and digital product usage rules.
  • Added /privacy (Privacy Policy) covering minimal data collection, cookies and analytics direction, and third-party checkout handling.

Trust surface & navigation

  • Updated footer trust links to include Terms and Privacy.
  • Aligned trust copy so commercial template licensing remains clearer and more consistent across pages.

Commercial readiness (templates)

  • Reinforced the open-core → paid acceleration model: open foundations remain discoverable while premium templates stay properly licensed.
  • Keeps NA-AI positioning consistent with a commercial license included at purchase via Gumroad distribution.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.2.1Stable

Starter Free docs + marketing UX polish

Feb 2026 (weekly release)
Read Starter Free docs

This release hardens PyColors.io as a distribution and onboarding surface. It ships a full Starter Free documentation set, improves the UI and Starter positioning pages, and adds trust signals like npm badges while tightening accessibility and navigation across mobile and layout surfaces.

Starter Free documentation shipped

  • Added a comprehensive Starter Free docs set: philosophy, installation, project structure, deployment, upgrade path, and key concepts such as auth and billing.
  • Improved progressive adoption guidance to validate product screens first, then wire backend later.
  • Added SaaS Starter and release policy docs to collections for clearer onboarding and team conventions.

Marketing pages: clearer product positioning

  • Revamped Starter Free page with product-focused UX: clearer Free vs Pro comparison, CTAs, and a more actionable quickstart.
  • Redesigned UI page messaging around shipping outcomes instead of generic component lists, with richer structure and trust indicators.
  • Enhanced homepage with a dedicated UI section, improved starter links, and clearer CTA plus demo paths.
  • Refined About copy and added open-source links for better transparency and discoverability.

Trust surface: npm badges + safer external SVG support

  • Introduced a reusable npm badge component (version / downloads / license) to improve package visibility.
  • Enabled remote SVG badges from shields.io and updated CSP to support external images while keeping security constraints.
  • Switched multiple links to internal routing and surfaced docs paths across pages for stronger navigation consistency.

UX & accessibility polish

  • Improved mobile nav accessibility: focus first link on open, added skip-to-content, and reduced layout shift with scrollbar compensation.
  • Refined footer layout and external links hierarchy; streamlined badges and CTAs for readability.
  • Cleaned redundant in-code comments and removed unused code for a tighter, more maintainable marketing codebase.
  • Removed sidebar border and simplified positioning for a cleaner UI.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.2.0Stable

Ecosystem public launch: Tokens + ESLint + Release Engine

Feb 2026 (weekly release)
Explore ecosystem

This release marks a major ecosystem milestone: PyColors is now a more structured developer platform with public packages (UI, Tokens, ESLint) and a hardened weekly release engine. The positioning shifts from isolated components to shipping infrastructure.

New public packages

  • @pycolors/tokens published on npm: light / dark themes, semantic variables, and Tailwind v4 bridge.
  • @pycolors/eslint-config v1.0.0 released: base, Next.js, and React internal flat configs ready for ESLint v9.
  • Improved peer dependency clarity and ecosystem alignment across packages.

Release & distribution engine

  • Stabilized Changesets publish workflow.
  • Subtree sync strategy hardened (monorepo = source of truth, mirrors = distribution).
  • GitHub Releases automated for public packages.

Marketing alignment

  • Changelog and roadmap updated to reflect ecosystem positioning.
  • Clearer messaging: PyColors as a SaaS shipping platform (UI → Starter → Templates).
  • Weekly release cadence formalized as a trust-building mechanism.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.1.2Stable

Starter foundations + release engine

Feb 2026 (weekly release)
View roadmap

This release focuses on foundations for the upcoming SaaS Starter (Free) and strengthens the shipping engine: discoverability, trust surface, and consistent ecosystem messaging.

Starters (in progress)

  • Started the SaaS Starter (Free): laying down production-ready foundations such as structure, DX conventions, and UI baseline.
  • Prepared ecosystem cross-links (UI ↔ Starters ↔ Templates) to support a cohesive builder workflow.
  • Defined starter release conventions: what is shipped vs in progress to keep public updates honest and predictable.

Discoverability & trust

  • Search and analytics baseline: ensure key pages are trackable and indexable through events and metadata hygiene.
  • Improved messaging across metadata to reflect PyColors as an ecosystem, not only a UI kit.
  • Roadmap and changelog copy aligned with weekly release cadence and commercial readiness.

Release engine

  • Standardized weekly release structure: highlights blocks, CTA focus, and a clearer “what’s next” narrative.
  • Small UI / UX polish passes to reduce friction and improve perceived quality.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.1.1Stable

Patterns docs + SEO polish

Jan 2026 (weekly release)
Browse patterns

Docs expansion for production-grade UX patterns such as data tables, overlays, and async actions, plus SEO cleanup, favicon refresh, and type-level consistency refactors.

Docs & patterns

  • Introduced a new Patterns docs section: feature-level UI patterns with guidance on when to use them.
  • Added a comprehensive Data Table pattern doc: anatomy, states, and variations for SaaS and admin dashboards.
  • Shipped Data Table preview components: loading, empty, error, filterable, and row actions states.
  • Added an Overlays pattern guide (Dropdown vs Dialog vs Sheet) with interactive demos and accessibility rules.
  • Added Async Actions UX patterns: optimistic / pessimistic updates, feedback tiers, error handling, and interactive demos.
  • Refactored Toast docs and centralized preview exports via an index file.

SEO & metadata

  • Refined site metadata messaging to better position PyColors as a product ecosystem.
  • Simplified metadata configuration by removing redundant title / description where Open Graph acts as the source of truth.
  • Enhanced docs layout SEO with improved titles, descriptions, and canonical URL support.

Branding & UI polish

  • Updated favicon assets for stronger branding consistency.

Refactoring

  • Standardized component prop typing by migrating from interfaces to type aliases.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.1.0Stable

Advanced UI + product patterns

Jan 2026 (weekly release)
Browse components

Major expansion of PyColors UI with advanced components, practical product patterns, and a clearer ecosystem structure — a SaaS-ready foundation from core interactions to data UI.

New UI components

  • Password Input, Sheet, Dialog, Dropdown Menu, Tabs, Toast, Table, Skeleton, Empty State, Pagination.

Docs & product guides

  • New guides covering SaaS layout composition, async UI states, and accessible forms with validation.
  • Docs expanded beyond components to include real-world product patterns and UX guidance.

Marketing & ecosystem structure

  • Restructured marketing pages to better reflect the PyColors product ecosystem.
  • Introduced dedicated sections for UI and Starters to clarify positioning and future offerings.

Platform readiness

  • Added Radix dependencies for advanced interactions.
  • Improved discoverability through clearer information architecture and interactive previews.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.0.1Stable

Marketing & trust baseline

Jan 2026 (post-release)
View templates

Improves the marketing and trust surface: templates listing, NA-AI template page, narrative About page, and navigation plus accessibility polish.

Templates

  • Templates index page: listing of available templates with status and positioning.
  • NA-AI template landing: clearer value proposition, stack, and distribution links.

About page

  • New About page: design principles and direction of PyColors UI.
  • Docs-first philosophy and trust positioning for early adopters.

Navigation & UI polish

  • Navigation cleanup and accessibility improvements.
  • Quick start copy updated for clearer onboarding.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

v1.0.0Stable

UI Core Foundation

Release Week (Mon 5 → Fri 9 Jan 2026)
View roadmap

Official v1.0 launch of PyColors UI: core components, docs baseline, and release hygiene — a production-ready foundation.

UI Core Components

  • Button, Input, Badge, Card, Alert — consistent variants, sizing, and accessibility baseline.

Documentation Baseline

  • Every component ships with Preview / Usage / Code / Props.
  • Docs quality contract established for future releases.

Release Hygiene

  • Changelog page and Roadmap page shipped.
  • Semantic versioning introduced and version bumped to v1.0.0.

Strategy Weekly releases build trust. Even when the larger premium system is still evolving, we ship usable foundations, document what is real, and keep product direction visible through roadmap and offer pages.

Changelog entries reflect shipped work. Internal tasks, strategy changes, and in-progress commercial scope may be grouped, summarized, or represented more fully on the roadmap and offer pages.