Website Updates


That looks awesome! Like the font and the principles layout. Love :smiling_face_with_three_hearts: that Status being Open Source has found a prominent spot. In 1:1 testing I noticed that with all the new lingo of decentralization, web3, cryptocurrency and blockchain, Open Source DOES ring a bell and is appreciated.


@jonathan should we set up a few different copy reviews, e.g. one with someone familiar with our protocol, one for browser/wallet/UI, etc. to step through the relevant sections together? I’ve made a few suggestions on the right in this spreadsheet but have more to do and it will require checking. I think it might actually be most effective to collaborate in real time.


@rachel - this would be a great idea.

All copy from the copy doc is now reflected on the staging site here

Im hoping to have have copy and asset reviews complete by Wednesday so we can finally push this live.

If you feel dedicated copy reviews are needed, I am open to that but I think we mostly just need to review for technical accuracy. A lot of the content across the site is fairly high level and written in a specific tone. So perhaps we can have teams review the features copy on both the homepage and features page. WDYT?


I think a quick review async will work fine.

Can you guys (tagged below) please do me a huge favor and review the following pages for technical accuracy. I wrote much of the copy based on existing material in the docs and various posts on our blog. However, before this site goes live, I’d like a final review to ensure there are NO false/inaccurate statements. Its really not much copy so shouldnt take long at all:

Please remember, much of the copy on these “marketing” pages are designed to provide basic info for interested viewers and then drive to the related docs, blog posts, tutorials, etc, for more info.

Please leave any notes or comments in this copy deck in a new column to the right next to each section:

@julien - browser copy
@goranjovic - wallet copy
@igor - general app, protocol copy
@yenda - whisper/messenger copy
@petty - security copy

Im hoping to have all copy final by end of day Wednesday so we can launch on Thursday.


Awesome job @jonathan !

A couple comments:

  • wallet doesn’t support all ERC721 but only a handful (i.e. 4). Adding extra ones requires new dev
  • same for ERC20 except we support much more oob and it’s much simpler to add extra ones

This statement is a bit confusing: Extensions allow you to leverage the native of features of Status within your DApp.
Extensions won’t let you leverage Status features in your DApp. More the other way around actually: leverage your DApp feature within Status.
Note that we also offer extra APIs on top of web3, Status API. Those match more closely the original description.


one annoying thing
submenu disappears if move mouse in this direction


Love the new website. A couple of very minor issues in the About tab:

  1. Missing a quotation mark at the end of Jarrad’s sentence.


  1. There should be a space between VIII and Inclusivity



Speaking of this mission statement, @jarradhope have you read this post by Virgil on Tor and their branding? Might be worth considering IMO


and what is your answer to calling the protocol family big brother? isn’t that going to get someone killed for upholding things that are not human-rights related (as defined by Virgil)


I don’t have a good one. It might be a bad name (Poe’s law, etc). I agree the title is clickbaity.


On (same on )

  1. Tutorial’s title is not listed in the content
  2. Pictures are not shown at the end of the page

#57 has no link to in the sentence

“Warning: Nightly builds are intended for development testing and may include bugs and other issues. You might want to use the stable builds instead.”

It’s expected that “stable builds” will link to page



On Desktop picture is too wide on mobile portrait (iphone 7, safari):



In says

Full support for all ERC20 and ERC721 tokens on Ethereum network. Send, store, and receive your tokens or collectibles confidently in Status.

Collectibles can’t be sent directly from wallet. They can be viewed and as Julien said, if they are among the selected few collectibles integrated with the app.


On the same page, screenshot on the right side displays a transaction overview from a design which hasn’t been included in the app release. It should (probably?) display a screen as it is in the current version of the app.


@jonathan there are ~300 broken links on staging (I’ve shared complete list in email to you). Some can be like example links that should not work but some are really broken ones


Also, under Safe Wallet:

No intermediaries means you are in total control of your funds.

Is “no intermediaries” really true, strictly speaking, if our default network connection goes through a remote RPC?

I agree with “you are in total control of your funds” in the sense that nobody can take away your money, as emphasized in the next sentence:

You and only you hold your private keys meaning nobody can access your cryptocurrency.

But reliance on an “intermediary” RPC can help restrict your access to the funds. Am I in full control of my assets if an ISP can shut down access to the service that allows me to send/receive/exchange it?

Again, I understand that this was meant in the “nobody can take it away from you” sense, but mentioning both no intermediaries and total control in the same sentence seems misleading in the second sense, too. Any way to reword it maybe?


@anna - thank you so much for the review! I dropped the ball on this and didnt properly plan QA. I have gone through your comments above and am tasking Christi with the edits we can make (i.e. know broken links, including links to stable builds page, image resize on mobile).

A majority of the broken links were on the page as there was a mistake when linking to the core contributor Github and Status profiles. @jakubgs has implemented a fix which should remedy 125 broken links.

most of the other broken links are coming from the docs pages. Docs was out of scope for this project so we simply replicated what was in the current docs into the new design/layout. Therefore anything broken on is currently broken on production. Docs is one of the next projects we really need to take on.

@goranjovic - thank you very much for the review. Ive made some edits in the copy spreadsheet. I have made the claims far less bold and rather opaque as to not make any false claims. Will also update the asset.

Once we make these edits, I suggest a window of QA for any more broken issues. Then we deploy next week. Once again, truly sorry for not accounting for proper QA on this.

Sound good? Also - we are discussing in #status-web-design


ok, providing my feedback in #status-web-design and thanks @jonathan the new site looks great!


looks amazing. great work guise!