# Newsletter tip submissions

> Three tier-A newsletters with public tip-forms or contact email. Submit T+3 to T+5 (after Show HN settles; you want a stable star count to cite). Each reaches 100K–500K developers daily.

## Targets

| Newsletter | Audience | Subs | Submission |
|---|---|---|---|
| **Ben's Bites** | AI builders (general AI) | ~163K | [bensbites.beehiiv.com/p/contact](https://bensbites.beehiiv.com/p/contact) — tip-form |
| **TLDR AI** | Tech/AI generalists | ~500K+ | [tldr.tech/submit](https://tldr.tech/submit) — submit form |
| **AI Engineer Weekly** | AI engineering practitioners | ~50K (tight fit) | [ai.engineer/newsletter](https://www.ai.engineer/newsletter) — email |
| **The Rundown AI** | Broader AI weekly | ~700K (less fit) | [therundown.ai/submit](https://www.therundown.ai/submit) |

Hit Ben's Bites and TLDR AI for sure; AI Engineer Weekly if you can find the right submission path; The Rundown only if time allows.

## Submission text (paste-ready)

```
Tool: doc-wiki — open-source Claude Code plugin (Apache 2.0)
URL: github.com/narailabs/doc-wiki
One-line description: Maintained wiki layer over code + Jira / Confluence
+ GitHub / GitLab / Notion / Linear / AWS-GCP / ORM-DB schemas — ER
diagrams from your real ORM models, an auto-generated cross-service
map, cited answers your coding agent reads before touching code.

Why it's interesting:
- The authors benchmarked their own headline claim (does the wiki lift
  autonomous ticket-fix accuracy?) and published the null in full — 92
  ticket pairs, SWE-bench-style, container-isolated; baseline 57/92 vs
  wiki 54/92, at benchmark/RESULTS.md. Rare transparency in a space
  full of unreproducible demos.
- Most AI coding tools target clean OSS code; doc-wiki targets the
  8-year-old enterprise monoliths people actually work in — including
  the root-of-microservices case where it documents how the services
  relate to each other. Smaller side projects work too.
- The pattern (LLM Wiki) was named by Karpathy in April 2026 (gist:
  https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f);
  doc-wiki is the enterprise-codebase execution.
- Apache 2.0 forever — explicit no-relicense commitment.

Show HN landed Tuesday at <HN_LINK>, currently at <N> stars.

Contact: <YOUR_EMAIL>
```

## Notes

- **Don't submit before Show HN** — newsletters love using the "trending on HN" hook, but only if it's recent. Submit T+3 when the post is still warm and you have an actual star count.
- **If accepted:** these run with 1–7 day editorial lead times. Don't expect same-day publication.
- **Track placements:** each newsletter inclusion typically drives 500–2000 GitHub visits in a day, ~5–10% star conversion. Worth measuring.
- **Don't re-submit the same week if no acknowledgement.** Wait 30 days.
- **If TLDR AI rejects** (they're picky about non-VC-backed tools sometimes): the AI Engineer Weekly submission carries the same audience minus 90%; still worth doing.
- **Don't pay for sponsored placement.** It dilutes the organic signal and most of these have honest reviewers anyway.