Prepare your project.
Start with AI project, a template, blank source, Git, or ZIP.
Bring your existing source or start from a template. Refine the design, build the behavior, and review the result before publishing.
// Your store. Your source.
function CartSummary({ items }) {
const total = items.reduce(
(sum, item) =>
sum + item.price * item.quantity, 0
);
return <OrderSummary total={total} />;
}Start with AI project, a template, blank source, Git, or ZIP.
Review appearance and behavior, then continue in the same project.
Review services, resources, and hosting costs before confirmation.
You run Khaneh, a homeware store. Choose a stage to see the task, the workspace, and what to check.
Already on another platform? You need portable source or a compatible API; a website URL alone does not import the store.
Select New project in Projects. For this example, choose Template, then Online shop. Name the project, review its execution location, and select Prepare project. AI project, Blank, Git repository, and Upload ZIP are other starting points.
Our example is Khaneh, a homeware store. Each stage includes where to work, a sample request, and what to review.
Select New project in Projects. For this example, choose Template, then Online shop. Name the project, review its execution location, and select Prepare project. AI project, Blank, Git repository, and Upload ZIP are other starting points.
My homeware store is called Khaneh. I am starting with Online shop. Once prepared, inspect the home page, catalog, cart, and customer sign-in, then explain what is ready.
Before continuing: Check cloud capacity. If preparation stops, read the reason and keep the draft. For local execution, check Faiber Worker connectivity and compatibility.
Open the project IDE and choose an available model. Ask Plan to inspect the source and sequence the work. Plan is read-only; switch to Design or Code to implement changes.
Read the store source and propose steps for categories, cart, and catalog management. Do not change any files yet.
Before continuing: Identify the existing backend and payment provider before replacing an integration.
Use Design with Preview to request a specific change: olive colors, readable product cards, and a better mobile layout. Changes belong to your actual project files.
Style Khaneh with olive green and a warm light background. Include image, name, price, and an add button on each card. Check mobile and RTL layouts.
Before continuing: Are images, prices, and purchase controls readable and usable on mobile?
Ask Code to implement categories, adding products, quantities, and cart totals. Try the result with specific products in Preview.
Implement the cart. Adding the same item should increase quantity. Support removal, totals, an empty state, and clear errors.
Before continuing: Check totals, unavailable products, and server-side price validation.
Online shop includes sign-in, messaging, website data and forms, payments, and customer profile services. Configure and verify the Zarinpal gateway and SMS/OTP provider in Manage. Live payments and SMS sign-in need this setup first.
Inspect catalog and order data integration. Report the status and missing settings for Identity, Messenger, Profiles, and Payments. Keep secrets out of browser code.
Before continuing: The template uses Iranian rial (IRR) for checkout and receipts. If displaying toman, verify conversion and the amount sent to the gateway.
After provisioning, use Manage for products, categories, and stock. Review the schema and permissions before importing an existing catalog.
Review products by category and stock. List missing images or prices and show proposed bulk changes before applying them.
Before continuing: Distinguish sample and live data. Review price and stock changes before applying them.
Walk from the home page through cart and payment results. Run Lint and Build, then review errors, mobile layouts, and Git changes separately.
Check category selection, cart add/remove, empty cart, and payment failure. Run Lint and Build. Report actual results and remaining issues.
Before continuing: A successful Build is not a payment test. Test the gateway in its sandbox environment too.
Review resources, configuration, and the cost quote. After confirmation, follow Build, service status, and logs. A custom domain needs DNS configuration. Test checkout again on the final domain.
Show deployment settings, enabled services, and the cost estimate. Identify missing settings and DNS requirements. Start deployment after my confirmation.
Before continuing: Check the domain, HTTPS, and gateway callback. Continue future improvements in the same project.
From a button color to a product record, each task has its place. Explore three views of the same example store.
680,000 toman
Your request
“Make the photo larger and place the price beside the add button.”
Work in the browser, or use Faiber App for local folders and tools.