At the moment, I don't think we have one.

Montserrat, and purple.

Steps to reproduce:

1. First fix a dependency issue (committed here)
2. Run npx gulp

 orbitdb.org/  $ npx gulp
[11:08:20] Using gulpfile ~/Projects/orbitdb/orbitdb.org/gulpfile.js
[11:08:20] Starting 'img'...
[11:08:20] Starting 'js'...

events.js:186
      throw er; // Unhandled 'error' event
      ^
[PluginError: Error: write EPIPE] {
  message: 'Error: write EPIPE',
  plugin: 'gulp-gm',
  showProperties: true,
  showStack: false,
  __safety: { toString: [Function: bound ] }
}

After looking at https://orbitdb.org/ front page a few times now, I think it is missing a visible link to https://github.com/orbitdb. Similar to IPFS and IPFS pubsub. Today the only GH link I can find is in the GH icon at the bottom of the page.

Do you think it would be beneficial to link the first "OrbitDB" in the first paragraph to https://orbitdb.org/?

I am personally against enabling Disqus, but it is something to think about. I think we should keep conversation on Gitter and GitHub, and leave the blog basically as a static site without having people feel the need to check in and comment on stuff there.

Currently a work in progress.

We may need one of these to be GDPR compliant or just in general, but I always find them tedious to write and institute. Perhaps we should just copy the Haja privacy policy and change the names of Haja Networks Oy to OrbitDB community, who will be in charge of this website anyway.

Do we want to have Google Analytics on this website? Does that send the wrong message?

https://docs.opencollective.com/help/collectives/embed-contribution-flow

Both to the main page and also as the social media twitter card image.

hey! i clicked through the link and the demo appears to be broken - tested in Firefox nightly, Canary and Brave nightly.

The community page for orbitdb.org has a link to github issues for call announcements which is broken

https://orbitdb.org/community/

https://twitter.com/orbit_db

Right now, the file was manualy edited to include the main page. We'll need it to automatically change for each new blogpost and so on.