PRESENTATION
The goal of this package is to transform your Plone Site in a platform in which you can add Minimal Sites.
A Minimal Site is a specific folder which implements INavigationRoot, so inside a Mini Site the plone portal is not visible.
The Mini Site is a blog or a simple Site (choose it at creation time). The blog is a topic showing complete last newsitems (entire full text). Comments are allowed on NewsItems and Documents.
The Mini Site has an email_from adress, this adress is used when sending mails with contact-form.
The Mini Site has a theme : you can choose a theme and modify it easily after Mini Site creation. You can also reload a new theme for the mini site. For themes we use collective.phantasy which permits to change some skin properties, to add a css in a skin, to overload static viewlets (colophon, logo, footer) and to select which dynamic viewlets you want to display. The plone administrator can add new themes in the theme’s repository, these new themes can be browsed at MiniSite creation/edition time.
The Mini Site implements a placeful workflow policy (all contents will use a really simple private/public workflow). Just improve this workflow if you need more transitions …
Inside Minisite you can add only 3 content types, a document, a folder or a news item.
Images, links and other linked medias can only be added with html editor inside documents or news items.
By default the Mini Site is using FCKEditor, the FCKEditor browser and uploader is using a specific Large Folder called attachments for file upload. In future we will use collective.ckeditor and collective.plonefinder currently in dev mode.
The MiniSite is using a specific Folder called PhotoAlbum used to show images. To upload images quickly in Photo Albums collective.uploadify is used.
MiniSite owner can manage portlets.
That’s all. Read also doctests inside product.
You have all you need to make a Blog Platform with Plone. Because Plone is a powerfull CMS, you will be able to make the same thing for your own needs quickly, and much better i think (i’m not a developper, just a webdesigner). Read the code, it’s easy, it’s Python and Zope, it’s a natural language.
Dependency :
Plone3.1+<4.0
The Plone4 compliance will depend on collective.phantasy not tested with Plone4 skins at this time. I need some time (and budget of course) for that, it’s not complex.
Installation :
Just add ‘aws.minisite’ in eggs and zcml section in your buildout or using easy_install ‘easy_install aws.minisite’
This will also download and install all dependencies :
collective.phantasy>=1.0 and its dependencies
Products.FCKeditor>=2.6.5.1
collective.uploadify (used in PhotoAlbum)
In Plone just add “Plone Mini Sites” product with quick_installer
Note :
To improve it you can add Apache in front to adapt urls with rewrite rules to get :
all urls with xyz.mydomain.com are rewritten in http://localhost:8080/minisites/xyz
The rewrite rule is really simple :
RewriteCond %{HTTP:Authorization} ^(.*) rewriteCond %{HTTP_HOST} ^(.+).minisites.mydomain.com [NC] rewriteCond %{HTTP_HOST) !^www. RewriteRule ^(.*) http://localhost:10080/VirtualHostBase/http/%{HTTP_HOST}:80/minisites/%1/VirtualHostRoot/$1 [P] rewriteCond %{HTTP_HOST) ^www. RewriteRule ^(.*) http://localhost:10080/VirtualHostBase/http/%{HTTP_HOST}:80/minisites/VirtualHostRoot/$1 [P]
Just replace the good things at the good place.
TODO :
A help page for end users added in mini site after site creation.
A redirection to id-minisite.mydomain.com/login_form after site creation when the minisite_domain property is filled in site_properties with ‘mydomain.com’ value.
In MiniSite Edit Form force the id widget to be visible, and change the id widget to get something like :
Enter the Mini Site address : _______ .mydomain.com
Translations
use collective.ckeditor + collective.plonefinder (more user friendly tools for upload and browse) packages in progress
keywords system for blog (must be independent for each mini site)
Contributions are welcome, contact :
Copyright :
Alter Way Solutions 2010 License GPL (read docs/LICENSE.txt) Author : Jean-mat Grimaldi
Change history
Changelog
1.0.0
First release [Alter Way Solutions]
1 maintainer
Metadata
1 maintainer
Release files for aws.minisite 1.0.2
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 |
|---|---|---|---|---|
| aws.minisite-1.0.2.zip | 623.1 kB | Without provenance | Details for aws.minisite-1.0.2.zip |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws.minisite-1.0.2-py2.4.egg | Legacy Egg format | - | - | Details for aws.minisite-1.0.2-py2.4.egg |
Total release size: 1.3 MB
Release files / aws.minisite-1.0.2.zip
| Download URL | aws.minisite-1.0.2.zip |
|---|---|
| Size | 623.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
856f00c1de5c9c0a2fc71c5c914cb7e91e233068355538ed4528110b84a8dbd6
|
|
BLAKE2b-256 checksum How to use checksums |
d489176282311b5a5f18cc609d8df49676d373004229f0cd8d4323a4326e48c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / aws.minisite-1.0.2-py2.4.egg
| Download URL | aws.minisite-1.0.2-py2.4.egg |
|---|---|
| Size | 629.5 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
b474336d05042dbf3cf61817c296e9c93009525298bac77c72f7c02257c45e1b
|
|
BLAKE2b-256 checksum How to use checksums |
cc5690b8d9d310bc1869ebe395b58a4fa3eadc074c75be7210cfc205d9487339
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aws.minisite 1.0.2
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.
