You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Revise website for a possible first experimental release for low-key testing and feedback #162
Good progress is happening on feature and design implementation. There was a brief exchange in the Signal group (via @johnny9) that we might get to a point soon where we want to invite more people for early testing, and restructuring the home page accordingly. I'd like to use this issue to plan this out.
I'll probably make a few assumptions here that need to be corrected, but here we go...
The situation
We (will) have decent (not perfect) implementations of all the 1.x milestone features and UX. It's at a point where feedback becomes useful and valuable in order to adjust direction before committing to finalizing and polishing.
The need
We want to have a dedicated landing page for people to download this early experimental release, understanding what it is and what it isn't, how to download, run, test and give feedback. These visitors are likely less interested in the nitty-gritty milestone and design system content.
1. Move all the project/design/milestone documentation to a sub section, including the sidebar/menu navigation
2. Keep the "Provide early feedback" section, but revise it to fit our 1.x experimental release info
3. Add a proper project intro and status info at the top
4. [Optional] Create a test guide [like Arké has](https://arke.cash/test/). This will ideally result in much better structured feedback
I have been thinking about this a bit more and I think your proposed changes are what we need to do. I am thinking about making the documentation section of the website be a sort of final piece of our "definition of done" that we need to do before v1.0 merge into main.
Current Topic / Area
Suggested User-Facing Name
Notes
First Run, Runtime Messages, and App Shell
Get Started and App Basics
Better user-facing name. Includes first launch, app navigation, status bar, notifications, runtime warnings/questions.
Node Operations, Peers, and Diagnostics
Run and Monitor Your Node
Good fit. Include block sync, storage, connections, peers, bans, traffic, console/debug tools.
Wallet Creation and Lifecycle
Create and Manage Wallets
Good fit. Include create wallet, watch-only creation, open/switch/close wallets.
Wallet Recovery, Migration, and Security
Secure, Back Up, and Restore Wallets
Good fit. Security/recovery are user goals and should be documented together.
Wallet Overview and Activity
View Balances and Activity
Good fit. Include overview, transaction history, transaction details, export, speed up/abandon from activity.
Addresses, Contacts, and Message Signing
Manage Addresses and Contacts
Mostly good, but message signing may deserve a subsection called Sign and Verify Messages.
Receive Funds and Payment Requests
Receive Bitcoin
Strong fit.
Send Funds
Send Bitcoin
Strong fit. Include RBF, PSBT, watch-only send, coin selection, fees.
External Signing
Use External Signers
Good as its own guide because it spans create, settings, receive verification, send signing.
Settings, Help, Display, and Localization
Settings and Help
Good fit.
This would be the highest level of the documentation pages and each subsection would contain basic userflow instructions with screenshots from the application.
Example under Send Bitcoin:
Basic send
Send to multiple recipients
Choose fees
Use RBF for a new transaction
Speed up a transaction from Activity
Select coins
Send from a watch-only wallet by saving/copying PSBT
Load, inspect, sign, broadcast, copy, or save a PSBT
Activity
johnny9 commentedon May 1, 2026
I have been thinking about this a bit more and I think your proposed changes are what we need to do. I am thinking about making the documentation section of the website be a sort of final piece of our "definition of done" that we need to do before v1.0 merge into main.
This would be the highest level of the documentation pages and each subsection would contain basic userflow instructions with screenshots from the application.
Example under Send Bitcoin: