Skip to content

Remove "hosting" wording from recipe copy #14

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
batuhan wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove "hosting" wording from recipe copy #14

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion recipes/status/meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,5 +27,5 @@
"Scheduled maintenance notices",
"Subscribe-to-updates email field and links to support / Twitter"
],
"based_on": "A public status page in the Atlassian Statuspage / Instatus mold for a developer API or hosting company, the type linked from a footer and watched during outages (modeled on Slack, Stripe, and OpenAI status pages)."
"based_on": "A public status page in the Atlassian Statuspage / Instatus mold for a developer API or platform company, the type linked from a footer and watched during outages (modeled on Slack, Stripe, and OpenAI status pages)."
}
2 changes: 1 addition & 1 deletion recipes/status/prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Build me a **public status page for my API / hosting product** — the kind of page linked from a footer and watched during an outage (think Stripe, Slack, or OpenAI status) — as a single self-contained static site (`index.html` + `styles.css` + `app.js`, no build step, no framework).
Build me a **public status page for my API or developer platform** — the kind of page linked from a footer and watched during an outage (think Stripe, Slack, or OpenAI status) — as a single self-contained static site (`index.html` + `styles.css` + `app.js`, no build step, no framework).

**Before you build, ask me these questions in one message and wait for my answers. If I skip anything, choose a sensible default and tell me what you chose:**

Expand Down
2 changes: 1 addition & 1 deletion recipes/wp-react/meta.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
"Newer/Older pagination driven by the X-WP-TotalPages header",
"Loading skeletons, empty state, and a recoverable error panel with Try again",
"Light/dark theme toggle persisted to localStorage",
"SPA fallback (_redirects → /* /index.html 200) so deep links work on static hosting"
"SPA fallback (_redirects → /* /index.html 200) so deep links work on a static site"
],
"based_on": "A headless-WordPress reading app: a React single-page app that fetches posts from a public, CORS-enabled WordPress REST API straight from the browser — the kind of decoupled front end developers build on top of an existing WP install.",
"notes": "Content is fetched live from the WordPress REST API at runtime, so there are no Unsplash/stock photo terms — images come from each post's _embedded featured media. Default API base is wordpress.org/news (the classic demo.wp-api.org demo is frequently offline). Build with `npm install && npm run build`; publish the dist/ folder.",
Expand Down
Loading