From f8459419dd9fa693ea21f8661433a393968ee166 Mon Sep 17 00:00:00 2001
From: Rob Brackett <rob@robbrackett.com>
Date: Tue, 7 Aug 2018 17:07:39 -0700
Subject: [PATCH 1/5] Add first draft of intro section 1 (what is IPFS)

This is a rewrite of 315ba7189ffb863717974bd9f3bfca1699d2b554 that fits with the new site organization (which wasn't fully baked when this draft was originally written).

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
---
 content/introduction/install.md    |  2 +-
 content/introduction/overview.md   | 86 ++++++++++++++++++++++++++++++
 content/introduction/usage.md      |  2 +-
 src/styles/components/article.less |  2 +-
 4 files changed, 89 insertions(+), 3 deletions(-)
 create mode 100644 content/introduction/overview.md

diff --git a/content/introduction/install.md b/content/introduction/install.md
index fe0c847..d50c2ef 100644
--- a/content/introduction/install.md
+++ b/content/introduction/install.md
@@ -1,6 +1,6 @@
 ---
 title: Install IPFS
-weight: 1
+weight: 2
 ---
 
 <!--
diff --git a/content/introduction/overview.md b/content/introduction/overview.md
new file mode 100644
index 0000000..42b08fa
--- /dev/null
+++ b/content/introduction/overview.md
@@ -0,0 +1,86 @@
+---
+title: What is IPFS?
+weight: 1
+---
+
+Welcome! If you’re new to IPFS, you’ve come to the right place. This guide is intended to give you a thorough but quick overview of what IPFS is, how it works, and how to use it.
+
+## IPFS is a distributed system for storing and accessing files, websites, applications, and data.
+
+What does that mean, exactly? Let’s say you’re doing some research on Aardvarks. (Just roll with it; Aardvarks are cool! Did you know they can tunnel 3 feet in only 5 minutes?) You might start by visiting the wikipedia page on Aardvarks at:
+
+```
+https://en.wikipedia.org/wiki/Aardvark
+```
+
+When you put that URL in your browser’s address bar, your computer asks one of Wikipedia’s computers, which might be somewhere on the other side of the country — or even the planet — for the Aardvark page. However, if you use IPFS to get that page from:
+
+```
+/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Aardvark.html
+```
+
+Your computer might have gotten it from someone else’s computer across town, or maybe even your neighbor’s computer across the street. When you use IPFS, you don’t only download a file from someone else, but your computer can help distribute it, too — when your friend a few blocks away needs the same Wikipedia page, they might be as likely to get it from you as your neighbor.
+
+IPFS makes this possible for web pages, but also for any kind of file a computer might store, whether it’s an MS Word document, an e-mail, an MP3 file, or even a database record.
+
+
+## So why does that matter?
+
+Making it possible to download a file from many locations that aren’t managed by one organization…
+
+- **Makes it hard for a website to go offline.** If someone attacks Wikipedia’s web servers or an engineer at Wikipedia makes a big mistake that causes their servers to catch fire, you can still get the same page from somewhere else.
+
+- **Makes it harder for authorities to censor content.** Because files on IPFS can come from many places and because some of those places might be nearby, it’s very hard for authorities (whether they’re states, corporations, or someone else) to block things. In 2017, Turkey blocked Wikipedia and Spain blocked access to Catalonian independence sites. We hope IPFS can prevent actions like those.
+
+- **Can speed up the web when you’re far away or disconnected.** If you can retrieve a file from someone nearby instead of hundreds or thousands of miles away, you can get it faster. (Organizations with enough money and expertise can do this with CDNs or multiple data centers, but IPFS aims to make this possible for everyone.) That’s especially valuable if your community is networked, but doesn’t have a good connection to the wider internet.
+
+That last point is actually where IPFS gets it’s name: **Inter-Planetary File System**! We’re striving to build a system that works across places as disconnected or far apart as other planets. That’s a pretty idealistic goal, but it keeps us working and thinking hard, and most everything we create in pursuit of that goal is also useful closer to home.
+
+
+## Links don’t change on IPFS.
+
+What about that link to the Aardvark page above? It looked pretty crazy:
+
+```
+/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Aardvark.html
+```
+
+That jumble of letters after `/ipfs/` is called a [*content identifier*]({{<relref "guides/concepts/cid.md">}}) and it’s how IPFS can get content from multiple places.
+
+Traditional URLs and file paths like…
+
+- `https://en.wikipedia.org/wiki/Aardvark`
+- `/Users/Alice/Documents/term_paper.doc`
+- `C:\Users\Joe\My Documents\project_sprint_presentation.ppt`
+
+…identify a file by *where it’s located* — what computer it’s on and where on that computer’s hard drive it is. That doesn’t work if the file is in many places, though, like your neighbor’s computer and your friend’s across town.
+
+Instead of being location-based, IPFS addresses a file by *what’s in it*, or by it’s *content*. The content identifier above is a *hash* of the content at that address, which means it’s also unique to that content, even though it’s [relatively] short. It also allows you to verify you got what you asked for — bad actors can’t just hand you content that doesn’t match. (If hashes are new to you, check out this article for good introduction: https://tiptopsecurity.com/what-is-cryptographic-hashing-md5-sha-and-more/)
+
+<aside class="alert alert-info">
+  Why do we say “content” instead of “files” or “web pages” here? In order to make the storage & transmission of data more efficient, IPFS can break files up in to many smaller pieces — which then means the system needs some metadata to tie them back together. An IPFS address can refer to the metadata of just a single piece of a file, a whole file, a directory, a whole website, or even other kinds of data. There’s no single kind of thing that content identifier identifies.
+</aside>
+
+Because the address of a file in IPFS is tied to the content itself, links in IPFS can’t be changed. For example…
+
+- If the text on a web page is changed, the new version gets a new, different link. If your favorite recipe site used to be in customary but recently switched to an unfamiliar metric system, your IPFS links will still point to the customary.
+
+- Content can’t be moved to a different address. If a company reorganizes their web site today, they could move a page from `http://mycompany.com/what_we_do` to `http://mycompany.com/services`. In IPFS, the old link you have would still point to the same content.
+
+- If someone removes a page entirely, you can still get it at the same address.
+
+It’s important to remember in all of these situations that it’s the address or link that doesn’t change. The IPFS network is a participatory and collaborative one — if nobody has the content identified by a given address, it won’t be available. On the other hand, content can’t be removed from IPFS so long as *someone* is interested enough to make it available, whether or not that person is the original author.
+
+
+## It’s all about possession and participation.
+
+While there is lots of complex technology in IPFS, the fundamental ideas are about changing how networks of people and computers communicate: while today’s world-wide-web is structured on *ownership* and *access*, where you get files from whoever owns them and they choose to grant you access, IPFS is based on the ideas of *possession* and *participation*, where many people have each others’ files and *participate* in making them available.
+
+That means IPFS only works well when people are actively participating. If you share a file on your computer, but then turn your computer off, other people won’t be able to access it from you. But if you or others make sure a copy of that file is stored on another computer running IPFS, it will be available more often. By default, your computer participates in sharing a file with others for a limited time after you’ve downloaded it with IPFS. You can *pin* a file to save and permanently share it.
+
+If you want to make sure one of your own files is permanently shared on the internet today, you might use a for-pay file-sharing service like Dropbox. Some people have begun offering similar services based on IPFS called *pinning services*. But since IPFS makes this kind of sharing a built-in feature, you can also collaborate with friends or partner with institutions (for example, museums and libraries might work together) to share each others’ files. We hope IPFS can be the low-level tool that allows a rich fabric of communities, business, and cooperative organizations to all form a distributed web that is much more reliable, robust, and equitable than the one we have today.
+
+
+## Next Steps
+
+Sounds interesting? We’ll cover [how to use it]({{<relref "introduction/usage.md">}}) next.
diff --git a/content/introduction/usage.md b/content/introduction/usage.md
index d419f5c..d1312b7 100644
--- a/content/introduction/usage.md
+++ b/content/introduction/usage.md
@@ -1,6 +1,6 @@
 ---
 title: Basic Usage
-weight: 2
+weight: 3
 ---
 
 If you haven't done so, [install IPFS](../install).
diff --git a/src/styles/components/article.less b/src/styles/components/article.less
index fb8004a..032ac9e 100644
--- a/src/styles/components/article.less
+++ b/src/styles/components/article.less
@@ -2,7 +2,7 @@
   line-height: 1.4;
 
   & > * {
-    max-width: 50em;
+    max-width: 50rem;
   }
 
   // Allow certain types of content to extend past normal text bounds

From 0e5b04daa4754ab2db7a2b5430eef280035274e0 Mon Sep 17 00:00:00 2001
From: Rob Brackett <rob@robbrackett.com>
Date: Tue, 7 Aug 2018 17:10:52 -0700
Subject: [PATCH 2/5] Change hashes link to our new concepts doc

We didn't have our own documentation on hashes when this document was originally written. Now we do, so link to it!

License: MIT
Signed-off-by: Rob Brackett <rob@robbrackett.com>
---
 content/introduction/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/introduction/overview.md b/content/introduction/overview.md
index 42b08fa..bd75158 100644
--- a/content/introduction/overview.md
+++ b/content/introduction/overview.md
@@ -55,7 +55,7 @@ Traditional URLs and file paths like…
 
 …identify a file by *where it’s located* — what computer it’s on and where on that computer’s hard drive it is. That doesn’t work if the file is in many places, though, like your neighbor’s computer and your friend’s across town.
 
-Instead of being location-based, IPFS addresses a file by *what’s in it*, or by it’s *content*. The content identifier above is a *hash* of the content at that address, which means it’s also unique to that content, even though it’s [relatively] short. It also allows you to verify you got what you asked for — bad actors can’t just hand you content that doesn’t match. (If hashes are new to you, check out this article for good introduction: https://tiptopsecurity.com/what-is-cryptographic-hashing-md5-sha-and-more/)
+Instead of being location-based, IPFS addresses a file by *what’s in it*, or by it’s *content*. The content identifier above is a *hash* of the content at that address, which means it’s also unique to that content, even though it’s [relatively] short. It also allows you to verify you got what you asked for — bad actors can’t just hand you content that doesn’t match. (If hashes are new to you, check out [the concept guide on hashes]({{<relref "guides/concepts/hashes.md">}}) for a good introduction.)
 
 <aside class="alert alert-info">
   Why do we say “content” instead of “files” or “web pages” here? In order to make the storage & transmission of data more efficient, IPFS can break files up in to many smaller pieces — which then means the system needs some metadata to tie them back together. An IPFS address can refer to the metadata of just a single piece of a file, a whole file, a directory, a whole website, or even other kinds of data. There’s no single kind of thing that content identifier identifies.

From 51b36abe09a2e7149cf5cb0ec9ef299080e90101 Mon Sep 17 00:00:00 2001
From: Oli Evans <oli@tableflip.io>
Date: Mon, 3 Dec 2018 15:00:20 -0800
Subject: [PATCH 3/5] Re-order description of content to be clearer

Co-Authored-By: Mr0grog <rob@robbrackett.com>
---
 content/introduction/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/introduction/overview.md b/content/introduction/overview.md
index bd75158..a2d506d 100644
--- a/content/introduction/overview.md
+++ b/content/introduction/overview.md
@@ -58,7 +58,7 @@ Traditional URLs and file paths like…
 Instead of being location-based, IPFS addresses a file by *what’s in it*, or by it’s *content*. The content identifier above is a *hash* of the content at that address, which means it’s also unique to that content, even though it’s [relatively] short. It also allows you to verify you got what you asked for — bad actors can’t just hand you content that doesn’t match. (If hashes are new to you, check out [the concept guide on hashes]({{<relref "guides/concepts/hashes.md">}}) for a good introduction.)
 
 <aside class="alert alert-info">
-  Why do we say “content” instead of “files” or “web pages” here? In order to make the storage & transmission of data more efficient, IPFS can break files up in to many smaller pieces — which then means the system needs some metadata to tie them back together. An IPFS address can refer to the metadata of just a single piece of a file, a whole file, a directory, a whole website, or even other kinds of data. There’s no single kind of thing that content identifier identifies.
+  Why do we say “content” instead of “files” or “web pages” here? Because a content identifier can point to many different types of data. In order to make the storage & transmission of data more efficient, IPFS can break files up in to many smaller pieces — which then means the system needs some metadata to tie them back together. An IPFS address can refer to the metadata of just a single piece of a file, a whole file, a directory, a whole website, or even other kinds of data.
 </aside>
 
 Because the address of a file in IPFS is tied to the content itself, links in IPFS can’t be changed. For example…

From 4343df7e0054e5dcf61588fda27da98a0979aea9 Mon Sep 17 00:00:00 2001
From: Oli Evans <oli@tableflip.io>
Date: Mon, 3 Dec 2018 15:01:11 -0800
Subject: [PATCH 4/5] =?UTF-8?q?=E2=80=9CCrazy=E2=80=9D=20is=20not=20a=20gr?=
 =?UTF-8?q?eat=20descriptor=20to=20use=20for=20most=20anything?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Co-Authored-By: Mr0grog <rob@robbrackett.com>
---
 content/introduction/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/introduction/overview.md b/content/introduction/overview.md
index a2d506d..2989197 100644
--- a/content/introduction/overview.md
+++ b/content/introduction/overview.md
@@ -39,7 +39,7 @@ That last point is actually where IPFS gets it’s name: **Inter-Planetary File
 
 ## Links don’t change on IPFS.
 
-What about that link to the Aardvark page above? It looked pretty crazy:
+What about that link to the Aardvark page above? It looked a little unusual:
 
 ```
 /ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Aardvark.html

From 623d02d004e325c59ca7e9a2796244562094945f Mon Sep 17 00:00:00 2001
From: Oli Evans <oli@tableflip.io>
Date: Mon, 3 Dec 2018 15:02:03 -0800
Subject: [PATCH 5/5] Be less United Statesian

Co-Authored-By: Mr0grog <rob@robbrackett.com>
---
 content/introduction/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/introduction/overview.md b/content/introduction/overview.md
index 2989197..69b61a0 100644
--- a/content/introduction/overview.md
+++ b/content/introduction/overview.md
@@ -63,7 +63,7 @@ Instead of being location-based, IPFS addresses a file by *what’s in it*, or b
 
 Because the address of a file in IPFS is tied to the content itself, links in IPFS can’t be changed. For example…
 
-- If the text on a web page is changed, the new version gets a new, different link. If your favorite recipe site used to be in customary but recently switched to an unfamiliar metric system, your IPFS links will still point to the customary.
+- If the text on a web page is changed, the new version gets a new, different link. If your favorite cooking site changes how they layout recipes your IPFS links will still point to the old version.
 
 - Content can’t be moved to a different address. If a company reorganizes their web site today, they could move a page from `http://mycompany.com/what_we_do` to `http://mycompany.com/services`. In IPFS, the old link you have would still point to the same content.