Blog
Public pages before the private app
Why Meteoric Creates and Zeal publish finished About, Contact, policy, and guide pages instead of parking everything behind /app/.
The login wall problem
A private journal needs authentication. A publisher site does not. When those two needs collapse into one URL, strangers meet a password form where they expected an explanation. Search engines, accessibility tools, and ordinary curious people all bounce for the same reason: there is nothing public to read.
Zeal therefore splits surfaces. The private journal lives at /app/. Public overview, guides, and policies live as ordinary HTML. Meteoric Creates, the studio host, carries the brand welcome, blog index, and studio policies. Ads, when shown, stay on public content—never inside the journal.
What “finished” public pages look like
Finished does not mean ornate. It means a real contact email, a named publisher, working navigation, a disclaimer that matches product behavior, and guides that are long enough to teach something without inventing clinical authority.
It also means saying no to placeholder chrome. “Soon” menus, empty blog indexes with no plan, and policy pages that contradict the app are all forms of unfinished publishing. They waste a visitor’s time and they make the studio look accidental.
Guides versus studio essays
Zeal guides are practical: hydration logging, sleep hygiene for journaling, walking as a default workout, reading daily trends without obsessing. Studio essays here talk about how we build and talk about software. Both are original. Neither is medical advice.
If a topic is about using the journal day to day, it belongs on the product host. If a topic is about Meteoric’s publishing choices or product craft, it belongs here. That rule keeps each sitemap coherent.
Advertising stays secondary
Public pages may show optional advertising after consent where required. The private journal does not. Policy pages that explain privacy, terms, disclaimer, and advertising also stay ad-free so disclosures are not competing with inventory.
We would rather earn attention with readable pages than with speculative doorway content. If advertising ever funds the studio, it should sit beside writing that would still be worth publishing without ads.
How reviewers and humans share needs
People evaluating a consumer product and automated crawlers looking for ownership signals need many of the same pages: who runs this, how to contact them, what the product claims, and where advertising may appear. Hiding those answers behind authentication fails both audiences at once.
That is why Zeal’s guides are public HTML with real paragraphs, not screenshots inside a logged-in tour. A guide you cannot read without signing up is a brochure, not a guide.
The studio blog exists for the same reason on meteoriccreates.com. Craft notes should be linkable. If the only way to understand the publisher is a social profile that might disappear, the site is incomplete.
Maintenance over launch theater
Launch posts age badly when the product changes and the essay does not. We prefer evergreen craft writing and dated policy pages. When behavior changes—new auth providers, new storage modes, new ad placement rules—the matching public page should change in the same release when possible.
Broken links are treated as product bugs. A calm brand cannot afford ornamental navigation that 404s. The build gate fails releases that ship thin guides or missing trust pages for exactly that reason.
Two hosts, one publisher
meteoriccreates.com is the studio door. zeal.meteoriccreates.com is the product door. Both should feel related without cloning every paragraph. Shared contact email, shared health boundary, distinct jobs.
Cross-links exist so a reader can move from a studio essay into a guide, or from a guide back to the publisher’s about page. Dead ends are a design smell. So are loops that bounce someone between identical policy text copied twice with different titles.
The private journal remains the only place that needs an account for core logging. Everything required to understand ownership and risk should remain readable without one.
That architecture also keeps advertising decisions clearer. Public content may fund the studio someday. Private entries should never become ad inventory. Splitting hosts and paths makes that rule easier to keep.
What “enough content” means for us
Enough content is not a keyword farm. It is a set of pages that answer ownership, contact, health limits, advertising placement, and day-to-day journaling questions with original paragraphs. Guides on the product host should teach a reversible habit. Studio posts should explain a publishing or engineering choice without inventing clinical authority.
We keep a build gate that fails thin guides and missing trust pages because unfinished public surfaces are how small sites get rejected by both humans and advertising programs. Shipping the journal first and “filling in policies later” is a common pattern. It is also a pattern that makes the product look abandoned on day one.
If you are building a similar split, publish the boring pages early: About, Contact, Privacy, Terms, Disclaimer, Advertising, sitemap, and ads.txt. Then deepen guides. The private app can grow behind authentication once strangers can already verify who you are.
A short closing
Public pages are not a delay before the “real” product. They are part of the product’s promise that strangers can understand what they are dealing with before they type a password.
Related studio notes
Disclaimer: Educational studio writing only—not medical advice. Zeal AI meal photos are optional model estimates and are not lab measurements. Read the full Disclaimer and Zeal Privacy before relying on any health-adjacent wording.