> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/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/elements-docs/choosing-and-switching/why-elements.md).

# Why Elements?

Discover why Elements is a modern way to build websites on your Mac

RapidWeaver Elements is a modern, Mac-native way to design, build and publish websites.

### Explore the Approach

* [Static Website Benefits](/elements-docs/choosing-and-switching/why-elements/static-website-benefits.md) — Learn why static sites can be fast, secure, portable, and straightforward to host.
* [Build a Digital Garden](/elements-docs/choosing-and-switching/why-elements/build-a-digital-garden.md) — Create a personal space for connected ideas and evolving content.

### Elements Is Community-driven

We listen to our [community of passionate users](https://forums.realmacsoftware.com) and use their feedback to help shape Elements.

1. Regular builds and development videos keep the community informed.
2. Owning a website helps you participate in the independent web instead of relying entirely on social media.
3. Static websites are fast, secure and easy to host, while PHP remains available when you need it.
4. An active, supportive community can help with questions and ideas.
5. Friendly product support is available when you need it.

### Join the Independent Web

**Be part of the independent web. Own your content.**

Realmac Software has always been an independent company and has never taken outside investment. For more than 20 years, we have remained privately owned, customer-funded and customer-focused.

We believe the web should remain open and independent. When you publish something on the web, it should [belong to you](https://indieweb.org/own_your_data), not a corporation. By joining the [indie web movement](https://indieweb.org/IndieWeb) and using [RapidWeaver Elements](https://www.realmacsoftware.com/rapidweaver/elements/), **you retain control of your content.**

You can publish in the format that suits your content and share clear links such as `example.com/ideas`. These links can remain [permanent](https://indieweb.org/permalinks) as your site evolves.

**Take back control and build your next website with** [**Elements**](https://www.realmacsoftware.com/rapidweaver/elements/) **on macOS.**

#### Further Reading

* [Seven Reasons for having a Personal Website](https://cheapskatesguide.org/articles/why-have-a-personal-website.html)\
  Maintaining my own personal website has been one of the most amazing, challenging, rewarding, growth-promoting, time-consuming, and adventurous experiences of my life.
* [For the Love of God, Make Your Own Website](https://aftermath.site/website-musk-twitter-facebook-internet)\
  The internet sucks now--but it doesn't have to.
* [You should have a website](https://nora.zone/manifesto.html)\
  You already have a social media account. But you should also have a personal website.
* [Autonomy Online: A Case For The IndieWeb](https://www.smashingmagazine.com/2020/08/autonomy-online-indieweb/)\
  One of the principles of the IndieWeb is that you own your content
* [This Page is Under Construction](https://localghost.dev/blog/this-page-is-under-construction/)\
  A love letter to the personal website.


---

# 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/elements-docs/choosing-and-switching/why-elements.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.