Stack Quarterly is a quarterly developer publication. This page exists for journalists, conference organizers, vendors who want to cite us, and anyone making a slide that includes our wordmark. Everything you need to refer to the publication accurately is below.
What we are
Stack Quarterly is a practitioner publication covering the AI and agentic developer-tooling market. Each issue is a small bundle of long-form pieces written by working engineers who have shipped agentic systems in production. We are quarterly by design: four issues a year, rolling pieces between them, no hot-takes from the news cycle.
The publication is operated by Lumenwhite Media Holdings Pte Ltd, a media-holding subsidiary of Web4Guru. Editorial control sits with the named bylines on the contributors page. The disclosure paragraph at the bottom of every page is the canonical version.
Official names and tagline
| Field | Value |
|---|---|
| Publication name | Stack Quarterly |
| Short form | SQ |
| Tagline (canonical) | “Quarterly deep dives on the tools real teams actually ship with.” |
| Tagline (short form) | “A practitioner publication.” |
| Operating entity | Lumenwhite Media Holdings Pte Ltd |
| Parent | Web4Guru (editorial independence preserved) |
| Established | 2026 |
| Cadence | Quarterly (four issues per year) plus rolling pieces |
| Voice | Practitioner-first, dry, code-where-code-applies |
| ISSN | [TKTK: ISSN-pending] |
Never style the publication name as STACK QUARTERLY in body copy; mixed case only. The brand mark SQ may be used in monospaced-uppercase. Do not abbreviate the title to “Stack” alone in print — the publication is two words.
Brand colors
| Token | Hex | Use |
|---|---|---|
| Accent (dark mode) | #7cc4ff | Brand mark background, links, callouts |
| Accent (light mode) | #0a66c2 | Brand mark background, links, callouts |
| Accent strong (dark) | #a7d9ff | Hover/active links |
| Accent strong (light) | #084d92 | Hover/active links |
| Background (dark) | #0f1115 | Default body |
| Background (light) | #fbfbf8 | Default body |
| Foreground (dark) | #d7dbe2 | Body text |
| Foreground (light) | #232730 | Body text |
| Rule (dark) | #262b36 | Horizontal rules, card borders |
| Rule (light) | #e5e3dc | Horizontal rules, card borders |
The accent is locked. Do not substitute teal, blue-green, or violet variants in derivative work that cites Stack Quarterly. If your publication’s design system cannot render the locked cyan accurately, use neutral grey for the brand callout and a footnote crediting Stack Quarterly inline.
Typography
| Slot | Font |
|---|---|
| Body | Iowan Old Style → Charter → Georgia → serif fallback |
| Headings / UI | Inter → system sans fallback |
| Code / mono labels | JetBrains Mono → Fira Code → SF Mono → ui-monospace fallback |
| Body size | 18px / 1.65 line-height |
| Max measure | 78ch |
If you cannot license Iowan Old Style for republication, Charter is the approved substitute. Do not republish Stack Quarterly pieces in a generic system serif if a better option is available.
Logo and lockups
Stack Quarterly does not yet ship a complex wordmark. The brand mark is a typeset SQ chip — JetBrains Mono Bold, white-on-accent, 3px corner radius, all caps, 0.05em letter-spacing — followed by the publication name in Inter Bold. Download the raw SVG: [TKTK: brand-svg-url]. Acceptable lockups:
- Horizontal: chip + name on the same baseline. Use this in headers, citations, and credit lines.
- Stacked: chip above name. Use in narrow vertical contexts only (sidebar widgets, business cards).
- Mark only: chip on its own. Reserve for favicons, app icons, and other contexts where the full name is redundant.
Minimum size of the brand mark is 24px high on screen, 0.6cm in print. Clear-space around the lockup is one chip-width on every side. Do not place the lockup on a busy photograph; if you must, use a flat 1px stroke in --rule between the lockup and the photo.
Editorial photography and OG images
Stack Quarterly does not publish stock photography in articles. The default open-graph image is a gradient + brand chip composition rendered at 1200x630 in the brand palette. Per-article OG images are generated at build time and reuse the same template — title set in Inter Bold, dek set in Iowan Old Style italic, byline set in JetBrains Mono. Vendors who want to embed our covers in their slides may screenshot the OG image directly; please link the article underneath.
Masthead bios (long form)
The full bios for each named contributor live on the contributors page. Short-form bios suitable for one-line speaker introductions:
Reza Mokhtari — Senior Practitioner Writer at Stack Quarterly. Covers agentic orchestration, MCP, and the working tooling choices of teams shipping in production.
Ginger Wolfe-Suarez — Staff Developer-Essayist at Stack Quarterly. Covers developer workflow, team adoption patterns, and the architectural decisions that signal team posture.
Editorial Team — A rotating byline used on landscape surveys, listicles, and decision-piece essays where the publication speaks collectively. Includes the editor, the named contributors above, and a research lead.
Press contacts
| Reason | Address |
|---|---|
| Editorial inquiry | editorial@stackquarterly.com |
| Pitches and contributions | pitches@stackquarterly.com |
| Tips (confidential) | tips@stackquarterly.com |
| Press / media | press@stackquarterly.com |
| Corrections | corrections@stackquarterly.com |
Stack Quarterly does not maintain a press phone line. Response time on press@ is two business days during issue weeks and five business days between issues. We do not pre-comment on unpublished pieces, do not confirm or deny attendance at unpublished conferences, and do not provide pull-quotes for vendor announcements except where the publication has already covered the underlying product.
Use of our brand
What you may do
- Cite Stack Quarterly pieces with byline, date, and a working URL. Republish up to 200 words of body text per piece for review and reporting purposes under fair use, with a link back to the original.
- Use the Stack Quarterly wordmark and brand mark in slides, panels, and writeups that cite our coverage. The mark is not a trademark we have registered; you do not need permission.
- Quote our writers in your own pieces. Where possible, contact the named author first — bylines are listed on the contributors page and email addresses follow the convention
<firstname>@stackquarterly.com. - Embed our OG images in slides that cite the underlying piece. Link the piece from the slide.
What you may not do
- Imply Stack Quarterly endorses a product, agency, vendor, or person on the basis of coverage. Coverage is not endorsement. We do not provide blurbs.
- Reprint full pieces without permission. Excerpts within fair-use limits are fine. Full reprints require written permission from the named author and the publication editor; mail editorial@stackquarterly.com.
- Use the Stack Quarterly wordmark on commercial collateral (sales decks, landing pages, ad creative) without written permission. Pretty much always granted for honest citation, never granted for testimonial positioning.
- Modify the brand mark — recoloring the accent, restyling the chip, or replacing the typeface — and continue to identify the result as Stack Quarterly. Derivative marks should be clearly labeled as not produced by us.
Republication policy
We accept republication requests for individual pieces under the following terms:
- Full piece, no edits beyond house-style adjustments. The original byline, date, dek, and the line “Originally published at Stack Quarterly” must appear at the top of the republished piece.
- A canonical link tag in the HTML head pointing at the original Stack Quarterly URL. We are happy to provide the exact tag on request.
- No paywall on the republished version unless the original is also paywalled. (None of our pieces are paywalled at launch.)
- The republication runs at most 30 days after the Stack Quarterly publication date. Pieces older than 30 days republished as “new” mislead the reader.
Send republication requests to editorial@stackquarterly.com with the publication name, the target URL, and the intended publication date.
Fact-check and corrections
Stack Quarterly corrects in place and appends a dated note at the bottom of any corrected piece. The full corrections log lives at /corrections/. If you spot an error in a piece — a misquoted source, a wrong version number, a misattributed claim — write to corrections@stackquarterly.com with the piece URL and the proposed fix. We aim to acknowledge correction requests within one business day and to publish the correction (or a “no correction needed, here’s why” reply) within five.
Permissions and legal
Stack Quarterly’s republication terms are documented above. Our privacy policy is at /legal/privacy/. Our terms of service are at /legal/terms/. Lumenwhite Media Holdings Pte Ltd is a Singapore-registered media-holding company. For legal correspondence, write to editorial@stackquarterly.com and request the legal address; we do not publish a physical mailing address on this site to limit address-spam to the editorial team.
A note on independence
The relationship between Stack Quarterly and Web4Guru is exactly what the disclosure paragraph says: Web4Guru is the holding parent, the publication is editorially independent, and Web4Guru does not approve, review, or commission specific pieces. The publication has covered and will continue to cover Web4Guru and Web4OS the same way it covers any other vendor in the agentic-stack market — by reporting what working practitioners are doing with it, what they like, and what they would change. If a piece is uncomfortable for a vendor, the piece still runs.