Hi,

i just came by your webpage and saw that http://blockstream.com redirects directly to https://github.com/ElementsProject/elementsproject.github.io
instead of http://www.blockstream.com.

You are using cloudflare? Maybe this post helps: https://support.cloudflare.com/hc/en-us/articles/200172286-How-do-I-perform-URL-forwarding-or-redirects-with-CloudFlare-

Besides this, I would add the URL http://www.blockstream.com to the repository description here on github.

While following this helpful instructional (https://elementsproject.org/sidechains/alpha/getting-started.html), my machine did not have enough disk space to run the ./bitcoind ... command.

Instructions should indicate ahead of time how much disk space is required.

from the README.md:

"It's nice working on something without millions of BTCs resting on it, and still have a path to production use.”

Is there a clearer way to express this. I don't think most readers would easily understand the meaning.

I randomly choose @gmaxwell to come up with a better quote. He might be motivated because this quote somehow ended up below his picture, while it isn't clear where the quote originally came from.

It'd be nice to have all content available in multiple languages. This being a static site, we'll need to research how this would be done.

Perhaps like Bitcoin Core, we could use a service like Transifex to allow users to contribute translations.

Chainparams.cpp is misspelled on the sidechains guide on line 49. it's spelled chaimparmas.cpp.

in https://elementsproject.org/sidechains/

currently it's pointing to issuance-final.

What is the current status of payment protocol? We should make it work.

https://www.elementsproject.org/elements/bitmask-sighash-modes/

https://github.com/ElementsProject/elementsproject.org/edit/master/source/elements/bitmask-sighash-modes/index.md

Has a link to: https://github.com/ElementsProject/elements/tree/feature_bitmasksighash

Which is not found.

Hello, Elements Project community!

I'm starting a conversation about how to best manage contributions to the ElementsProject.org website. What is the most appropriate flow for a community-managed, content-oriented resource on the web?

Considerations should include how we manage content updates, bug and issue reports, tasks and resourcing, and who is able to merge (and who is expected to merge) pull requests.

Seeking opinions and discussion.

Due to having no scrolling horizontal bar on this page https://test.elementsproject.org/elements/confidential-transactions/ the TX code runs off the of the edge of the screen in browser (Chrome)

While testing locally (npm install, npm start), package.json modified itself:

   "hexo": {
-    "version": "3.2.2"
+    "version": "3.3.8"
   },
   "dependencies": {
     "hexo": "^3.1.0",

Not sure what to do about that...
More data:

$ npm -v
3.5.2
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04 LTS
Release:	16.04
Codename:	xenial

To help developers and writers contribute, we should make it very simple to run a local copy and see changes quickly. Live reload would be a good means for doing this.

The code on this page, defining the vars to create a sidechain isn't justified to be readable. It runs completely off to the side of the page. This can be fixed using a simple div tag or the like.