17: Strip PHP from the remaining sections - #3397
Merged
Merged
Conversation
Deletes nine pages that exist only to document a PHP API or a code-level extension point: the catalog, price, product, Quable, segment and language API pages, the SiteAccess injection page, an orphaned snippet, and the Raptor CDP data customization page, whose subject is writing PHP field processors. Strips PHP from the pages that survive as feature documentation, removing the sections that existed only to tell the reader to write a class or open a PHP shell. The REST binary-attachment example becomes a description of the REST sequence rather than a PHP client script. Keeps the conceptual half of SiteAccess-aware configuration — the namespace/scope/parameter format and its inheritance rules, which the spec preserves — and cuts the bundle implementation that followed it. Clears residue R15 (an orphaned Extensibility section) and R18 (an instruction to restart the application). Removes 58 entries from the invariant baseline. Co-Authored-By: Claude Opus 5 (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
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.
Ticket 17 of the Cohesivo SaaS conversion. Base:
saas-batch-3.Scope note: the ticket estimated ~30 pages; 18 remained after tickets 07–13
deleted the rest.
37 files changed, 1,346 deletions, 19 insertions.
Nine pages deleted
Six
*_api.mdpages exist only to document a PHP API — catalog, price, product,Quable, segment and language. Three more are code-level extension points or
orphans:
injecting_siteaccess.md— injecting a PHP service into custom code.raptor_cdp_data_customization.md— its subject is writing PHP fieldprocessors; stripping the samples would leave prose listing PHP class names,
which is worth nothing to a tenant.
snippets/search_term_aggregation_settings.md— a PHP-only snippet, alreadyorphaned with zero includers after ticket 14.
Three of those were named in
cards()blocks, which callopen()directly andcrash the build rather than warning.
Pages stripped
Sections that existed only to tell the reader to write a class or open a PHP
shell are gone: the MCP capability class and server-list command, the REST
testing page's
## PHPsection, three Customer Portal "create a FormType / event subscriber" sections, custom-controller permissions, the custom
symbol attribute format, and the authentication listener.
rest_requests.mdwas handled differently. Its binary-attachment examplewas a PHP command-line script inside XML/JSON tabs — but it documented a real
REST capability. Rather than deleting the section, it now describes the REST
sequence itself: POST to create the draft, PUBLISH to publish it, authenticated
per the existing auth page. The knowledge survives; the PHP does not.
SiteAccess-aware configuration: kept, not deleted
This page is 90% PHP — bundle registration, a
Configurationclass, theContextualizer. But its opening half explains the<namespace>.<scope>.<parameter_name>format and what a scope is (SiteAccess,group,
default,global), which is exactly the SiteAccess concept the specsays to preserve, and four surviving pages link to it as the definition of
"SiteAccess-aware". So the concept stays and the implementation goes. It is a
candidate for ticket 18's review label.
configuration.md's pointer to it was reworded from "implement SiteAccess-awaresemantic configuration" to a statement about settings varying per SiteAccess.
Residue
### Extensibilitysection inai_actions_guide.md,invisible to link scans because ticket 11 had already removed its links.
restart the application, and the typo was pre-existing.
One more orphaned anchor
mcp_guide.mdadvertised "create custom server capabilities with PHP API"linking to a section this PR removes. The bullet is gone — the capability it
promised no longer exists for a tenant.
Verification
mkdocs build --strict→ exit 0.pytest -q→ 90 passed.administration/pages, which that PR clears.
🤖 Generated with Claude Code