Introduction
bobtemplates.bsuttor is a mr.bob templates to generate strucutre packages for Plone projects.
At the moment, there is only one template for a empty Plone add-on
Hot to create a Plone add-on package
You have to install mr.bob and bobtemplates.bsuttor eggs. Then you can run mrbob:
$ pip install mr.bob $ pip install bobtemplates.bsuttor $ mrbob -O collective.foo bobtemplates:plone
You have to answer some questions:
Welcome to mr.bob interactive mode. Before we generate directory structure, some questions need to be answered. Answer with a question mark to display help. Value in square brackets at the end of the questions present default value if there is no answer. --> Namespace of the package: collective [...]
Now you can install your add on:
$ cd collective.foo $ make install
Finally you can lauch test:
$ bin/test
Or starting Plone:
$ bin/instance fg
Go with your browser to http://localhost:8080/Plone, and you can see your site with your module installed
It’s time to customize it ;-), see Plone developer help
Other example
You can see other example of bobtempaltes which are inspired me
Metadata
Release files for bobtemplates.bsuttor 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bobtemplates.bsuttor-0.1.1.zip | 30.2 kB | Without provenance | Details for bobtemplates.bsuttor-0.1.1.zip |
Release files / bobtemplates.bsuttor-0.1.1.zip
| Download URL | bobtemplates.bsuttor-0.1.1.zip |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8dd4da010adb8b81448d3a9f7c2dae063799ffb709068d55779dfcbb542f367
|
|
BLAKE2b-256 checksum How to use checksums |
1af832058f4420169d9ff7e789d9a07fd0792bcc0c1ae0c779779e7549c8983a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for bobtemplates.bsuttor 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.