Skip to content

docs: fix README branding, add services link and contact - #13

Merged
rome2o merged 4 commits into
mainfrom
readme-seo-fix
Sep 17, 2026
Merged

rome2o merged 4 commits into
mainfrom
readme-seo-fix

Conversation

@rome2o

@rome2o rome2o commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace the old internal codename cloudflare-shopify-starter with the actual repo identity shopify-on-cloudflare in the README H1 and setup command examples (D1 wrangler d1 create, R2 wrangler r2 bucket create, HOST example hostname, and the D1 execute seed command). The "Deploy to Cloudflare" button already pointed at the correct devkindhq/shopify-on-cloudflare repo path, so it was left unchanged. The live preview link (cloudflare-shopify-starter-template.ali-d43.workers.dev) is a real deployed Worker subdomain, not repo text, so it was left as-is rather than rewritten into a non-existent URL.
  • Add one outbound link to Devkind's Shopify development services page (https://devkind.com.au/services/shopify).
  • Add an author/contact byline: "Built by Devkind. Maintained by Kazim Ali."
  • No performance numbers, star counts, or benchmark claims were added — this is a structural/branding/link fix only. All existing setup, architecture, and stack content is untouched.

Ref: 04-projects/devkind-agentic-engineering/shopify-on-cloudflare-seo-audit.md (gap 3) in the internal vault.

Test plan

  • Kazim review only — README rendering can be checked directly on the PR diff/preview on GitHub.

Replace the old internal codename cloudflare-shopify-starter with the
actual repo identity shopify-on-cloudflare in the H1 and setup command
examples (D1/R2 resource names, HOST hostname example). Add a single
outbound link to Devkind's Shopify services page and an author/contact
byline, per the oss-github-seo README template.
…udflare

Aligns wrangler.jsonc (name, D1/R2 resource names, comments), package.json
(name field, D1 script commands, binding descriptions), package-lock.json
name fields, src/index.ts health-check string, and both CLAUDE.md files
with the repo's actual name so the documented commands match the config
resource names.
@rome2o
rome2o merged commit fd66ed2 into main Sep 17, 2026
4 checks passed
@superkindhq

superkindhq Bot commented Sep 17, 2026

Copy link
Copy Markdown

post-merge verify-fixes audit - shopify-on-cloudflare #13 (README branding/docs)

Merged 2026-09-17 21:12 UTC into main. Zero reviews pre-merge - full post-merge review of the 210-line diff (docs + config renames, no logic).

Verified

  • Rename is consistent across the 7 touched files: cloudflare-shopify-starter -> shopify-on-cloudflare / shopify-on-cloudflare-db / -files in README, CLAUDE.md (root + src/), package.json, package-lock.json (both name nodes), wrangler.jsonc (name, database_name, bucket_name), and src/index.ts /health app string.
  • The Devkind services link + contact section is additive, correctly placed before the License section.

Findings (2, both low)

  1. 3 stale cloudflare-shopify-starter references remain (verified via code search at main): .dev.vars.example:18 and .env.example:13 (example HOSTnames) and README.md:12 - the "Live preview" link still points at the old-template workers.dev URL. That preview is still up (verified 200 just now; /health still reports app: cloudflare-shopify-starter, i.e. deployed from the pre-rename Worker name), so the link works today, but it now advertises the old brand and silently rots if that Worker is renamed/deleted. Suggest a follow-up one-liner renaming the remaining three.
  2. Deploy-name note: wrangler.jsonc name changed to shopify-on-cloudflare, so the next wrangler deploy from this repo creates a NEW Worker rather than updating the existing old-template one. If the live preview Worker should keep serving, whoever deploys next needs to update the README link (or keep the old name). Not a code issue - branding/ops alignment.

Verdict: clean docs merge; the two leftovers are cosmetic.

Posted by the scheduled merged-PR verify-fixes audit (comment-only, no action taken on branches).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant