> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/faq/how-to-change-default-view-in-exported-web-archive.md).
# How to change default view in exported web archive
In order to change the default view in exported web archive, first thing you need to do is to find the *views-list.js* file which is located inside of db folder: *DESTINATION\_FOLDER\YOUR\_DATABASE\_ID\db*. You can open it any text editor, it should look like this:
In this web archive the default view is "*NFL\\\Conferences*". We can see that because the value of "*is\_default"* is set to *true.* Let's say we want the view *"NFL\\\Superbowl stats"* to be default. We need to change the value of *"is\_default"* in the view "*NFL\\\Conferences"* to *false* and set the value of *"is\_default"* in the view "*NFL\\\Superbowl stats"* to *true*. File *views-list.js* should now look like this:
Save the file, reopen your web archive in the browser and now when you open the database the default view will be "*NFL\\\Superbowl stats*".
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.swingsoftware.com/seascape-for-notes/faq/how-to-change-default-view-in-exported-web-archive.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.