34 lines
1018 B
Markdown
34 lines
1018 B
Markdown
---
|
|
trigger: always_on
|
|
---
|
|
|
|
# Technical Architecture Guidelines
|
|
|
|
This rule outlines important architectural considerations for this project.
|
|
|
|
## Technical Implementation
|
|
|
|
- Astro.js + React + Tailwind
|
|
- Framer Motion + GSAP
|
|
- Auth and Payment with Clerk
|
|
- Strapi as CMS
|
|
- Deployment with Docker Compose configured for Coolify
|
|
- Newsletter with Listmonk
|
|
|
|
## Notes for Astro.js
|
|
|
|
- use Island Architecture smartly to optimize for performance
|
|
- use server islands if appropiate
|
|
|
|
## Notes for Framer Motion + GSAP
|
|
|
|
- for more complex use GSAP, otherwise Framer Motion, search online for inspiration if none was given to you
|
|
|
|
## Notes for Strapi
|
|
|
|
- Strapi should be used as the CMS
|
|
- Portfolio Sites should easily be added to the CMS and displayed in the frontend (think if this makes sense and give feedback if any other solution would be more viable)
|
|
|
|
## Auth with Clerk
|
|
|
|
- Clerk was not used for any projects so far but it should be used for a payment plattform on this website as well as user authentication for clients. |