Ownership, and Making This Template Your Own (Part 5)
Part 4 covered how this platform actually ships — scaffolding, CI/CD, and the two deployment shapes. This closing part is the two things every one of the last four parts has assumed: who actually owns each piece of this, and what it takes to make this whole template yours. Who owns what Every piece of this platform belongs to exactly one team, and that split is what makes independent deploys…
This final part of the platform template series revisits two key aspects: ownership and customization. Ownership is clearly defined - each component belongs to a single team. The Store, Components, manifest, and identity provider are owned by the Platform team, while the MFEs each own their respective components. The identity provider and domain are owned by the MFE team. This clear ownership structure is crucial for independent deploys.
Customization is equally important. The template is designed to be easily forked and adapted. A new organization would simply fork the GitHub template repository, modify the platform.config.json file to include their specific branding, identity provider details, and manifest URL, and then point the DNS and CDN to their own infrastructure.
This straightforward process ensures the fork remains upgradeable from the original template, avoiding drift into incompatible territories. The versioned contracts between components and the manifest schema serve as the seam for these upstream changes, allowing for seamless integration without breaking existing domain team builds.
In summary, this series establishes a clear ownership model for platform components, making the deployment process tractable even with multiple domain teams. It also provides a simple, effective method for organizations to customize and fork the template to suit their specific needs.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
