> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/classic/addons/premium-themes/marvel/marvel-version-history.md).

# Marvel Version History

{% hint style="info" %}
Find your theme version by pressing the keyboard shortcut (**⌘ + ,**) while in RapidWeaver, selecting the "**Addons**" tab from the Preferences window, selecting the "**Themes**" sub-tab, and searching for "**Marvel**" in the search box.
{% endhint %}

**Version 1.0.7**

**Added**: Theme banner alt tag.

***

**Version 1.0.6**

**Added**: GDPR compliance.

***

**Version 1.0.5**

**Fixed**: Large drop shadows on blog entry images.

***

**Version 1.0.4**

**Fixed**: Minor fixes

***

**Version 1.0.3**

**Fixed**: Minor layout corrections

***

**Version 1.0.2**

**Added**: Basic site footer, can be toggled hide/show in the Styles > Theme Tools > Hide Footer

**Added**: Styles > Theme Tools > Disable Parallax Effect

***

**Version 1.0.1**

**Added**: 2nd level sub page parents within the slide out menu, are now functional, and include an arrow marker.

**Added**: Style > Theme Tools > Hide Site Title

**Fixed**: Style option, Header – Max Width: 700px

**Fixed**: Style option, Hide Link Hover Underline

***

**Version 1.0.0**

*Original theme release*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/classic/addons/premium-themes/marvel/marvel-version-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.