Summary
The architecture concept page (concepts/architecture.md) is around 145 words. It names three components and gives each about two sentences. Expand it into a page that actually explains how Web3Signer works.
Current state
The page lists a remote signer, a slashing database, and the APIs, and describes each briefly. It carries no diagram.
Why this is needed
The architecture page is one of the first pages a reader opens when deciding whether Web3Signer fits their setup, and it is the page most likely to be quoted or referenced elsewhere. At its current depth it cannot do that job.
It also cannot support the pages that should build on it. Any explanation of the security model needs an established trust boundary to refer to, and any guidance on running multiple instances needs an established coordination model. Neither exists on the page today, so each of those topics has to start from scratch.
Summary
The architecture concept page (
concepts/architecture.md) is around 145 words. It names three components and gives each about two sentences. Expand it into a page that actually explains how Web3Signer works.Current state
The page lists a remote signer, a slashing database, and the APIs, and describes each briefly. It carries no diagram.
Why this is needed
The architecture page is one of the first pages a reader opens when deciding whether Web3Signer fits their setup, and it is the page most likely to be quoted or referenced elsewhere. At its current depth it cannot do that job.
It also cannot support the pages that should build on it. Any explanation of the security model needs an established trust boundary to refer to, and any guidance on running multiple instances needs an established coordination model. Neither exists on the page today, so each of those topics has to start from scratch.