WordPress can’t render a stacked nebula photo. Substack won’t even try.

Can I embed Stellarium or other sky chart tools in my posts?

Yes. The TipTap editor includes a /star-chart slash command that embeds Stellarium Web (the open-source browser version) or Aladin Lite (CDS sky atlas) inline in your observation log or deep-sky image report post. The embed renders an interactive star chart centered on your target's RA/Dec coordinates, which you set in the capture-data block attached to the post. For static finder charts, you can upload a screenshot generated from Stellarium Desktop, Cartes du Ciel, or any planetarium software as a standard AVIF image.

Does VeloCMS preserve RAW or TIFF astrophotography files, or does it convert everything to JPEG?

VeloCMS preserves your original file as the source attachment and serves a display-optimized AVIF conversion for the post. A 22MB PixInsight TIFF becomes a 400-600KB AVIF for web display — full-bleed Aperture layout, pinch-to-zoom on mobile, no JPEG artifacting at nebula dust-lane detail level. The original TIFF is stored in Cloudflare R2 and downloadable by the post author. For digital product sales (raw stacks, calibration frames, processing workflows), you can sell the original TIFF via BYOK Stripe checkout at 0% platform fee.

What is the image weight budget for a 12-image deep-sky gallery post? Will it still hit sub-1s LCP?

Yes. At AVIF compression, a 12-image deep-sky gallery with 22MB source TIFFs per frame comes out at 12 x 200-350KB per AVIF = 2.4-4.2MB total for the full gallery. Next.js lazy-loads all gallery images below the fold and serves only the above-the-fold hero image for the initial LCP measurement — so even a 12-image gallery post hits sub-1s LCP on 4G with the Aperture full-bleed layout. The hero image (typically the finished nebula or galaxy image) renders at the Cloudflare edge at the visitor's viewport width, so a 1440px desktop visitor gets a 220-300KB AVIF hero, not a 22MB TIFF.

Can I set up an RSS feed for a sky-events or star-party calendar?

Yes. Every VeloCMS blog generates an RSS 2.0 feed at /rss.xml and a JSON Feed at /feed.json. You can tag star party announcements and sky-events posts with a specific tag (e.g., 'star-party' or 'sky-event') and generate a filtered RSS feed at /tag/star-party/rss.xml that subscribers can add to their planetarium software, Feedly, or sky-events aggregator. The /star-party TipTap block also generates JSON-LD Event schema that gets indexed by Google Events — so your star party announcements appear in Google search as event cards with date, location, and RSVP link.

Can I cross-post my observation logs to Cloudy Nights or other astronomy forums?

VeloCMS generates a Cloudy Nights-compatible post excerpt — a 150-word summary with the canonical link to your full observation log — via the cross-post settings in Admin -> Distribution. You paste the excerpt into Cloudy Nights manually (the forum doesn't have an API for automated posting). The canonical link in the cross-post drives Cloudy Nights readers back to your VeloCMS domain where the full report, subscriber signup, and AVIF image gallery live. Your affiliate links and paywall gates are on your domain, not the forum.

Does VeloCMS support JSON-LD for telescope reviews and affiliate revenue?

Yes. The TipTap editor includes a /telescope-review structured data block that renders schema.org/Product + AggregateRating markup on equipment review posts. When a search engine crawls your Celestron EdgeHD 11 review, it reads the structured data and marks the post as eligible for Google Rich Results — star rating displays next to the search result, which increases CTR and affiliate conversion. The affiliate link (Amazon, B&H, OpticsPlanet, Astronomics, OPT Telescopes) is disclosed in the structured data as a potentialAction recommendation. You configure your affiliate ID once in Admin -> Settings -> Affiliates and the blocks auto-inject your ID into every equipment link.

How does the Bortle scale tag system work across the archive?

You assign a Bortle scale value (1-9) to each observation log post or astrophotography report using the /capture-data block. The tag creates a filterable archive at /bortle/4 (or whichever level you use most frequently). Readers can filter your full observation log archive by Bortle scale to find sessions conducted under specific sky conditions — useful when they want to compare your Bortle 4 M31 images with your Bortle 7 M31 images to understand light pollution impact. The tag also appears in the observation log's structured markup, making Bortle scale a searchable dimension for LLM crawlers answering queries like 'what can you see under Bortle 5 skies with a 10-inch Dobsonian.'

I run a dark-sky preserve campaign. Can I use VeloCMS for advocacy content alongside the astronomy blog?

Absolutely. Dark-sky preservation advocacy, light-pollution mapping analysis, Bortle-scale methodology writing, IDA designation campaign documentation, and municipal lighting ordinance coverage are all first-class content types on VeloCMS. The Studio Newsroom theme works well for advocacy journalism (Inter display headlines, pull-quote callouts, newsroom editorial column for policy analysis). The Engineering theme works for technical Bortle-scale measurement documentation. You can run both on the same blog with tag-based archive filtering. A paid 'Dark Sky Preservation Digest' newsletter at $7/mo (IDA policy coverage, light pollution mapping updates, municipal ordinance wins and setbacks) earns subscription revenue from the same audience reading your observation logs — same subscriber, two content tracks, one platform.