Closed harding closed 1 year ago
Thanks to @GBKS for suggesting the updated terms used in this PR, "full wallet" for a full node backed wallet, "light wallet" for a wallet using some variation of simplified verification, and "wallet service" for custodial wallets where users trust a remote service to protect their funds. Also thanks to the other members of the Bitcoin Design Community's Slack for putting up with my strange request for help with approachable terminology.
Concept ACK.
How to navigate to the Features page from the main one?
@hebasto
How to navigate to the Features page from the main one?
This is what I meant in the OP about it being an "orphan page [...] with no links from elsewhere on the site". I don't want to add links from the main page to this content until we've added additional content, such as a page about the privacy benefits of Bitcoin Core. In a later PR, I expect to link from the main page to the features page with something like this:
Until then, the only way you'll be able to navigate is by appending /en/features/
to the main page URL in your browser.
Please ping me when you'd like me to re-ACK !
ACK, thanks for adding this, needs rebase in _data/translations.yml
apparently!
hell of a piece of work
Preview: http://dg2.dtrt.org/en/features/
Continuing the series started with #783, this PR adds the first of a set of pages about the benefits of using Bitcoin Core for your own received transactions. A Features page is added that links to a Verification page about the benefits of verification. That page has a few sub-pages about specific attacks Bitcoin Core helps protected against. This is adapted and updated from content I originally wrote for the Bitcoin Core section of Bitcoin.org in 2015. https://web.archive.org/web/20150929204455/https://bitcoin.org/en/bitcoin-core/features/validation
The pages added in this PR are orphans---we don't add links to them from anywhere on the site. This is deliberate so that we can develop this content in small PRs and only link to them from the homepage when everything is finished. For that reason, this PR also has no dependencies on #783 , although there might be some slight merge conflicts there regarding shared CSS definitions.