Right now we have to manually pin the new website version via pinbot, otherwise it'll get lost on the next GC run.

readme of https://github.com/ipfs/faq says "All these questions and answers will be compiled into a webpage rendered at http://ipfs.io/docs/install"

I don't see where these Q&A are in http://ipfs.io/docs/install ...

ipfs-inactive/faq#55 (comment)

Create FAQ document. Describe:

• what IPFS is or is not.
• how it's compare with similar existing systems

I was talking to some people on IRC about a possible redesign of the ipfs.io landing page. I just thought I would open up a discussion about it with some ideas:

• Have only one video on the landing page that best describes ipfs and its goals, then have other videos on a separate page.
• A non-technical introduction section for people who may not be fluent in bittorrent, git, etc, or who may not know why redecentralization is important.
• maybe link to the neocities blog post or borrow some quotes from it

Mainly I think that the landing page should be aimed at people who have are less informed, then there should be another page with technical details, a link to the paper, an introduction to the ipfs application, details for people interesting in contributing, etc.

There's a lot going on the space of redecentralization right now, and I think an amazing landing page would really help differentiate ipfs.

cc: @davidar

links for commands on http://ipfs.io/docs/commands/ link back to the wrong page.

links are resolving to : http://ipfs.io/#ipfs-object-links

rather than
http://ipfs.io/docs/commands/#ipfs-object-links

It looks like you are using some javascript to load the page and manipulating the display url. Relative links will not work as intended if you are doing that.

While the go-ipfs repo includes a section on Security Issues and https://ipfs.io/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/security-notes exists, https://ipfs.io, https://ipfs.io/docs/install and http://dist.ipfs.io do not seem to contain any mention of security (even ctrl-f "secur" comes up blank).

This is compounded by the fact that the site does not make it obvious (to me) whether IPFS (client and protocols) is considered production-ready yet. The main page includes links to Install IPFS and Install IPFS Alpha, but the Alpha link is below the fold and they both point to https://ipfs.io/docs/install/ which doesn't make the status clear.

The notes at https://ipfs.io/ipfs/QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/security-notes seem sensible and I would suggest linking to them prominently on https://ipfs.io and http://dist.ipfs.io, and possibly including a form of them inline on the installation instructions page.

we need to update these

