archivalo-oss/replayweb.page
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Minor docs updates & Link Updates (#361)

Browse Source 
### Changes
- Fix docs edit URL
- Update links to new webrecorder.net pages
This commit is contained in:
Henry Wilkinson
2024-11-01 09:43:27 -07:00
committed by GitHub
parent 4d02878c6b
commit 218c1ed14f
4 changed files with 5 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
mkdocs/site/docs/embedding/index.md
+1 -1
View File
@@ -106,7 +106,7 @@ For example, if you publish your JavaScript files at:
Then you must adjust your HTML to reference the new resources:
```html
<script src=""/js/ui.js""></script>
<script src="/js/ui.js"></script>
<replay-web-page replayBase="/js/" source="/wacz/example.wacz" url="https://webrecorder.net"></replay-web-page>
```
mkdocs/site/docs/user-guide/index.md
+1 -1
View File
@@ -7,7 +7,7 @@
## Supported Formats
While ReplayWeb.page aims to support a variety of formats for archived web content, for best performance we recommend using WACZ files. To archive webpages to WACZ files on a per-page basis, we recommend [ArchiveWeb.page](https://archiveweb.page). If you need to archive entire websites, check out [Browsertrix](https://browsertrix.com).
While ReplayWeb.page aims to support a variety of formats for archived web content, for best performance we recommend using WACZ files. To archive webpages to WACZ files on a per-page basis, we recommend [ArchiveWeb.page](https://webrecorder.net/archivewebpage). If you need to archive entire websites, check out [Browsertrix](https://webrecorder.net/browsertrix).
??? question "WARC? WACZ? What's the difference?"
Due to the nature of the WARC format, the entire file must be read on first use to generate an index — a list of all the pages and content available in the file used by ReplayWebpage to rebuild and display the archived content.