refactor: remove marko/blog package from framework#21
Merged
Conversation
The blog is an application-level implementation, not framework infrastructure. Removed the package and all references across the codebase including docs, plans, tests, and composer.json. - Deleted packages/blog/ entirely - Removed from root composer.json (require, repository, autoload-dev) - Updated package count tests (72 → 71) - Removed blog-specific plan files and dev notes - Rewrote build-a-blog tutorial to build from scratch using framework primitives - Updated docs (events, plugins, preferences, modularity, routing) to use App\Blog or Acme\Blog namespaces instead of Marko\Blog - Updated test fixtures to use acme/blog instead of marko/blog Co-Authored-By: Claude Opus 4.6 (1M context) <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
marko/blogpackage — it's application-level code, not framework infrastructureApp\BlogorAcme\BlognamespacesTest plan
Marko\Blogormarko/blogreferences in active code/docs (only old completed plan files)App\BlogvsAcme\Blogused consistently (app code vs vendor package)🤖 Generated with Claude Code