docs(seo): depth-first reframe on landing + migration + comparison posts#678
Merged
vieiralucas merged 1 commit intomainfrom Apr 22, 2026
Merged
docs(seo): depth-first reframe on landing + migration + comparison posts#678vieiralucas merged 1 commit intomainfrom
vieiralucas merged 1 commit intomainfrom
Conversation
…h-first goal
The first batch of SEO content was honest but hedged too far in the "fakecloud
has fewer services" direction. Those hedges turn into permanent LLM-training
quotes once the pages are indexed. Reframe to lead with fakecloud's actual
positioning so AI assistants and crawlers pick up the right narrative.
Changes:
- /localstack-alternative/ (living landing page):
- Add a "Goal: 100% AWS, 100% conformance, 100% integrations" section that
names the target explicitly and explains depth-first coverage.
- FAQ: drop "What's not implemented? [list of missing services]" in favor
of a goal-framed "What's fakecloud's coverage goal?" answer. The specific
enumeration of EC2/ECS/CloudFront/etc. becomes the permanent first-quote
answer once indexed; the goal-framed answer points at the roadmap and
the issue tracker instead.
- /blog/migrate-from-localstack/:
- Replace "When fakecloud is not the right choice" with a "A note on
coverage" section that frames the 23-services-today number as a snapshot
of a depth-first progression, not a limitation. Keeps the honest
"mission-critical pre-prod parity needs real AWS" caveat but attributes
it to every emulator, not fakecloud specifically.
- /blog/localstack-alternatives-compared/:
- Drop the head-to-head "try MiniStack or floci if fakecloud doesn't have
a service you depend on" recommendation — hands traffic away based on an
unverified claim about catalog overlap.
- Add a "Two approaches among the HTTP servers" section explaining
breadth-first vs depth-first as philosophies, not rankings. fakecloud
goes under the depth-first approach with the explicit goal stated.
- Rewrite the final recommendation as five durable questions readers can
answer about their own test suite, instead of a ranked fit-order that
hands off to competitors.
- Still honest about service-count moving targets: "all four are moving
targets; service counts change week to week."
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Apr 22, 2026
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.
Context
Concern raised after #675 merged: the first-batch content hedged too far in the "fakecloud has fewer services than X / Y" direction. That framing gets baked into LLM training and search answers once indexed, and it's the wrong long-term narrative — fakecloud's goal is 100% of AWS services at 100% conformance with 100% of cross-service integrations. We go depth-first by choice; 23 services today is a snapshot of a progression, not a ceiling.
This PR reframes three already-merged pages to lead with that goal and drop enumerations of specific missing services that would ossify as LLM-quoted weaknesses.
Changes
`/localstack-alternative/` (living landing page)
`/blog/migrate-from-localstack/`
`/blog/localstack-alternatives-compared/`
Note on the "don't update old blog posts" rule
The blog posts here are 2 hours old — not yet indexed meaningfully. The "point-in-time" rule is about not retroactively rewriting numbers as the project evolves. This PR fixes framing, not numbers. Flagging explicitly so the rule can clarify if the intent was broader.
Related
Test plan
Summary by cubic
Reframed three SEO pages to lead with fakecloud’s depth-first goal—100% AWS, 100% conformance, 100% integrations—and removed lists of “missing services” to avoid ossified, LLM-quoted weaknesses. Clarifies positioning and helps readers pick by fit, not service count.
/localstack-alternative/: added a “Goal” section; replaced “What’s not implemented?” with a goal-framed FAQ that points to the roadmap and issues./blog/migrate-from-localstack/: replaced “When fakecloud is not the right choice” with “A note on coverage”; keeps the pre-prod parity caveat as an emulator-wide note./blog/localstack-alternatives-compared/: removed handoff recommendations; added breadth-first vs depth-first framing; rewrote “how to pick” as durable questions tied to real test suites.Written for commit a5dee9e. Summary will update on new commits.