In the first 90 days, the DSTS knowledge library should not chase random volume. The more important promise is publishing rhythm: each week has cadence, each topic has a role, each article deepens understanding, and the system never falls into empty pages.
Content pillars must serve the project map
The first pillars should cover what DSTS is, no black pages, knowledge library, Script Journey, Movement Portal, NDNUM Guardian-first, transparency, privacy, impact, tour, press, partners, diaspora, and Layer 2 readiness.
Fallback is the technical promise of content
If API or D1 fails, the library must still be readable. Fallback is part of content strategy. It should not be thin fake data; it should be public content strong enough to stand when dynamic systems are not ready.
The library holds the DSTS voice
A website can have many routes, but the library is where the DSTS voice accumulates. The first 90 days do not need to be perfect, but they must be consistent.