Thank you for the update on this important work,@cyr06130.
In onboarding myself to Polkadot, I have noticed the fragmented nature of the various information sites. Despite your good work, I often find content that is out of date, duplicating (or forking) other content, or somewhat haphazardly organised. Even though I am fairly new here, I have been gaining confidence that it’s not just me 
. I’ve made a couple of small contributions danrandow (junglanml) · GitHub , but somewhat blindly, as I have been wondering where the strategic approach to this is.
So it’s great to hear about Horizon, and see these examples of exactly that strategic approach! Is there some way I could participate?
Wider thoughts…
Websites are easier to fix than the UX of Polkadot itself, which like anything in web3, is a hard problem. Web content can smooth onboarding too, of course, for users and developers. And it is crucial to people’s first impressions, including in search results and increasingly, in LLM responses.
Improving content requires some clarity about the purpose that each site has to fulfil, and some patterns and standards for how to do that. Without these, any evaluation of a specific content improvement will swerve off into what we are trying to achieve and how.
And that, and other initiatives like biz dev, slogan, governance even, requires a decently clear product (hub, cloud, …) strategy, which in turn requires an overall Polkadot strategy. @flez, your comments and the context you link to are super-interesting to me, thank you 
. @alice_und_bob has contributed lots of strategy thinking too (eg Polkadot Growth Strategy ). And yet (maybe it’s just me?) none of this seems to coalesce. Though I don’t want to drag this thread away from its UX and DevX focus, I am also curious to know where Polkadot’s strategy and product schelling point is?