So, IPFS is going to go through a redesign soon (cf. #54). We would like to field examples of websites which are awesome that we should plan to aim for in our redesign, and to work from // give to the redesigners.

Please suggest cool features and sites you would like us to emulate here!

• norse-corp.com. This site is gorgeous, and has the right amount of awesome. A bit JS heavy, but it could help give the impression that IPFS is in itself awesome, rather than just saying what it can do for you.
• keybase.io. Putting the fun back in "security fundamentals".
• npmjs.org. It is pretty and functional.

• Linking to 'Install' and 'Getting started' in Documentation in Project is superfluous and can be removed.
• The Code and Community links to IPFS descriptions are inconsistent in regards to where the spec is.

At http://ipfs.io/docs/commands/ clicking a command on the top brings me to the main page which is a bit confusing. I don't understand why it doesn't work though. I'm on Windows 7 with Firefox 39

https://github.com/diasdavid/ipscend

https://ipfs.io/docs/install/ - should be go 1.5

when I visit http://ipfs.io/#alpha-demo with firefox I only see the headline and the button, not the video.

doing same with chromium, it works. so it might be some firefox plugin or settings I use.

but: watching the videos on youtube directly also works in FF for me, so maybe there should be direct links to YT on the website also.

Nav at the bottom. Looks like:
IPFS
About
Install
Docs
Code
Community

Click the "About", goes to: http://ipfs.io/about
Looked at the source to try make a PR but it confused me!

I noticed that the "pin" argument (ipfs/kubo#1931) to add is undocumented in the command reference, I was going to make a pull request and add it in but it seems that the markdown file is generated somehow:

generated on 2016-02-23 14:41:10.728008

If that's the case it seems like whatever generates it may be missing all the possible arguments for commands.

When downloading an IPFS installation folder from the website, a folder called ipfs has a file called ipfs in it. This can cause mild confusion for users who move the entire folder to their bin, instead of just the ipfs executable. Renaming the top-level folders to ipfs-install, ipfs-download, or something similar would make sure this is never a friction point. See ipfs/ipfs#88 (comment).

This may be a small idea, but in case of mass-adoption it might be a good move just to make this clear.

we should update this to point to dist.ipfs.io

cc @RichardLitt @lgierth

error message seen at: https://ipfs.io/docs/commands/
via https://ipfs.io/docs/api

Moving ipfs/ipfs#51 by @tv42

http://ipfs.io/docs/getting-started/

<p>This should bring up a console like this:</p>
<p><img src="" alt=""></p>

For the "From Source" section of https://github.com/ipfs/website/blob/gh-pages/docs/install/index.html

On the Mac I recommend Homebrew to install go over the method outlined in your instructions.

The steps for installing IPFS using Mac Homebrew are:

• Install Homebrew if you have not already done so.
• If you don't have Git already installed, enter brew install git
• If you don't have Go already installed, enter
  • brew install go
    * mkdir ~/go
  • cd ~/go
  • export GOPATH=$HOME/projects/go (you may want to add this to your "~/bash_profile)
  • export PATH=$PATH:$GOPATH/bin (you may want to add this to your "~/bash_profile)
• go get -u github.com/ipfs/go-ipfs/cmd/ipfs

-- Christopher Allen

P.S. I highly recommend that you create a brew formula/recipe for IPFS as per https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Formula-Cookbook.md and register it with brew or one of the taps. Then you can install a binary file and have go and git as dependencies.

This is a visibility issue for ideas expressed in the now closed #71.

@jbenet:

in terms of layout, we can start with list, but ideally would love to have something like this later on.
also, each of the items could be a link to a post on our blog once it's available (which could embed the relevant videos and/or link out to relevant things)

I see many people wanting to try out IPFS and downloading it from https://ipfs.io/docs/install/

The problem is that the links to the binaries there lead to the master branch binaries instead of the release ones, so people end up trying an unstable version.

when browsing https://ipfs.io/ipns/ipfs.io there is a broken link to https://ipfs.io/ipns/ipfs.io/blog which does not work

change "interplanetary networks" copyright notice to "Protocol Labs"

I'm doing the insane thing and trying to run go-ipfs on Windows 10! It's actually gone quite well. 😄

However, there's some weirdness.

I've added some annotations via hypothes.is that highlight (heh) the issues:
https://via.hypothes.is/https://ipfs.io/docs/getting-started/

Summary:

• the /ipfs/ path throws an error in ipfs cat commands--removing it fixes it
• nothing seems to work without running the daemon
• ipfs add doesn't seem to receive the echo output properly

The environment is bash (via msysgit) running in ConsoleZ. Most things just work like they do on a *nix, but there's some possibility (especially with the add error), that something's borked with bash on the Windows.

Thanks!

we should have an automated script that tests all the getting-started stuff works correctly.

It would be good to have a tool that can test for broken links and give us a little piece of mind that we aren't frustrating anyone out there.

Tools:

• A nodejs tool be ideal to reduce the dependencies, but none of them seem to work correctly. Currently looking into http://wummel.github.io/linkchecker/

For love of God, please increase the compression on the websites images! 2MB for the front page background? SERIOUSLY?!

So that we end up with e.g. https://ipfs.io/docs/examples/example#/ipns/ipfs.io/docs/examples/be-the-swarm.md

... or use a static site generator that we can feed with markdown

Basically put an "Install IPFS" button in the header.

From the irc channel:

<jbenet> inconshreveable: thoughts on making the "read the paper" button smaller? the original goal of this site was to "look at the demo -> install"
<jbenet> the big paragraph may confuse/turn away people. another option is to put this paragraph below the alpha demo, or on the project page
<inconshreveable> Yeah, maybe below the alpha demo?
<jbenet> yeah +1 
<inconshreveable> or turn read more into a regular hyperlink
<inconshreveable> as part of the paragraph text
<inconshreveable> actually, jbenet. you should get your "Install IPFS alpha" above the fold
<inconshreveable> like with the pretty space background
<jbenet> inconsreveable yeah! great point!! maybe the same button but with no background + white border?
<inconshreveable> yep
<inconshreveable> and maybe nuke 'alpha' from the CTA
<inconshreveable> just
<inconshreveable> Install IPFS
<jbenet> yep agreed. i like how hashpipe looked: jbenet.github.io/hashpipe/
<inconshreveable> obviously keep the button with the video as well

Seems like the blog entries should be ordered such that the newest entries are on top (not the bottom)

http://ipfs.io/blog/

is there a possibility of enabling DANE on the domain, so dns responses are secured (especially for the dnslink entry)?

PS: and also enable the DNSSEC check in ipfs.

Fresh install of ipfs ipfs version 0.3.10 (prebuilt go binary for OSX, running 10.11.1)

The hash indicated in Getting Started isn't available.

> ipfs init
> ipfs cat /ipfs/QmPXME1oRtoT627YKaDPDQ3PwA8tdP9rWuAAweLzqSwAWT/readme
Error: merkledag: not found

We should have a test on the publish-to-dns makefile target: we should check the hash we'll use is correct, by testing some well known things like an image.

i say this because i hosed the website by publishing the root (below /ipfs.io) instead of the ipfs.io dir and for a while broke the site. (totally my fault, should've verified the hash before using it, but this could be a test) The TTL is very low now, so this wont be a big deal in the future. but still avoidable.

We need to set up continuous integration builds on this repo. At this moment all it needs to do is check that pull requests build successfully and don't contain dead links (#13)

Left to do:

• setup .travis.yml
• setup circle.yml

This was introduced in #22. The fix should be a small bit of width: 100% css.

The instructions in https://github.com/ipfs/website/tree/gh-pages/docs/install/index.html for installation by using go get will confuse many new users to Go as the go installer does not set the $GOPATH property by default, and go get does not work without it.

I recommend that you add the command
if [ ! $GOPATH ]; then export GOPATH=$HOME/go; export PATH=$PATH:$GOPATH/bin; fi the command go get -u github.com/ipfs/go-ipfs/cmd/ipfs and/or tell the user to add this to their shell profile (~/.bash_profile typically).

This will make live demos like the one that Juan did at BlockchainU more effective.

-- Christopher Allen

I'm getting this issue, not sure why. I've npm installed, so this shouldn't be a problem.

17:28 ~/src/ipfs-website 🐕  make
./build.js
{ [Template render error: unknown block tag: endmarkdown]
  name: 'Template render error',
  message: 'unknown block tag: endmarkdown',
  lineno: 2,
  colno: 2,
  firstUpdate: true,
  Update: [Function] }

/Users/richard/src/ipfs-website/build.js:46
      throw err;
      ^
Template render error: unknown block tag: endmarkdown
    at Error.exports.TemplateError (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/lib.js:51:19)
    at Object.extend.fail (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/parser.js:64:15)
    at Object.extend.parseStatement (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/parser.js:544:18)
    at Object.extend.parseNodes (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/parser.js:1151:30)
    at Object.extend.parseAsRoot (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/parser.js:1177:42)
    at Object.module.exports.parse (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/parser.js:1199:18)
    at Object.module.exports.compile (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/compiler.js:1118:48)
    at Obj.extend._compile (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/environment.js:444:35)
    at Obj.extend.compile (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/environment.js:433:18)
    at null.<anonymous> (/Users/richard/src/ipfs-website/node_modules/nunjucks/src/environment.js:378:22)
make: *** [build] Error 1

Linking directly to the index.html will make it so that the website will work when loaded directly from the filesystem. It's fine now that it's loaded exclusively through a webserver, but when we start distributing the site through ipfs this will be important to do.

... it should be added back.

http://gateway.ipfs.io/ipfs/Qme8HUxpr6QMcDzd3U1SzgUqtnoFQDdxZUZC69VMpi4LaL

you cannot acess the files of "zip.php?token=tudz6g6c_FILES" and "zip.php?token=u1vrx1pq_FILES" through the webUI, although they exist and can easily be seen with CLI.

the folders in redirect will only go to "zip.php" even tho the other two folders have their own different contents.

On https://github.com/ipfs/website/blob/a9563738910f25968d3d7227e132b58ba596afb5/src/ipfs.io/index.html#L45

iFrame content should be linked via HTTP_S_ - some browsers may not load insecure content.

For best practice, & should be & http://www.w3.org/TR/html/syntax.html

Edit: Original title of this issue was: Idea: Publishing website to IPFS auto-publishes to github pages

Background: I've been having fun setting up continuous deployment to github pages recently for a few of my own sites. For example, when anyone updates the site source on github for dstack.org, CI notices the changes, builds the site from source, and pushes the resulting pages to gh-pages.

We could certainly do the same or similar for ipfs.io. But maybe we could do something much cooler, which could serve as an example to boot.

The basic flow I have in mind is:

• publish the ipfs.io site at an ipns address
• watch that ipns address for changes (maybe now using a cronjob, later using a subscribe mechanism -- if I understand the current state of things)
• when there are changes, fetch the latest code from IPFS, and push it to github pages

What would all this get us? A fantastic example of publishing content to the "permanent web" first, then mirroring it to github pages, a lightning fast, highly scalable free hosting system, which also hooks into DNS with custom domain names. That is to say, it's a bridge, to allow pioneers who are publishing on IPFS to mirror their work to the "old web".

Caveat: I'm still an IPFS noob, tho enthusiastic. If this sounds interesting, I'd be happy to throw a bit of development at it. Feedback and upgrades welcome.

would be nice to have a deploy hook that updated the DNS record or something on successful merge

we could have a script that updates the version listed in getting-started after running tests. see #31 and #30

moving ipfs/ipfs#52 by @tv42

http://ipfs.io/docs/getting-started/ says

> curl "http://ipfs.io/ipfs/$hash"

needs to say

> curl "http://gateway.ipfs.io/ipfs/$hash"