# Developers

**URL:** https://community.pnlcs.com/c/developers/10.md

[Latest](https://community.pnlcs.com/latest.md) · [Categories](https://community.pnlcs.com/categories.md) · [Tags](https://community.pnlcs.com/tags.md)

---

## [About the Developers category](https://community.pnlcs.com/t/about-the-developers-category/12)

<div class="topic-metadata">

**Author:** [@keyvanertugrul](https://community.pnlcs.com/u/keyvanertugrul)\
**Replies:** 0\
**Last updated:** [October 23, 2026, 9:26am UTC](https://community.pnlcs.com/t/about-the-developers-category/12 "2026-10-23T09:26:19Z")

</div>

Writing modules, themes and integrations, and using the PNLCS API.

---

## [Start here: writing your first PNLCS module](https://community.pnlcs.com/t/start-here-writing-your-first-pnlcs-module/21)

<div class="topic-metadata">

**Author:** [@keyvanertugrul](https://community.pnlcs.com/u/keyvanertugrul)\
**Replies:** 0\
**Last updated:** [October 25, 2026, 1:41pm UTC](https://community.pnlcs.com/t/start-here-writing-your-first-pnlcs-module/21 "2026-10-25T13:41:59Z")

</div>

A module is a folder under modules/ with a pnlcs.json manifest. Drop it in and PNLCS registers it on the next request. You don’t edit the core, and nothing has to be re-registered after an update. modules/ └── Gateways/…