Stream: SIG Documentation

Topic: Docs Focus for 2H 2026

Victor Adossi (Jun 17 2026 at 15:39):

Hey all,

In this weeks meeting we discussed where the focus of the docs team should be for the second half of 2026 (just as a vague time marker). Here's what we came up with:

1. Smooth the onboarding path
2. Construct a clear path from demo-level competence to advanced practical use cases
3. Increase traffic to the component model book, for a specific non-Rust language
4. Concretely measure the number of people trying the component model (maybe via a template they can clone that we can watch metrics on?)
5. Better explanations of wasmtime vs wit-bindgen vs other tools in building components
6. How to build a custom embedding with wasmtime is not covered (though the host does it in-repo)

Victor Adossi (Jun 17 2026 at 15:41):

After a little bit of discussion, it seems like (4) is a lynchpin for a goals (1),(2), (3), and (5) -- In the sense that we need to have an action for people to take that we can measure.

(6) is actually just a work item that IMO someone could pick up -- we probably should have a page on that and we just dont

Victor Adossi (Jun 17 2026 at 15:42):

Also, explicitly, P3 is a high priority right now since it's been announced, but as @Eric Gregory has already worked on most of that and things are just waiting for reviews I think we're good there at least to start!

Victor Adossi (Jun 17 2026 at 15:43):

Addition thoughts?

@David Bryant @Daniel Macovei @Mikhail Katychev @Kate Goldenring @Eric Gregory ?

Victor Adossi (Jun 17 2026 at 15:43):

Basically it seems like the first thing to do is break out the current in-tree examples to their own repos so we can track when they're forked/used as templates?

This is something that came up during the meeting, but we figure we can add some CTAs to per language pages, and this will inform success in other areas/goals

Kate Goldenring (Jun 17 2026 at 16:06):

could one option be to track registry pulls of an artifact if we have a quickstart that does a wkg pull?

Victor Adossi (Jun 17 2026 at 17:44):

Oh yeah definitely -- I think that signal might get muddy w/ things like CI runs or stuff like that, but it would definitely be directionally right!

David Bryant (Jun 18 2026 at 17:44):

I definitely appreciate the effort here to strategize about 2H2026 goals across documentation broadly and am comfortable with the list list you produced. It's great that one of those items unlocks most of the others, so initial focus on being able to measure some aspect of component model use sounds both great here and a very good thing to do generally.

If there's anything I can do to help you all out operationally or relative to BA infrastructure, services, website, etc. please don't hesitate to let me know!

Mikhail Katychev (Jun 18 2026 at 17:46):

is there anything in the ghcr OCI setup to allow us to track clones/pulls?
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

Mikhail Katychev (Jun 18 2026 at 17:46):

I can't seem to find anything in the docs

Victor Adossi (Jun 19 2026 at 15:16):

Yeah I definitely don't know that we get much as far as tracking pulls on ghcr, you do get pull counts on tags though!

Victor Adossi (Jun 19 2026 at 15:17):

So for example a component from the project I work on -- we have the pull count for 0.1.0, but it's like 9.3MM pulls... I think that signal might not be great

Last updated: Jul 29 2026 at 05:03 UTC