fteg-cms-dev fteg-cms-ichiwa-dev do not edit web-ichiwa-dev

FTEG CMS Product Plan

Single plan for the CMS product: architecture, implementation steps, sprint timeline, and Ichiwa tenant (first restaurant clone). Keep /srv/www/web-ichiwa-dev read-only.

Commercial policy — 1 site = 1 subscription

Policy also documented in Platform Architecture and /srv/www/hubs/GROUP-ARCHITECTURE.md (CMS section).

Overview

Architecture — template vs CMS vs modules

Same rule as PropFlex: structure in code; marketing copy in package-cms; transactional data in host modules or optional packages.

Reservation reference: makiisushi.com/reservation (Makii-style flow — date → session → courses → T&C → deposit; now Fiuu on product API).

Contents

1. 1 site = 1 sub
2. Overview
3. Architecture
4. Deploy model
5. How to start — scaffold
6. Wire packages + Site Content
7. Clone Ichiwa tenant
8. Port Ichiwa template
9. CMS vs restaurant modules
10. Reservation (optional package)
11. Sprint timeframe
12. Checklist

1. Deploy model

 /srv/www/fteg-products/
 ├── ROADMAP.md
 ├── fteg-cms-dev/
 │   └── docs/
 │       ├── README.md
 │       └── fteg-cms-plan.html   ← this file (canonical)
 └── fteg-cms-ichiwa-dev/         ← tenant clone (create)

 /srv/www/web-ichiwa-dev/         ← DO NOT CHANGE (reference only)
 /srv/www/package-cms/            ← Site Content BO
 /srv/www/package-admin-core/
 /srv/www/package-admin-ui/
 /srv/www/package-seo/
 /srv/www/package-reservation/    ← engine (consumed by fteg-reservation product)
 /srv/www/fteg-products/reservation/  ← standalone product (live — G0–G3 + B6)

2. Prerequisites

• PHP 8.2 + Composer + nginx + php-fpm (same stack as PropFlex / fame-proplist)
• MySQL/MariaDB database(s) for each app
• Local path packages available under /srv/www/package-*
• Reference apps: propflex or fame-proplist for CMS wiring

How to start — scaffold fteg-cms-dev

1. Create the Laravel host (prefer copying a known FTEG bo-starter / PropFlex-lite shell if you have one; otherwise fresh Laravel + packages).
2. Place it at /srv/www/fteg-products/fteg-cms-dev.
3. Create DB + .env (APP_NAME=FTEG CMS, unique APP_KEY, DB credentials).

# Example skeleton (adjust if you use an internal bo-starter)
cd /srv/www/fteg-products
# Prefer: copy from an approved FTEG CMS host skeleton when available.
# Fallback:
composer create-project laravel/laravel fteg-cms-dev
cd fteg-cms-dev
cp .env.example .env
php artisan key:generate

4. Step 2 — Wire packages + Site Content

In fteg-cms-dev/composer.json add path repos (adjust relative paths):

{
  "repositories": [
    { "type": "path", "url": "../../package-cms", "options": { "symlink": true } },
    { "type": "path", "url": "../../package-admin-core", "options": { "symlink": true } },
    { "type": "path", "url": "../../package-admin-ui", "options": { "symlink": true } },
    { "type": "path", "url": "../../package-seo", "options": { "symlink": true } }
  ],
  "require": {
    "fdev2024/package-cms": "@dev",
    "fdev2024/package-admin-core": "@dev",
    "fdev2024/package-admin-ui": "@dev",
    "fdev2024/package-seo": "@dev"
  }
}

composer update fdev2024/package-cms fdev2024/package-admin-core fdev2024/package-admin-ui fdev2024/package-seo
php artisan vendor:publish --tag=cms-config
php artisan migrate

First CMS templates (default product)

php artisan cms:make-template Home --type=site --key=home
php artisan cms:make-template Contact --type=site --key=contact
php artisan cms:make-template Footer --type=site --key=footer

# Register each in config/cms.php, then:
php artisan cms:sync-elements home
php artisan cms:seed-page home
# …repeat for contact, footer

Public Blade uses CMS helpers (same as PropFlex):

@php($page = cms_page('home'))
<x-cms::text :page="$page" key="hero.title" tag="h1" />
<x-cms::image :page="$page" key="hero.background" />

