|
|
1. I have found a few Perl6 content management systems on github: [Uzu](https://github.com/scmorrison/uzu), [Cantilever](https://github.com/davepagurek/Cantilever), [November](https://github.com/viklund/november)
|
|
|
1. I have found a few Perl6 content management systems on github: [Uzu](https://github.com/scmorrison/uzu), [Cantilever](https://github.com/davepagurek/Cantilever), [November](https://github.com/viklund/november);
|
|
|
|
|
|
2. Quick search & found just [one topic](http://blogs.perl.org/users/scott_walters2/2014/06/perl-needs-a-user-friendly-cms.html) about devel of Perl5 user-friendly CMS, 2014 :(((
|
|
|
2. Quick search & found just [one topic](http://blogs.perl.org/users/scott_walters2/2014/06/perl-needs-a-user-friendly-cms.html) about devel of Perl5 user-friendly CMS, 2014;
|
|
|
|
|
|
3. No pure CMS itself (on Perl5), there are a few Perl frameworks: Mojolicious, Plack, Catalyst. Pure = I mean CMS out-of-box. Framework is used to implement specific features, but offen we need a quick-deployment tool for blog, landing, small store or something else.
|
|
|
3. No pure CMS itself (on Perl5), there are a few Perl frameworks: Mojolicious, Plack, Catalyst. Pure = I mean CMS out-of-box. Framework is used to implement specific features, but offen we need a quick-deployment tool for blog, landing, small store or something else;
|
|
|
|
|
|
4. I had developed Pheix (Perl5) for a few years and it succesfully powers ~20 sites. This January I have decided to port it to Perl6.
|
|
|
4. I had developed Pheix (Perl5) for a few years and it succesfully powers ~20 sites. This January I have decided to port it to Perl6;
|
|
|
|
|
|
5. Requrements to CMS. This is my own list from more than 10 years of midlevel (landings, small stores, personal pages: less than 1000 visitors per day) web-site development experience.
|
|
|
5. Requrements to CMS. This is my own list from more than 10 years of midlevel (landings, small stores, personal pages: less than 1000 visitors per day) web-site development experience;
|
|
|
|
|
|
6. Architecture
|
|
|
6. Architecture;
|
|
|
|
|
|
7. General benefits and strong suits: a) module scaling, b) opensource, c) mobile and seo friendly, d) deeply documented, e) abstract DB support level, f) it's on Perl6
|
|
|
7. General benefit: Phiex uses blockchain (Ethereum) to store data (database via [smart contracts](http://solidity.readthedocs.io/en/v0.4.24/introduction-to-smart-contracts.html), files via [swarm](http://swarm-guide.readthedocs.io/en/latest/introduction.html)). It's the decentralized webapp;
|
|
|
|
|
|
8. Module scaling features: install procedure, *bytecode (?)*
|
|
|
8. Other benefits and strong suits: a) module scaling, b) opensource, c) mobile and seo friendly, d) deeply documented, e) abstract DB support level, f) it's on Perl6;
|
|
|
|
|
|
9. Built-in modules: core and security (with simple access levels)
|
|
|
9. Module scaling features: install procedure, *bytecode (?)*;
|
|
|
|
|
|
10. General addon (module no.1): universal module for blog, show room (catalog w/o buy option), landing, etc... |
|
|
10. Built-in modules: core and security (with simple access levels);
|
|
|
|
|
|
11. General addon (module no.1): universal module for blog, showroom (catalog w/o buy option), landing, etc... |