ktd knowledge gateway
I turned a Confluence-based playbook into a personalized knowledge platform for thousands of KTD associates.

the problem
The KTD Playbook had grown into an important source of knowledge for Kroger Technology & Digital, but technically it was still a Confluence-based experience delivered through a plugin.
It worked for publishing information, but it limited how far we could take personalization, search, integrations, role-based experiences, and the overall product experience.
The bigger problem was that KTD knowledge did not live in one system. Associates had to know where to look across documentation, learning platforms, internal tools, team resources, and other systems before they could even start finding an answer.
The idea behind the Knowledge Gateway was to stop treating knowledge as a collection of pages and create an actual front door to KTD.
my role
I became the sole developer and technical owner of the Knowledge Gateway.
I was responsible for taking the application from the early concept through architecture, development, authentication, infrastructure, testing, deployment, launch, and continued iteration.
I worked closely with Knowledge Management, design, infrastructure, identity, security, and platform teams, but owned the technical side of turning those requirements into a production application.
I built the Gateway with Next.js and TinaCMS, with the application and content separated so that non-developers could manage knowledge without changing application code.
That meant the work was never just building the website. I was building the infrastructure, development workflows, integrations, authentication, and systems around it too.
from playbook to product
Moving away from the original Confluence-based Playbook gave me room to build experiences specifically around how KTD associates discover and use knowledge.
The Gateway grew to include:
- personalized and role-based content
- Role Essentials and learning journeys
- a searchable resource hub
- blogs and KTD events
- learning resources
- dark mode and personalization
- dashboards
- intake requests
- administrative experiences
One of the most important architectural decisions was separating the application from its content.
TinaCMS gave content owners a way to manage knowledge without requiring every change to become a development task, while Git still provided versioning and structure behind the scenes.
The Gateway could now evolve like a product instead of behaving like a collection of Confluence pages.
the experience
One of my favorite parts of the Gateway is how much complexity sits behind what is ultimately a pretty simple experience for an associate.
A user signs in and the Gateway can understand their access and role, personalize what they see, and give them a single starting point for finding resources, learning, events, tools, and knowledge across KTD.
The goal was not to make people understand where knowledge was stored.
It was to let them find what they needed without having to think about where it came from.
shipping it
Getting the Gateway into production became its own engineering problem.
The application needed separate environments, secure authentication, role-aware authorization, content infrastructure, Azure resources, deployment workflows, secrets management, and a process for safely moving changes from development to stage and production.
The Knowledge Gateway officially launched in January 2026.
But I never treated launch as the finish line.
After launch, I continued shipping features, fixing problems, reworking architecture, and establishing a more repeatable release process. Changes could move through Stage for testing across Associate, Manager, and Contractor experiences before reaching Production.
That allowed me to keep moving quickly without treating production as the test environment.
key decisions
-
Build a standalone application instead of extending the Confluence plugin: This meant taking on more responsibility around hosting, authentication, deployment, security, and maintenance, but removed the ceiling on what the Gateway could become.
-
Separate content from application code: Using TinaCMS with a dedicated content repository let Knowledge Management manage content without requiring every update to be a development task. The tradeoff was a more complicated architecture and deployment model that I had to build and maintain.
-
Make identity part of the product: Associates, contractors, managers, and administrators do not always need the same experience. I built authentication and authorization around those differences so the application could personalize experiences while protecting restricted content.
-
Iterate instead of waiting for a "finished" platform: I shipped a useful core and continued improving it through regular releases. Feedback could influence the product early, while Stage testing helped keep that iteration safe.
-
Treat integrations as the future of the platform: Instead of manually recreating information inside the Gateway, I started connecting it directly to the enterprise systems that already own that data.
beyond the launch
Once the core platform was stable, my focus started shifting from "how do I build the Gateway?" to "what can the Gateway connect?"
I began integrating systems that previously existed completely outside the experience.
Coursera and Pluralsight data could make learning progress part of the Gateway.
UpRaise could surface company objectives without making associates jump into another platform.
ServiceNow opened the door to bringing KTD topology and business-capability data directly into the experience.
Microsoft Graph enabled the Gateway itself to begin communicating with users through workflows such as blog notifications and automated page-audit reminders.
A lot of the work behind those integrations was invisible in the UI.
I worked through service accounts, API access, SPM changes, application permissions, identity configuration, firewall rules, and coordination with security and platform teams to make those connections possible.
connecting the gateway to AI
Another part of that evolution has been figuring out how the Gateway can become a knowledge source for the tools associates already use.
I have been working through the networking, authentication, service-account, firewall, and Akamai requirements needed for platforms such as Microsoft 365 Copilot and Atlassian Rovo to securely access Gateway content without exposing the application publicly.
That changes what the Gateway can be.
Instead of only being somewhere an associate has to visit, its curated knowledge can begin meeting people inside other tools and AI experiences.
building 2.0
That is the direction I am taking with Knowledge Gateway 2.0.
The first version proved that we could create a better front door to KTD knowledge. 2.0 is about making that platform cleaner internally and more connected externally.
I am continuing to simplify the architecture, improve the content model, strengthen feature boundaries, and remove technical decisions that made sense during the initial rapid build but no longer make sense for a platform intended to keep growing.
At the same time, I am continuing to push the Gateway toward deeper enterprise integrations and AI discoverability.
The goal is no longer simply to replace the KTD Playbook.
It is to build a knowledge layer for KTD that can connect people, content, enterprise systems, and AI through one platform.
outcome
The Knowledge Gateway shipped as the internal home for KTD associates — one place to search, learn, discover tools, understand what teams own, and keep up with what is happening across the organization.
What started as an evolution of a Confluence-based Playbook became a production platform that I have continued to own technically through launch, rapid iteration, new features, enterprise integrations, and now its next generation.
- 3,262
- total internal users
This is fantastic to see the work you have been doing, especially while still attending your college courses. That is quite the feat, and you should be really proud of yourself. Seriously, juggling school and crushing it at work is no small accomplishment. The site is awesome!