Repository navigation
docs(adr): enjeu pages as a content type - #92
Merged
Merged
Conversation
Six enjeu pages become an `enjeu` content type with structured frontmatter, experts declared on team members, bow tie perimeter in content, and a website redeploy on merge.
Contributor
|
🔍 Preview: https://website-ddhfdupt5-ocobo-22231b32.vercel.app Built from website |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Records the decision to store the six enjeu pages of the website redesign as content in this repo, owned by their lead expert.
docs/adr/0002-enjeu-pages-as-content.md: new content typeenjeuwith structured frontmatter, Revenue AI as a sixth file, agent window demos and the partner block as content, bow tie stages in website code, experts declared on the Team member, ownership and review, and redeploy on merge.CONTEXT.md: adds the terms Enjeu, Stage and Milestone, and their relationships to Team member and Story.docs/rename-repo-plan.md: drops the GitButler wording, as the repo now runs on plain Git.Documentation only. No schema or content change: those come with the tickets of #91.
Related