feat: Add Human-AI Collaboration for Small Teams blog article - #336
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
/lgtm |
|
Nice write-up. One issue I found: Broken internal link. The article links to Suggested fix in -(If you're building a [one-person company with an AI team](/blog/one-person-company-ai-team), this is where you start.)
+(If you're building a [one-person company with an AI team](/blog/personal-ai-company), this is where you start.)Note that Nothing else blocking from a code perspective — content-only change, CI green, images present, JSON-LD not in the file yet but that's mentioned as "prepared" in the PR body so I'll assume follow-up. |
gusye1234
left a comment
gusye1234
left a comment
There was a problem hiding this comment.
Content Review — PR #336 (Human-AI Collaboration for Small Teams)
Reviewed the diff. New MDX article + 3 webp images. No code changes.
Looks good:
- Metadata is complete (
slug,title,date,author,excerpt,readingTime) and matches other posts' shape. - Images are
.webp(small: 75-85KB each), consistent with the site's blog image convention. - External HBR links are real HBR URL patterns; internal link
/blog/personal-ai-company— heads up: PR #339 is currently retitling that same post, but the slug is preserved there so this internal link stays valid. - Content is opinionated but honest (no fabricated stats, no invented case studies) — reads well.
Minor:
- Internal link target.
/blog/personal-ai-companyshould exist post-#339 merge. If #339 changes slug or is dropped, this link becomes dead. Confirmed from #339's diff that slug is preserved — good. - Alt text quality. The three image alt-text strings are descriptive and keyword-loaded, which is fine for SEO but two of them are quite long (100+ chars). Not a bug.
- Date
2026-06-30— matches the batch of June posts, no issue. - Author
Donia— different from the "Alook Team" byline on other recent posts. If this is intentional (a named contributor), fine; if not, worth aligning.
PR description mentions JSON-LD schemas "prepared" — no jsonLd export in the MDX. Once #338 merges, this post could be a good candidate to actually add the FAQ/HowTo schema for rich results. Not required to ship.
Assessment: Content-only, CI green. Safe to merge. Recommend confirming the Donia byline is intentional.
…(ref/id #3) Removes the A2 thread-message guard (which made `/s/c/#N#M` non-navigating) now that the shape is ratified: a thread-message token's `()` holds the thread's OWN channelId (tid) — a thread is its own channel (§3.4b) — so the jump is uniform with a plain-channel message. - resolveMessageJump now takes the token `id` and uses it DIRECTLY as the jump channelId (tid for a thread, cid for a plain channel), NOT a directory lookup: a thread's tid is never in useChannelRefDirectory (top-level only), so a lookup would miss. serverId still resolves from the label's server segment via the directory (the server is always a top-level entity). seq = the message's own seq (parsed.seq = the trailing #M — the thread-internal message to land on). Dropped the `threadRootSeq !== undefined → null` guard. Returns null only for a seqless label (plain channel → navigate) or an unresolvable server. - Access stays server-enforced: a channel's privacy anchors to its parent, so a private-parent thread the viewer can't see returns not-found on open — no client-side climb (Blondie #336). - Display axis vs jump axis (Faustine #332): a thread message's DISPLAY seq is the ROOT seq N ("which message opened the thread" — the human anchor), while the JUMP uses the thread-internal M. refDisplayParts now returns `threadRootSeq ?? seq` for a message pin's display seq; resolveMessageJump keeps `parsed.seq` (M). So a thread pill reads `ideas #N` (and when the tid has no directory name — always, since tids aren't in it — it degrades to that leaf + root-seq, never empty/bare-tid). Zero producer emits thread-message tokens today; this is the定形 + the jump/display wiring for when one exists. Touches A2 (QA'd) → Ingaborg re-verify. shared 1721 / web 3512 / daemon 787 green, 3-pkg typecheck + web knip clean, full pre-commit no --no-verify. Stacked on origin bfb0df4, local.
2 participants
Summary
Add new SEO blog article: Human-AI Collaboration for Small Teams
Files
SEO
Validation
validate:blogscript passed