docs(seo): FAQ page with FAQPage JSON-LD schema

[vieiralucas]

Batch 4C. New /faq/ page with 21 Q&A entries covering install, licensing, services, LocalStack migration, Lambda execution, RDS/ElastiCache real engines, CI, Docker, correctness validation, AI-coding-tool usage, competitor comparisons.

Why it matters: the embedded FAQPage JSON-LD block makes Google render the FAQ as expandable rich snippets directly in SERPs — question drops down, answer visible without clicking through. High-conversion SERP real estate per ranked impression.

Validates on https://search.google.com/test/rich-results once deployed. Each Q&A in the markdown matches a Question entry in the schema so the visible content and structured data agree (Google penalizes mismatches).

---

Summary by cubic

Adds a new /faq/ page with 21 Q&A entries. Embeds an FAQPage JSON-LD block so Google can show expandable FAQ rich results, improving SERP visibility and CTR.

• New Features
  • Adds website/content/faq.md covering install, licensing, supported services, LocalStack migration, Lambda, RDS/ElastiCache, CI, Docker, correctness, tooling, and comparisons.
  • JSON-LD mirrors the on-page Q&A to avoid mismatch penalties and validates in Google Rich Results Test after deploy.

^{Written for commit e98e749. Summary will update on new commits.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[cubic-dev-ai]

2 issues found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="website/content/faq.md">

<violation number="1" location="website/content/faq.md:35">
P3: This link points to a non-existent page. Link to the existing RDS docs instead.</violation>

<violation number="2" location="website/content/faq.md:39">
P3: This link points to a non-existent page. Link to the existing ElastiCache docs instead.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

P3: This link points to a non-existent page. Link to the existing ElastiCache docs instead.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At website/content/faq.md, line 39:

<comment>This link points to a non-existent page. Link to the existing ElastiCache docs instead.</comment>

<file context>
@@ -0,0 +1,133 @@
+
+### Does fakecloud run real Redis for ElastiCache?
+
+Yes. ElastiCache runs real Redis / Valkey Docker images. `LPUSH`, `ZADD`, `XADD`, streams, pub/sub, Lua scripts — all work. See [Local ElastiCache for tests](/local-elasticache/).
+
+### Do S3 notifications fire Lambda?
</file context>

Suggested change

	Yes. ElastiCache runs real Redis / Valkey Docker images. `LPUSH`, `ZADD`, `XADD`, streams, pub/sub, Lua scripts — all work. See [Local ElastiCache for tests](/local-elasticache/).
	Yes. ElastiCache runs real Redis / Valkey Docker images. `LPUSH`, `ZADD`, `XADD`, streams, pub/sub, Lua scripts — all work. See [ElastiCache](/docs/services/elasticache/).

[cubic-dev-ai]

P3: This link points to a non-existent page. Link to the existing RDS docs instead.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At website/content/faq.md, line 35:

<comment>This link points to a non-existent page. Link to the existing RDS docs instead.</comment>

<file context>
@@ -0,0 +1,133 @@
+
+### Does fakecloud run real databases for RDS?
+
+Yes. RDS emulation pulls real PostgreSQL / MySQL / MariaDB Docker images and runs them as the DB instance. Your SQL schema, indexes, triggers, and extensions work because the engine is real. See [Local RDS for tests](/local-rds/).
+
+### Does fakecloud run real Redis for ElastiCache?
</file context>

Suggested change

	Yes. RDS emulation pulls real PostgreSQL / MySQL / MariaDB Docker images and runs them as the DB instance. Your SQL schema, indexes, triggers, and extensions work because the engine is real. See [Local RDS for tests](/local-rds/).
	Yes. RDS emulation pulls real PostgreSQL / MySQL / MariaDB Docker images and runs them as the DB instance. Your SQL schema, indexes, triggers, and extensions work because the engine is real. See [RDS](/docs/services/rds/).