bnomei / kirby3-plopfile Goto Github PK

https://github.com/getkirby-v2/cli

kirby make:blueprint
To create a boilerplate blueprint for a particular template, you can use the kirby make:blueprint command:

kirby make:blueprint projects
This will start the blueprint builder and take you through a couple questions to setup the blueprint options.

If you prefer to just create a clean boilerplate, you can use…

kirby make:blueprint projects --bare
This will create a fresh blueprint: /site/blueprints/projects.yml

kirby make:controller
To create a boilerplate controller for a particular template, you can use the kirby make:controller command:

kirby make:controller projects
This will create a fresh controller: /site/controllers/projects.php

kirby make:snippet
To create a snippet, you can use the kirby make:snippet command:

kirby make:snippet header
This will create a fresh snippet: /site/snippets/header.php

kirby make:template
To create a template, you can use the kirby make:template command:

kirby make:template projects
This will create a fresh template: /site/templates/template.php

kirby make:user
To create a new user account, you can use the kirby make:user command:

kirby make:user -u home -p simpson -e [email protected]
The email is optional. You can also use the full option names:

kirby make:user --username home --password simpson --email [email protected]
This will create a new user in /site/accounts/homer.php

kirby make:tag
To create a new kirbytext tag template, you can use the kirby make:tag command:

kirby make:tag mytag
This will create a new tag boilerplate in /site/tags/mytag.php

kirby make:plugin
To create a new plugin boilerplate, you can use the kirby make:plugin command:

kirby make:plugin myplugin
This will create a new plugin boilerplate in /site/plugins/myplugin/myplugin.php

https://github.com/getkirby/kirby/releases/tag/3.6.0-beta.3

Yes, with 3.8.1.1 and the develop branch version I can happily create custom commands in a plugin:

<?php

Kirby::plugin('getkirby/commander', [
    'commands' => [
        'foo' => [
            'command' => function ($cli) {
                $cli->success('foo');
            }
        ]
    ]
]);

Originally posted by @bastianallgeier in getkirby/cli#10 (comment)

• template (with its page blueprint, controller, model)
• snippet (with subfolder)
• blueprint (with subfolder, choose yaml or php file on generation)
• controller
• model
• config file (default and for other envs)
• plugin
• language
• content (a content file with path, maybe localized)
• user (if i can replicate the generation of encrypted pw)
• htaccess (kirbys default)
• robots txt
• index.php (default and public folder setup)

kirby/config folder is found before site/config