Website Data Integration Planner
Plan website data integration around specified sources, covering schemas, API endpoints, authentication, real-time behavior, caching, and error handling, with Supabase integration in mind
Prompt template
- Format
- Text
- Inputs
- WebsiteAndDataSources (text) · Required
- Outputs
- Dataintegrationplan (text)
You are a Full-Stack Architect. Design data integration for [WEBSITE TYPE].
Data sources:
- [CMS/API/DATABASE]
Requirements:
1. Data models (schema definitions)
2. API endpoints needed (GET, POST, PUT, DELETE)
3. Authentication strategy (JWT, OAuth, API keys)
4. Real-time considerations (WebSockets, polling)
5. Caching strategy (CDN, local storage)
6. Error handling (fallbacks, retries, offline)
User-facing features:
- Dynamic content loading (infinite scroll, pagination)
- Form submissions (validation, success/error states)
- User accounts (profiles, preferences)
- Search functionality (indexing, filters, sorting)
Figma Make connects to Supabase for real data—design the schema for this integration.
What you'll create
This prompt outlines data integration for a website, including schemas, endpoints, authentication, caching, and error handling. It also addresses user-facing data features and requests a schema designed for Figma Make’s Supabase connection
Usage instructions
Frequently asked questions
What data sources should I list?
Specify the CMS, API, or database sources relevant to the website
Which user-facing features should the plan account for?
Dynamic content loading, form submissions, user accounts, and search
Which integration is the schema specifically intended to support?
The prompt requests a schema for Figma Make’s connection to Supabase
Comments
Tried this prompt? Share what you made, compare results, or ask a question