Developer Onboarding
This onboarding guide gives you a clear panoramic view of the product so you can quickly understand how the system works, what matters most, and where your work will have impact.
Direct production links
- Product app: app.visyble.ai
- Backend API base: api.visyble.ai
- OpenAPI JSON: api.visyble.ai/openapi.json
- Frontend Main Sections: docs.visyble.ai/generated/frontend-main-sections
- Flow Explorer: docs.visyble.ai/flow-explorer
- Frontend API Usage Reference: docs.visyble.ai/generated/frontend-api-usage-reference
- API Endpoint Details: docs.visyble.ai/generated/api-endpoint-details
- Backend API Explained: docs.visyble.ai/generated/backend-api-explained
What this product is
The platform helps teams understand and improve their visibility in AI-driven search experiences. It combines product analytics, operational workflows, and recommendations into one system that supports both strategic decisions and daily execution.
At a high level, the platform has four major perspectives:
- Frontend product experience, where teams explore insights and take action.
- Backend intelligence and APIs, where data is processed, normalized, and served.
- Competitive intelligence, where gaps and opportunities are tracked against market expectations.
- Feature and execution coverage, where capabilities are mapped to business outcomes.
How to mentally model the platform
Think about the platform as a loop:
- Data is collected and processed.
- Insights are generated and organized into product sections.
- Teams review dashboards and operational views.
- Teams execute changes through actions, content work, settings, and planning.
- New data confirms impact and starts the cycle again.
This loop is important for onboarding because each developer contribution usually improves one part of that cycle. Good onboarding means understanding where your change sits in this loop before implementation starts.
What new developers should focus on first
Your first priority is understanding product intent before implementation details. Start by learning:
- Which product sections are considered core for users.
- How frontend sections connect to backend capabilities.
- Which backend domains power high-impact user workflows.
- Where operational reliability affects user trust and decision-making.
When this context is clear, code-level decisions become easier and cleaner.
Practical onboarding goals for week one
By the end of your first week, you should be able to:
- Explain the purpose of each major frontend area in plain language.
- Describe the backend domains that support those areas.
- Trace one complete user journey from interface to backend behavior and back to visible outcome.
- Identify which APIs are critical, which are supporting, and which are currently underused.
- Understand how reliability and operations influence product quality.
How to use the onboarding section
This onboarding area is intentionally split into focused pages so each one answers a specific question:
- Frontend orientation explains what users see and how product areas are organized.
- Backend orientation explains what services do and why each API group exists.
- Backend operations explains production reliability, execution safety, and response priorities.
Read these pages in order, then move to frontend and backend documentation sections for deeper detail.
Onboarding mindset
The most successful onboarding approach here is:
- Learn the product story first.
- Understand the architecture second.
- Implement changes third.
- Verify user impact continuously.
This sequence avoids local optimizations and helps you make contributions that align with the real product goals from day one.