Planned |
### HTTP and HTTPS
diff --git a/docs/offline.md b/docs/offline.md
index 96665d4..8c61c42 100644
--- a/docs/offline.md
+++ b/docs/offline.md
@@ -1,33 +1,67 @@
---
layout: default
title: Offline Use
-nav_order: 4
-parent: Usage
-permalink: /docs/offline
+nav_order: 2
+parent: Loading Web Archives
+permalink: /docs/loading_offline
---
# Offline Use
+{: .no_toc }
+
+## ReplayWeb.page is available for offline use in several ways.
+{: .no_toc .text-delta }
+
+
+1.
+{:toc}
-ReplayWeb.page is available for offline use in several ways.
## ReplayWeb.page Offline Cache
-After ReplayWeb.page is loaded, it can automatically be used offline without requiring an internet connection.
+After ReplayWeb.page is loaded, it can automatically be used offline without requiring an Internet connection.
-If a connection is not available, all web archive already loaded will continue to be available.
+That's to say, once you have loaded ReplayWeb.page online (with an Internet connection), if an Internet connection is not available later on, all web archives already loaded will continue to be available because it's cached.
+
+To do this, https://replayweb.page/ in your Chrome browser, and the site will start loading local archives even without an Internet connection.
+
+
+
+
+ What's cache?
+
+
+ Cache is a temporary storage space in your browser that keeps certain files. Cached data is used to quickly load an application or website (like replayweb.page!) every time you log on.
+
+
-[Loading local archives](loading#loading-local-web-archives) should fully work without an internet connection.
## ReplayWeb.page as Progress Web App
ReplayWeb.page can also be installed as [Progressive Web App](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps) and be available as a standalone app on desktop and mobile.
-This is still experimental, but should provide the same behavior as regular https://replayweb.page/
+These type of apps use the same, current version of Chrome you normally use while searching or browsing the web. This is still experimental, but should provide the same behavior as regular https://replayweb.page/
+
+To do this, on the ReplayWeb.page site, you might have noticed a "new window icon" in your search bar. Clicking on this icon will open the progressive web app on your computer so you can use it offline.
+
+
+
+ What's a Progressive Web App?
+
+
+ Progressive Web Apps can be considered as a cross-platform app: part web and part native. PWAs are built on the web and has web features that make is faster and easier to discover and share. AND it also has native features that makes it better integrated with your operating system and allows you to install on your computer so that it works offline!
+
+
+
+
+
+
## ReplayWeb.page as Standalone Desktop (Electron) App
-ReplayWeb.page is also available as a standalone Electron App. In this mode, ReplayWeb.page
-ships its own version of Chrome.
+ReplayWeb.page is also available as a standalone Electron App. In this mode, ReplayWeb.page packages its own version of Chrome.
+
+To do this, go to our [GitHub repo for replayweb.page](https://github.com/webrecorder/replayweb.page) and scroll down to "what's in this repo" for [app releases](https://github.com/webrecorder/replayweb.page/releases). You can download as a .dmg (for Apple) or .exe (for Windows).
Although the Web Page/Progressive Web App versions have almost the same features, the standalone App is useful for two primary reasons:
@@ -39,3 +73,19 @@ Once loaded, ReplayWeb.page App can continue to load web archives from disk.
The desktop app fully replaces [Webrecorder Player](https://github.com/webrecorder/webrecorder-player)
When using [https://replayweb.page](https://replayweb.page), you may be asked to re-open a local file because a web site can not have persistent access to your file system.
+
+
+
+ What's a standalone desktop (Electron) app?
+
+
+ Electron is the framework being used for a native application. A standalone desktop app just means that you can download the application to your desktop and open it up whenever without Internet!
+
+
+
+
+
+
+Once an archive has successfully loaded, you will be redirected to the archive view from where you can explore the archive.
+
+Next: [Exploring the Archive](/docs/exploring)
diff --git a/docs/sharing.md b/docs/sharing.md
index 555e099..a397a3b 100644
--- a/docs/sharing.md
+++ b/docs/sharing.md
@@ -2,7 +2,6 @@
layout: default
title: Sharing Web Archives
nav_order: 3
-parent: Usage
permalink: /docs/sharing
---
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
new file mode 100644
index 0000000..6d38704
--- /dev/null
+++ b/docs/troubleshooting.md
@@ -0,0 +1,35 @@
+---
+layout: page
+title: Troubleshooting
+nav_order: 4
+description: Troubleshooting ReplayWeb.page
+permalink: /docs/troubleshooting
+
+---
+
+This section will be dedicated to common errors and issues that we’ve encountered during web archiving.
+
+### WARC file is too big / too slow / fails to load.
+#### Loading Large Files: Full vs On-Demand Loading
+
+Due to the nature of the WARC format, the entire file must be read on first use to generate an index.
+
+For WARC files **>25MB**, only the index is initially stored in the browser, and the actual content is loaded 'on-demand',
+when the content is first accessed. This leads to faster loading and saves memory when dealing with large archives, but the entire
+file must still be read.
+
+[Web Archive Collection (WACZ)](wacz-format) are always loaded on-demand, as no indexing is required.
+The initial archive view should load almost instantly as a result.
+
+We recommend converting larger WARC files to WACZ files.
+
+This is currently possible by using the `wacz` python library, see [py-wacz documentation](https://github.com/webrecorder/wacz-format/tree/main/py-wacz)
+for more info.
+
+While we've recently made improvements to large WARC loading, for very large files, this may still take some time and occasionally the browser may not load the full file.
+
+If an archive could not be loaded, an error will be displayed instead of the progress.
+Please report any issues encountered via [GitHub Issues](https://github.com/webrecorder/replayweb.page/issues)
+
+## Have another error or issue?
+Since we just launched, we’ll need your help with what we should troubleshoot! Please contact us and ask us questions and show us examples.
diff --git a/docs/usage.md b/docs/usage.md
index 5f22e1d..a3a990c 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -1,35 +1,26 @@
---
layout: default
-title: Usage
+title: Loading Web Archives
nav_order: 2
-description: About ReplayWeb.page
+description: How to use ReplayWeb.page
has_children: true
-permalink: /docs/index.html
+permalink: /docs/usage
---
-# Using ReplayWeb.Page
-## Serverless / Client-Side Web Archive Replay
+# How to use ReplayWeb.Page
+So you generated WARC files after capturing your website. Now what?
+At this point in your web archiving workflow, you'll most likely want to replay these WARC files.
-{: .fs-6 .fw-300 }
-ReplayWeb.page is an [open-source](https://github.com/webrecorder/replayweb.page) browser-based system to replay archived web pages as accurately as possible, with interactive elements preserved.
+This is where replayweb.page can be helpful for you! You can view your web archives either from various locations directly in the browser or offline on your computer.
-{: .fs-6 .fw-300 }
-Archives can be loaded as static files from anywhere a browser can connect to, or from users local machine.
+## Online Use
-{: .fs-6 .fw-300 }
-ReplayWeb.page provides the following features:
+Currently the easiest way to view your WARC and/or WACZ files is online through replayweb.page. You can load web archives locally from your computer or from other remote web archives. Check out [Online Use](/docs/loading_online) for more information how to load your web archives.
-- High-Fidelity replay of web archives in [several formats](formats) and from [various locations](locations) directly in the browser.
-
-- Several way to [explore web archives](explore): story view, page search and URL search.
-
-- On-demand, incremental [loading of large archives](loading#loading-large-files-full-vs-on-demand-loading/).
-
-- Several options for fully-functional [offline usage](offline).
-
-- Available as a standalone [desktop app](https://github.com/webrecorder/replayweb.page/releases) with Flash support.
-
-- Support for [versioned embedding of web archives](embedding).
+
+## Offline Use
+You can run replayweb.page on your computer by running it locally. And then you can load web archives the same way you would online. Check out [Offline Use](/docs/loading_offline) for more information how to load your web archives - offline.
+
diff --git a/docs/wacz-format.md b/docs/wacz-format.md
index cb36e44..b6d659b 100644
--- a/docs/wacz-format.md
+++ b/docs/wacz-format.md
@@ -1,6 +1,6 @@
---
layout: default
-title: 'Web Archive Collection Zipped (WACZ) Format'
+title: WACZ Format
nav_order: 1
permalink: /docs/wacz-format
parent: Reference