About Atlas Wiki

The KFC Atlas Wiki is the self-serve home for understanding how the platform works, how to operate it, and how KFC teams can confidently use it across markets.

It brings together product context, operating guidance, and campaign playbooks in one place so users do not have to depend on ad hoc explanations, scattered documents, or direct hand-holding every time they need an answer.

What Is Atlas Wiki

Atlas Wiki is a structured documentation experience for the KFC Atlas platform.

It is designed to help teams:

• understand what the platform does
• learn how to operate the Byte Commerce Admin Portal
• find step-by-step guidance for real operational tasks
• reference market-specific behaviors and feature configurations
• execute repeatable workflows through practical playbooks

In short, it is meant to make platform knowledge easier to discover, easier to trust, and easier to use.

Who Created Atlas Wiki

Atlas Wiki was created by Justin Pagalilauan.

This page exists to acknowledge the ownership and intentionality behind the work. Atlas Wiki was not assembled as a generic document repository. It was built deliberately to support adoption, enablement, and day-to-day platform confidence for KFC teams.

If you want the team context behind the work, see Brand Experience Team.

Why We Are Building It

The main reason for building Atlas Wiki is self-serve enablement.

As the platform grows, teams need a faster and more reliable way to answer questions such as:

• What does this feature do?
• Which guide should I follow?
• How do I configure this in the admin portal?
• What is market-specific versus globally shared?
• What should I do before launching a campaign?

Without a central knowledge layer, those answers get repeated in meetings, chat threads, and one-off walkthroughs. That slows teams down and makes knowledge harder to scale.

Atlas Wiki helps solve that by creating a single reference point that is:

• searchable
• structured
• role-aware
• reusable across teams
• available on demand

Who It Aims To Cater To

Atlas Wiki is built for the people who need to understand, operate, support, and scale the platform.

That includes:

• Restaurant teams who need operational guidance
• Market and regional teams who manage rollout, setup, and execution
• Enablement and support teams who need consistent answers and references
• Marketing and campaign operators who need practical playbooks
• New team members who need onboarding context without relying only on live training
• Cross-functional stakeholders who need a clearer view of what the platform actually supports

What Atlas Wiki Aims To Do

Atlas Wiki aims to:

• reduce dependency on one-to-one support for common platform questions
• give teams a self-serve path to find the right article quickly
• create shared understanding across markets
• make documentation easier to maintain and easier to search
• support both operational execution and product understanding
• improve onboarding for new users and new markets
• strengthen consistency in how platform knowledge is communicated

Core Features

Atlas Wiki currently includes:

• Front-end Guide for customer-facing platform behaviors and market configurations
• Admin Portal Guide for operating the Byte Commerce Admin Portal
• Playbooks for execution workflows such as promotions and lifecycle campaigns
• English-first support so the active market audience has one maintained source of truth
• Search across titles, headings, and article content to help users find the right guide faster
• Structured navigation to make complex documentation easier to browse
• Localized documentation experiences that preserve route structure by language

Design Principles

Atlas Wiki is being built around a few simple principles:

• Self-serve first: users should be able to answer common questions independently
• Operationally useful: content should help people do real work, not just describe concepts
• Easy to navigate: people should be able to browse by area or search directly
• Scalable: the documentation model should grow with more markets, guides, and translations
• Credible: the content should feel curated, intentional, and relevant to KFC operations

Long-Term Role

Over time, Atlas Wiki can become more than a documentation hub.

It can serve as:

• an enablement foundation for new markets
• a reference point for support and training
• a source of truth for platform workflows
• a launchpad for better AI-assisted discovery in the future

In One Sentence

The KFC Atlas Wiki exists to make platform knowledge findable, usable, and scalable for the teams who operate it.