Building a personal hub on Cloudflare Pages
Replace videoId with your YouTube video IDs. Embeds load lazily for performance.
Daniel's Corner is a Cloudflare Pages hub for the domains I am building, YouTube notes, Google Drive legacy work, prompt-and-answer logs, and raw thinking before it becomes something polished. Critical content ships as static HTML so Google and LLM crawlers can read it without JavaScript.
Owned domains include IsraeliLeads, Prism Publication, and Devorah's Art, plus this hub on Cloudflare Pages. Each row lists production URL, dev preview, status, and stack in a plain HTML table crawlers can parse.
Update public/data/domains.json, run npm run build, then deploy. The table below is static HTML generated from that file.
| Project | Live | Dev | Status | Stack |
|---|---|---|---|---|
| IsraeliLeads | Production | Dev / preview | live | Cloudflare Pages |
| Prism Publication | Production | n/a | live | Web |
| Devorah's Art | Production | Dev / preview | live | Cloudflare Pages |
| Daniel's Corner | Production | Dev / preview | dev | Cloudflare Pages |
TLDR: Owned domains: israelileads.com, prismpublication.com/company, devorahsart.com, plus this hub.
Related: IsraeliLeads · Prism Publication · Devorah's Art · How to build this hub
Six Pages projects and one Worker on the Prism Publication Cloudflare account. Each row links to the live preview and the Cloudflare dashboard for deploys and settings.
Edit public/data/cloudflare-dev.json, run npm run build, then deploy. Dashboard links use account f8c334… on dash.cloudflare.com.
TLDR: ConvoMargin, Daniel's Corner, ChatAD Land, FitFeed, two Trump legacy Pages sites, and the Claude Plus You Worker.
Related: Domains and dev pages · Hub build guide
Videos embed through the privacy-enhanced youtube-nocookie.com host with lazy loading so the homepage stays fast. Each card includes a title and description in static HTML beneath the iframe.
Swap video IDs in public/data/youtube.json and rebuild. Embeds load only when the user scrolls near them.
Replace videoId with your YouTube video IDs. Embeds load lazily for performance.
TLDR: Lazy YouTube embeds with titles and descriptions in plain text for crawlers.
The blog stores the exact prompt and the full answer as static HTML on each post page. List cards on this homepage preview the title, date, and summary so search engines and LLM retrievers see the content without running JavaScript.
Add rows to public/data/blog-posts.json or open a post to read the full prompt-and-answer pair.
Use static HTML with JSON data files, a build step that inlines content for crawlers, lazy YouTube embeds, prompt-and-answer blog posts with question-based H2s, and a thinking capture page that exports entries you can commit to git.
TLDR: Prompt-and-answer logs ship as static HTML for search and LLM discovery.
Related: Full blog index · RSS feed
Short dated notes live in JSON and render as static HTML on this page. The Thinking page adds local browser drafts you can export and commit to git when an idea is ready to publish.
Nothing is sent to a server until you merge exported JSON into public/data/thoughts.json and redeploy.
One site for everything I am building: domains, dev previews, prompt logs, Drive archives, and raw thinking before it becomes a post.
Cloudflare Pages keeps it fast and cheap. Static HTML first so Google and LLMs can read it without running JavaScript.
TLDR: Capture locally, export JSON, merge into thoughts.json, rebuild, deploy.
Related: Thinking capture page · Prompt blog
Legacy exports, slides, and code snapshots link out to Google Drive folders. Each card names the archive, year range, and description in static HTML so the hub stays a single index for old and new work.
Update public/data/drive-projects.json with your Drive folder URLs, then rebuild and deploy.
Replace driveUrl with your Google Drive folder link. Opens in a new tab.
Add folders for slides, spreadsheets, and exported code snapshots.
TLDR: Drive folders linked as static cards with title, year, and description.
Related: Active projects table · Hub build guide
These are the most common questions about how Daniel's Corner is organized, updated, and published. Answers appear in plain text below and in FAQPage JSON-LD in the page head.
public/data/domains.json, run npm run build, then npm run deploy.public/data/blog-posts.json, rendered at /blog/{slug}/ as static HTML with the full prompt and answer.thoughts.json, rebuild, and redeploy.TLDR: JSON data files plus a build step keep every public page crawler-readable.
Related: Full hub build guide · Blog