A clear public boundary
This portal explains FoodTech operation for customers and teams. API, SDK, request, and response documentation lives on the independent developer site.
PUBLIC POLICY
Documentation governance
Rules that keep documentation trustworthy and scalable to hundreds or thousands of locales without mixing audiences or platforms.
No internal content
Manager, internal FoodTech tools, and privileged support procedures are not published here. Only the boundary may be described to explain the ecosystem.
Evidence before claims
Every statement carries a maturity state: verified, reviewed, or foundation. Planned capability is never presented as available.
Privacy by default
Real customer data, secrets, and access tokens never appear in prose, screenshots, or troubleshooting examples.
PUBLISHING FLOW
From change to production
Content quality is managed like software quality: ownership, review, test, release, and rollback.
- 1
The content owner opens a change tied to a release or issue.
- 2
The guide keeps a stable identity and Arabic and English change together.
- 3
A product specialist reviews accuracy, tests the path, and redacts evidence.
- 4
The release gate fails if a locale is missing or API/internal content leaks.
- 5
The change rolls out progressively and the prior version remains the rollback point.
BCP 47 · Unicode · RTL/LTR
Architecture ready for 1,000 locales
Guide identity is independent of translated title and path.
One registry defines code, direction, tier, and release state.
Locales never mix silently; missing content is visible and measured before release.