> 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/developers/plugins/plugin-sdk.md).

# Plugin SDK

If you’d like to create your own native page types for RapidWeaver Classic you’ll need to use RWKit, it’s available on GitHub along with sample code to get you started. It also requires a Mac, a copy of Xcode and RapidWeaver Classic.

* [RWPluginKit on GitHub](https://github.com/realmacsoftware/RWPluginKit)

### Developer Support <a href="#developer-support-1" id="developer-support-1"></a>

If you have any questions on getting up and running, please email <support@realmacsoftware.com> or visit the [RapidWeaver Developer Network forum](https://forums.realmacsoftware.com/c/rapidweaver-developer-network/) group to ask any questions - we’re always happy to help!

### Sample Code <a href="#sample-code-2" id="sample-code-2"></a>

The Sample code below is a boilerplate RapidWeaver plugin to use as a starting point. It implements the minimum set of API, views, and icons. It’s a little outdated but it’s a starting point.

The sample plugin is built to be compatible with both ARM and intel.

* [Download RapidWeaver Classic Sample Plugin](https://www.realmacsoftware.com/downloads/developer/classic/rw8_sample_plugin.zip)
* [Download RapidWeaver Classic SDK](https://www.realmacsoftware.com/downloads/developer/classic/rw8_sdk.zip)


---

# 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/developers/plugins/plugin-sdk.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.