{{-- with config fallback while migrating --}}
{{ cms('contact', 'intro.title', config('site.contact.intro.title')) }}

BO: Site Content should appear under admin (package-cms routes, typically /site-content) once admin-core is wired.

5. Step 3 — Clone Ichiwa tenant

1. Copy the default app to the tenant path.
2. Give it its own DB + .env + APP_KEY.
3. Keep package versions in sync with default (same path repos).

cd /srv/www/fteg-products
cp -a fteg-cms-dev fteg-cms-ichiwa-dev
cd fteg-cms-ichiwa-dev

# New env / DB
cp .env.example .env   # or edit existing .env
# APP_NAME=Ichiwa CMS
# APP_URL=https://ichiwa-….fteg.dev
# DB_DATABASE=fteg_cms_ichiwa_dev
php artisan key:generate
php artisan migrate
php artisan cms:sync-elements   # after templates registered
php artisan cms:seed-page home
php artisan cms:seed-page contact
php artisan cms:seed-page footer

6. Step 4 — Port Ichiwa template (copy only)

From /srv/www/web-ichiwa-dev, copy into the tenant — do not edit the source tree.

# COPY only — never write back into web-ichiwa-dev
SRC=/srv/www/web-ichiwa-dev
DST=/srv/www/fteg-products/fteg-cms-ichiwa-dev

mkdir -p "$DST/public/assets" "$DST/resources/views/web"
cp -a "$SRC/assets/." "$DST/public/assets/"
# Then manually convert each HTML → Blade layout + sections
# index.html → resources/views/web/home.blade.php
# menu.html  → resources/views/web/menu.blade.php
# …

Suggested Blade map

7. Step 5 — CMS fields vs restaurant modules

Build order inside the Ichiwa tenant:

1. P0 — Layout + home/contact/footer on CMS (hardcoded menu/events OK temporarily).
2. P1 — Menu / Omakase / Event CRUD in BO; public pages read DB.
3. P2 — Reservation lead capture (store request + notify WhatsApp/email).
4. P3 — Real availability + admin calendar.
5. P4 — Fiuu guest deposit (G3 done on product API), confirmation email.

8. Step 6 — Reservation (fteg-reservation product)

Reservation is a standalone FTEG product — not installed inside CMS. Ichiwa calls the product API with a venue key (G2 done).

• reservation.js in tenant public assets → remote API + X-Api-Key
• Bookings / capacity / deposits live in fteg-reservation
• BO for bookings/sessions/settings/wallet lives in reservation product — not CMS
• Subscribe + billing via fteg-erp (RM59/mo Fiuu) — Track B6 done
• Guest deposit via Fiuu + venue wallet contra — Track G3 done

Full product plan: fteg-reservation-plan.html

9. Nginx + local check

Example vhosts (create when apps exist):

# /etc/nginx/conf.d/fteg-cms-dev.conf
server {
  listen 80;
  server_name cms-32829402.fteg.dev;
  root /srv/www/fteg-products/fteg-cms-dev/public;
  index index.php;
  access_log /srv/www/logs/fteg-cms-dev-access.log;
  error_log  /srv/www/logs/fteg-cms-dev-error.log;

  location / { try_files $uri $uri/ /index.php?$query_string; }
  location ~ \.php$ {
    try_files $uri =404;
    fastcgi_pass unix:/run/php-fpm/www.sock;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    include fastcgi_params;
  }
}

# /etc/nginx/conf.d/fteg-cms-ichiwa-dev.conf
# server_name ichiwa-38902193.fteg.dev;  # can point here later
# root /srv/www/fteg-products/fteg-cms-ichiwa-dev/public;

10. Sprint timeframe (8-week plan)

CMS development is part of sprint Track E (Dev 4). Reservation Track G + B6 are done (product API + Fiuu).

Milestones: S4b Aug 8 (CMS shell + Ichiwa on BO) · S5 Sep 5 (corporate CMS sites live).

11. Done-when checklist

mkdir -p /srv/www/fteg-products
# then scaffold fteg-cms-dev (bo-starter or Laravel + packages)
# then: cp -a fteg-cms-dev fteg-cms-ichiwa-dev