How we run our newsletter on our own Astro stack instead of Substack
The article discusses the transition of a newsletter from Substack to a self-hosted Astro stack. This move was motivated by the desire for better SEO control and customization. The author highlights the benefits of owning the entire setup, including improved structured data and a more tailored reading experience.
- ▪The newsletter was previously hosted on Substack but was moved to gain control over SEO elements.
- ▪The new setup uses the same Astro build as the rest of the site, allowing for seamless integration and customization.
- ▪Features like sidenotes and structured data are easily implemented due to ownership of the rendering process.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/nadyyym/how-we-run-our-newsletter-on-our-own-astro-stack-instead-of-substack-20fb |
| Publication time | Fri, 22 May 2026 07:52:47 +0000 |
| Retrieval time | 2026-05-22T08:02:00.886Z |
| Last seen | 2026-05-22T08:02:00.886Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 5WnAsyS0GDhb |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3945556) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Vladimir Nadymov Posted on May 22 • Originally published at getbeton.ai How we run our newsletter on our own Astro stack instead of Substack #newsletter #buildinpublic #opensource #sal This is a post about plumbing. We send a newsletter, it goes out from our own site, and over the last few months that setup turned into something I actually like working on. Here is the whole thing. Why we left Substack The newsletter used to live on Substack. We moved it for one reason: SEO control.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
