This directory is the public download source for MacPad Pro extensions.
MacPad Pro reads:
https://raw.githubusercontent.com/anvilfilbert/MacPadPro/main/RepositoryExtensions/catalog.json
Each extension has one directory:
RepositoryExtensions/<extension-id>/<extension-id>.macpadproext
Extensions can include extra package-owned files in the same directory. Script text-command extensions use:
RepositoryExtensions/<extension-id>/transform.js
The manifest must include scriptCommand.sourceURL and scriptCommand.sourceSHA256 so Extension Manager can download and verify the script before saving it locally.
Data-driven extensions can declare verified resource files:
{
"resources": [
{
"file": "themes.json",
"sourceURL": "https://raw.githubusercontent.com/anvilfilbert/MacPadPro/main/RepositoryExtensions/pro-themes/themes.json",
"sourceSHA256": "..."
}
]
}Theme packages also declare the resource that contains color definitions:
{
"themeResource": {
"file": "themes.json"
}
}The .macpadproext manifest must match the catalog entry exactly:
idtitledescriptionversionkind
Manifests can also include compatibility metadata:
packageFormatVersionminimumMacPadProVersion
If any value differs, Extension Manager rejects the package.
Extension Manager also displays optional trust metadata:
authorpermissions
Installed packages show Update Available when this catalog publishes a newer semantic version than the local package.
Use these terms in extension descriptions when relevant so users can find packages through Extension Manager search:
- markdown
- preview
- export
- html
- rtf
- statistics
- diff
- backup
- versions
- clipboard
- snippets
- outline
- navigation
- csv
- tsv
- table
- encoding
- line endings
- focus mode
- themes
- formatter
- php
- c++
- json
- ai agent
- ollama
- openrouter
- javascript
- script command
- title case
- Add source under
Sources/NotepadMacCore/Extensions/<extension-id>/. - Add package under
RepositoryExtensions/<extension-id>/. - Add catalog entry in
RepositoryExtensions/catalog.jsonand update the pinned catalog SHA-256 before release. - Add package entry to
ExtensionCatalog.default. - Add SHA-256 checksums for every package-owned resource file.
- Update
README.mdand docs when the extension adds a new user-facing capability. - Run
./scripts/verify-public-repo.shand./scripts/verify-release.shbefore publishing.