We now have 659 Yenizens in the Yeniverse (as I am writing this blog post), which means our community has grown more than 50% since May 1st! I have only been working on this project for two months, and yet, it feels like we have already grown so much since I have started and I couldn’t be more excited for the future.
Brand development can be a nightmare for companies, especially startups. Where do you start? How do you know your brand identity is good? Does our brand properly reflect who we are as a company? These questions can cause headaches for anyone and they certainly have for us at YEN.
The team working on YEN is completely distributed, but that doesn’t mean that we do not like getting together in person every once and awhile, and we believe that our community would like more opportunities to do the same.
Just like an iceberg, there are so many things that we’re building and putting together for our community that doesn’t get a lot of air time (i.e. press)! In many ways, the team has been building not just one software product but two (or three!).
If you’ve been with us for a while, you’ll notice the posts from the past two years will look familiar. These are the actual posts one for one from our Patreon page which we closed at the end of 2018. We couldn’t have gotten to this point without the help and support from our patrons but we made the difficult decision to move on from Patreon to focus on our magnum opus, YEN.io.
If you’re just catching up, we thought the previous posts would be a neat way to share our background and our thought processes to everyone without any type of subscriptions. Take a look back and see how we developed CryptoYum, CoinPuffs, the Bitcoin Pub, and now Yen.io.
Besides, you don’t know where you’re going until you know where you’ve been. We’ll post any updates to our community and our efforts here so please bookmark and follow along!
There are times where we’re going to need to communicate important messages to our community and we’ve come up with a way to do that by putting it right into your canonical feed.
It should like like above and below you’ll see how it feels in the larger feed context:
There are so many different ways to do this, but, we opted to test out this way first. I like how it’s a slightly different color and that you can easily “X” it out (close it) if you’re done reading it.
Examples of site-wide notifications might include:
– Planned downtime for upgrading the system
– A new (and important) feature that was implemented (e.g. new security update)
– An outage at one of the exchanges that we’re connected to
– A new hardfork that has stopped certain trading for tokens (e.g. BCH / BCH ABC / BCH SV hardfork updates)
And things like that. We hope to implement this in the next few sprints!
This is our digital journal: A living, breathing, work-in-progress account of what it’s like to build community & product in the decentralized economy. It’s our attempt to more “evenly distribute” the future that’s already here. Join us!