System Architecture Overview
This document provides a high-level, interactive overview of the Yipi platform's architecture. Use the navigation or click the diagram elements to explore how the system works.
Interactive Visual Architecture
Click on any component box to jump to its detailed explanation.
Component Deep Dive
Select a component to learn more about its role and how it functions within the platform.
1. The "Storefront": Frontend (Vue.js + Nuxt.js)
What it is: This is the public-facing website that your customers and vendors see and interact with.
How it works: Think of this as the shiny, modern showroom. It’s built to be very fast and responsive. It doesn't actually *store* any data (like product info or user accounts). Instead, it "requests" data from the "Back Office" (the Backend) through a secure, private door (the API).
Summary of Data Flow
This is the typical journey of data from the user to the system and back.
A User visits the Frontend (website).
The Frontend requests data by securely "talking" to the Secure API.
The API "asks" the WordPress Backend for that data.
WordPress (using its plugins) finds or saves the data in the Database (MySQL).
If needed, WordPress uses the Stripe plugin for payments or the Tastemaker plugins to sync with CreativeWorks.