Skip to content

ATLAS Plugin Template ​

The official ATLAS Plugin Template on GitHub is a ready-to-use repository for a single ATLAS plugin. Use GitHub's Use this template action to create your own repository.

Plugin generator in Administration ​

ATLAS Administration includes a plugin generator. In addition to the plugin ID, name, description, version, entry path and capabilities, you can choose between an MDI icon from the locally bundled catalog and a custom PNG icon. Search the MDI catalog and select an icon; its SVG and license notices are included in the install package. Custom PNG files can be up to 512 KiB. Their colors and transparency are preserved, and the image data is embedded in the generated package. This applies to the plugin icon, not to arbitrary binary files used by the plugin itself. Host those files separately and reference them by URL. The generator also creates an editable HTML/CSS/JavaScript starter, a repository.json catalog file and a localized README.md with metadata, capabilities, a file list, and installation, publishing and development guidance. You can also download the documentation on its own. Review the generated content and paths and add the files to your repository; the generator does not create a GitHub repository or publish anything automatically. Manually imported packages appear in the Plugin Hub, but their files are not yet served or executed as plugin pages. To launch a plugin, make it available through a repository or a locally served plugin folder.

Plugins with their own language selector inherit the saved ATLAS language preference when launched. A language parameter in the plugin URL takes precedence. If a plugin does not support the selected language, it uses its configured fallback language.

Quick start ​

  1. Open the template repository and choose Use this template → Create a new repository.

  2. Clone your new repository and edit plugins/atlas-plugin/atlas-plugin.json. Set a unique plugin ID, name, version, description and only the capabilities the plugin actually needs.

  3. Replace the example app in plugins/atlas-plugin/ and replace icon.svg, logo.svg and preview.svg with your plugin assets.

  4. Build and validate the package locally:

    sh
    npm run build
    npm run check
  5. Update repository.json and install.html for your repository. The package builder copies the ID, name, version, descriptions and asset paths from the manifest and keeps the catalog in sync.

  6. Enable GitHub Pages for the main branch. The catalog will then be available at https://raw.githubusercontent.com/<owner>/<repo>/main/repository.json.

  7. Add the catalog URL in ATLAS Administration and install the plugin for testing.

Included ​

The template contains a small example plugin, manifest, repository catalog, installation page, package builder, validation and a GitHub Actions workflow. The workflow runs the build and checks on pushes and pull requests.

Bump the plugin version for every release and run npm run build afterwards. Keep the plugin ID stable after publication. Review permissions and declared capabilities before publishing.

Current installation scope ​

The generic repository installer currently stores package files locally. It does not automatically execute arbitrary plugin code downloaded from a repository. The package format stores plugin files as text; larger binary assets should be hosted separately and referenced by URL.

See Repository Format for catalog and package details. Template repository: rockbaer2007/atlas-plugin-template.