Carter Anderson

> The "Single Arc tree" bullet point in "Bevy Assets v2" section mentions we could attach metadata to handles. Using this for change ticks would make the implementation much more...

I think putting this in the "next steps" for beginners might be a mistake. This feels like "advanced level Rust for people that are curious", not something to direct people...

I'm on board for this! Although in the short term I think its probably more important to focus on "non-relative to other engines learning content". Given how sparse the current...

I wouldn't mind a samples repo maintained at a best-effort / with reduced scrutiny. Especially if the samples are allowed to "fall behind" bevy versions. We can do that under...

(provided we're still meticulous about licensing and attribution)

If yall can agree on a name I can create it. Do we want to limit it to "blog post samples" or expand it to accommodate anything?

This doesn't acknowledge or address the recent plan as laid out here: https://github.com/bevyengine/bevy-website/issues/623#issuecomment-1518887997. I personally think that is still the best path forward. I'm also not particularly excited about moving...

> I think the fact that it hasn't moved in almost 2 months shows it may not be the best path forward... I see this as an indicator of a...

For now I'm back on team "internal observer cache storage" in the interest of moving forward. I do think its a solid design given the constraints, and the current impl...

Just pushed a unification of Events + Triggers, as discussed above, as well as relevant renames. (open to discussion ... this is just for consideration)