This repository was archived by the owner on Apr 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 48
Create 087-deprecating-the-old-docs-site.md #387
Closed
Closed
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
1fe8b68
Create 087-deprecating-the-old-docs-site.md
johnnymatthews a2812a5
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews f945728
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 01b08d0
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 42c9b66
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews a0cea9c
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews b2af309
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 06b9a05
Remove Netlify comments.
johnnymatthews 286e6cb
Formatting and grammar tweaks
jennwrites c442f1d
Fix typos. Add new docs link to intro paragraph.
johnnymatthews 10dbcb2
Not posting on April Fools Day.
johnnymatthews bede585
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 50a25cd
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 5947691
Specify nobody ends up on a 404.
johnnymatthews 644a2f5
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 9f6d353
Update content/post/087-deprecating-the-old-docs-site.md
johnnymatthews 26da3f5
Merge branch 'master' of https://github.com/johnnymatthews/blog-1
johnnymatthews 5464835
Link to GitHub, not HackMD.
johnnymatthews File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
--- | ||
date: 2020-04-03 | ||
url: 2020-04-01-deprecating-the-old-docs-site | ||
title: Deprecating the old docs site | ||
author: Johnny Matthews | ||
--- | ||
|
||
# Goodbye, IPFS legacy docs | ||
|
||
The IPFS team is deprecating the old documentation website. That’s just a fancy way of saying we’re replacing the current docs.ipfs.io website with the new [docs-beta.ipfs.io website](https://docs-beta.ipfs.io). | ||
|
||
## We built a new docs site | ||
|
||
A common complaint from users new and old was that the IPFS onboarding experience was rough - and that the documentation was particularly difficult to navigate to find fast, reliable answers. We set out to change that! Work on a new documentation site for IPFS started in Q3 of 2019. Before that, the docs site was built upon Hugo. While Hugo is an excellent static-site generator, it was missing some features around interactive content that we needed to adaptively respond to user needs and collect feedback on which pages to improve first. | ||
|
||
With that in mind, the IPFS docs and UX working group built a new site to host the documentation on VuePress. After finishing the new site towards the end of 2019, we ran an opt-in public beta to get feedback and continue making improvements throughout Q1. You can see a preview of the site at [docs-beta.ipfs.io](https://docs-beta.ipfs.io). | ||
|
||
## The deprecation plan | ||
|
||
We’ve built the site, put it online, and it’s been well received. Next comes the tricky part: removing the old website and putting this one in its place. | ||
|
||
Back in the early days of the internet, deprecating a site was as simple as putting up a notice saying things were going to be down for an hour or so, deleting everything in `/var/www/html`, and replacing it with the new website. Sadly, the good-old-days are gone, and we now live in a world full of checks, balances, and redirects. With that in mind, here is our plan to deprecate the old site and replace it with the new one. | ||
|
||
### Inform the world | ||
|
||
The first step is to let everyone know what we’re going to be doing. This post serves as part of the notification process, along with call-outs on the legacy site, and in the `ipfs/docs` GitHub repository. | ||
|
||
### Plan for redirects | ||
|
||
There have been several changes to the structure and naming conventions in the docs repo. Significant URL redirects must be put in place from legacy links to where the content now lives. This is to ensure that nobody ends up on a `404` page, and is always directed to the content that they want to see. | ||
|
||
### Update external services | ||
|
||
Tools like Google Analytics and Bing Webmaster all need to be informed of the changes. While they may not be major players in the decentralized web of tomorrow, for today at least, centralized search engines are still tools that help us reach people with IPFS questions and spread the word about the dweb. | ||
|
||
### Combine all the repos | ||
|
||
The IPFS docs have been stuck in limbo for a few months, with GitHub issues living in `ipfs/docs`, but the actual documentation and website content living in `ipfs/ipfs-docs-v2`. This has caused some confusion with posting and commenting upon issues in one repo while reflecting those changes in another. | ||
|
||
Part of our deprecation plan is to merge the *code* in `ipfs/ipfs-docs-v2` into `ipfs/docs`. All the legacy docs site content in `ipfs/docs` will be upgraded, but the issues will remain intact. Open issues will have their links checked to make sure they are referencing the correct and updated pages. | ||
|
||
### Follow-up | ||
|
||
This final task will take place around 6-12 weeks after the site deprecation. There are four things the docs team will need to focus on at this stage: | ||
|
||
1. Remove the _this URL has changed_ notices in any existing pages. | ||
2. Re-crawl the site to make sure all the links and references are still working and up to date. | ||
3. Check the top 404 referrers, and create a fix for them where possible. | ||
4. Search all content in the IPFS and Protocol Labs GitHub orgs for references to old site pages, and fix those (so we don’t 404 ourselves!). | ||
|
||
## And that’s it | ||
|
||
After these steps are complete, the docs site will be fully ready to help readers explore the wonderful world of the decentralized web! These deprecation steps are set to begin in April and should be finished by June 2020. You can take a look at [the full plan on GitHub.](https://github.com/ipfs/docs/issues/475). |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused about which docs you are referencing here (links to the docs-v2? links to ipfs.docs?) and also why we expect to be hitting so many 404s in our existing docs/orgs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new docs site. There's a plan to automate this step however, so this point isn't necessary.
If there are links coming in from external sites (other GitHub repos, tutorials, forum posts, etc) that are wrong, we can either redirect them to the homepage of docs, or redirect them to the most relevant page. Obviously the plan is to have no internal broken links.