PHPackages roseblade/silverstripe-user-reg - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. roseblade/silverstripe-user-reg ActiveSilverstripe-vendormodule[Utility & Helpers](/categories/utility) roseblade/silverstripe-user-reg =============================== A skeleton for Silverstripe CMS modules. 021PHP Since Aug 18Pushed 8mo agoCompare [ Source](https://github.com/RosebladeMedia/silverstripe-user-reg)[ Packagist](https://packagist.org/packages/roseblade/silverstripe-user-reg)[ RSS](/packages/roseblade-silverstripe-user-reg/feed)WikiDiscussions main Synced 1mo ago READMEChangelogDependenciesVersions (1)Used By (0) Silverstripe CMS supported module skeleton ========================================== [](#silverstripe-cms-supported-module-skeleton) A useful skeleton to more easily create a [Silverstripe CMS Module](https://docs.silverstripe.org/en/developer_guides/extending/modules/) that conform to the [Module Standard](https://docs.silverstripe.org/en/developer_guides/extending/modules/#module-standard). This README contains descriptions of the parts of this module base you should customise to meet you own module needs. For example, the module name in the H1 above should be you own module name, and the description text you are reading now is where you should provide a good short explanation of what your module does. Where possible we have included default text that can be included as is into your module and indicated in other places where you need to customise it Below is a template of the sections of your `README.md` you should ideally include to met the Module Standard and help others make use of your modules. Steps to prepare this module for your own use --------------------------------------------- [](#steps-to-prepare-this-module-for-your-own-use) Ensure you read the ['publishing a module'](https://docs.silverstripe.org/en/developer_guides/extending/how_tos/publish_a_module/) guide and update your module's `composer.json` to designate your code as a Silversripe CMS module. - Clone this repository into a folder - Add your name/organisation to `LICENSE.md` - Update this README with information about your module. Ensure sections that aren't relevant are deleted and placeholders are edited where relevant - Review the README files in the various provided directories. You should ultimately delete these README files when you have added your code - Update the module's `composer.json` with your requirements and package name - Update (or remove) `package.json` with your requirements and package name. Run `yarn install` (or remove `yarn.lock`) to ensure dependencies resolve correctly - Clear the git history by running `rm -rf .git && git init` - Add and push to a VCS repository - Either [publish](https://getcomposer.org/doc/02-libraries.md#publishing-to-packagist) the module on packagist.org, or add a [custom repository](https://getcomposer.org/doc/02-libraries.md#publishing-to-a-vcs) to your main `composer.json` - Require the module in your main `composer.json` - If you need to build your css or js and are using components, injector, scss variables, etc from `silverstripe/admin`: - Ensure that `silverstripe/admin` is installed with `composer install --prefer-source` instead of the default `--prefer-dist` (you can use `composer reinstall silverstripe/admin --prefer-source` if you already installed it) - If you are relying on additional dependencies from `silverstripe/admin` instead of adding them as dependencies in your `package.json` file, you need to install third party dependencies in `silverstripe/admin` by running `yarn install` in the `vendor/silverstripe/admin/` directory. - Start developing your module! License ------- [](#license) See [License](LICENSE.md) This module template defaults to using the "BSD-3-Clause" license. The BSD-3 license is one of the most permissive open-source license and is used by most Silverstripe CMS module. To publish your module under a different license: - update the [`license.md`](LICENSE.md) file - update the `license' key in your [`composer.json`\](composer.json). You can use [choosealicense.com](https://choosealicense.com) to help you pick a suitable license for your project. You do not need to keep this section in your README file - the `LICENSE.md` file is sufficient. Installation ------------ [](#installation) Replace `silverstripe-module/skeleton` in the command below with the composer name of your module. ``` composer require silverstripe-module/skeleton ``` **Note:** When you have completed your module, submit it to Packagist or add it as a VCS repository to your project's composer.json, pointing to the private repository URL. Documentation ------------- [](#documentation) - [Documentation readme](docs/en/README.md) Add links into your `docs/` folder here unless your module only requires minimal documentation in that case, add here and remove the docs folder. You might use this as a quick table of content if you mhave multiple documentation pages. Example configuration --------------------- [](#example-configuration) If your module makes use of the config API in Silverstripe CMS it's a good idea to provide an example config here that will get the module working out of the box and expose the user to the possible configuration options. Though note that in many cases simply linking to the documentation is enough. Provide a syntax-highlighted code examples where possible. ``` Page: config_option: true another_config: - item1 - item2 ``` ### Health Score 17 — LowBetter than 6% of packages Maintenance42 Moderate activity, may be stable Popularity6 Limited adoption so far Community2 Small or concentrated contributor base Maturity13 Early-stage or recently created project How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/79709cf1f76ba0120e459da3effa93120ae0897393a34caa5200140c7e5fd728?d=identicon)[MatMorrisParker](/maintainers/MatMorrisParker) ### Embed Badge ![Health badge](/badges/roseblade-silverstripe-user-reg/health.svg) ``` [![Health](https://phpackages.com/badges/roseblade-silverstripe-user-reg/health.svg)](https://phpackages.com/packages/roseblade-silverstripe-user-reg) ``` ### Alternatives [adigital/help-links Define useful links to be added to the dashboard for clients. 102.0k](/packages/adigital-help-links) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)