Hi team,
We've been exploring satus as a foundation for content-driven sites at our org and really like the architecture — clean App Router patterns, the Lenis integration, and the overall component structure.
We're interested in contributing back, specifically around GSAP and Three.js integration:
- Animation primitives or helpers that build on your existing Lenis/GSAP setup
- Three.js components or patterns for WebGL sections (backgrounds, transitions, interactive elements)
- Supporting demos or examples showcasing these integrations
Since there's no CONTRIBUTING.md yet, a few questions before we start:
- Are you open to external contributions? We understand satus is a studio starter, so we want to gauge whether outside PRs are welcome or if this is primarily an internal tool.
- Preferred contribution areas? Would you value docs, tests, demos, or new components most? We'd rather align with your priorities.
- Any conventions we should follow? We noticed the PR template and the existing code style — anything else we should know about branch naming, commit format, or review expectations?
Happy to start small (docs, tests, or a focused demo) and build from there. Thanks for making this available under MIT — it's a solid foundation.
Hi team,
We've been exploring satus as a foundation for content-driven sites at our org and really like the architecture — clean App Router patterns, the Lenis integration, and the overall component structure.
We're interested in contributing back, specifically around GSAP and Three.js integration:
Since there's no
CONTRIBUTING.mdyet, a few questions before we start:Happy to start small (docs, tests, or a focused demo) and build from there. Thanks for making this available under MIT — it's a solid foundation.