Blog will be used for articles about local-first software, P2P networking and miscellaneous stuff.

It should be possible to donate using:

• Patreon
• Buy me a coffee
• Bitcoin/Ethereum/USDT/USDC/Polkadot/Cosmos

Documentation is what AdiDoks was really created for. We will draft docs in Notion and publish to our website. When we'll have a lot of docs, we'll need clear summary of AdiDoks features dedicated to navigating the docs.

I've decided to give justification a shot, in our blog: https://www.ark-builders.dev/blog/

It's important to make spaces between words look nice, because text justification is considered bad when used on web-pages. See more about this:
https://www.changedetect.com/how-to-justify-text/
https://maxwellforbes.com/posts/web-justified-text/

However, it could be alright when used together with hyphenation. We need to verify that it looks OK on all devices. If it doesn't, we should turn it off.

Rate | ARK Builders

is must-have if you travel a lot. Convert several currencies into set of others in one go.

https://www.ark-builders.dev/apps/rate/

We need a blog post answering these questions:

1. What problem are we trying to solve with our P2P lib?
2. What technical challenges do we have to overcome to solve it?
3. What options did we evaluate?
4. What main tradeoffs did we consider?
5. What did we choose in the end, and how will we move forward?

Preliminary answers:

1. Direct communication between any two users and/or devices.
2. Scalable solution requires hole-punching as relay servers don't scale.
3. a. Using LibP2P.
   b. Using WebRTC.
   c. Adapting Syncthing or Nebula.
   d. Writing custom code.

Our project has similar goals to what is described as "Local-first Software". Let's write something to show where our goals are similar and how do we want to achieve these goals.

We should embed nice looking buttons leading to Play Store for the published apps.

The plain APK download button should be kept near, but we need to improve its image.

Contribute section should aggregate open issues from different repos of our organization.

Developers looking for a challenge should be able to see all issues labeled as good first issue and bug. We can consider also enabling them to see aggregated lists of issues labeled as enhancement or feature.

As a bonus feature, we could even create our own bounty tracker! We have label bounty in several repos, but right now it's only used for setting a bounty before-hand. We could have separate display for more challenging issues, which must be paid upon successful implementation.

We need Research link in the top menu. Somewhere between Blog and Contribute.

The link itself will lead to our Notion: https://ark-builders.notion.site/Research-0e9029fa5e704ddfa8b6786b794a2f17?pvs=4