docs: clarify substrate extension types (markdown vs code)#25
Open
docs: clarify substrate extension types (markdown vs code)#25
Conversation
Add publishing module (v1.2.0): blog post template with required Visual Plan section, blog post instructions covering SEO/screenshots/publishing flow, and agent-write routing for blog content. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds the markdown-extension vs code-extension distinction to both PHILOSOPHY.md and extending-and-contributing.md. The substrate principle already said "if it requires code to run, it's not substrate." This makes that rule actionable: two named types, a comparison table, and clear install paths for each. Surfaces a boundary that trips up new users building integrations. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
1 participant
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
PHILOSOPHY.mdanddocs/extending-and-contributing.mdWhy
The substrate principle was clear on the rule but didn't name the two patterns that follow from it. New users building integrations frequently hit the question "where does this live?" — this gives them a framework to answer it before they build.
Surfaces naturally alongside "The Repo Stays Dumb" post publishing today.
Test plan
extending-and-contributing.mdnew section precedes the existing litmus test and doesn't contradict it🤖 Generated with Claude Code