szabgab / 6blog Goto Github PK

Just a couple of suggestions since it's early in the game:

1. How about using Perl 6 file names as ".p6" and ".pm6" as the trend seems to be?

2. Also, use Perl 6ish kebab-case for names where possible, e.g., 'content-type' instead of 'content_type'?

Same for Bailador...

I love both projects, Gabor, thanks!

Currently I am using bashblog for a few of my sites. It would be great to have one in perl or perl6. I would consider paying for it.

I feel that if we are going to create a new platform from scratch then we should give some real thought to the desirable architecture characteristics . WordPress gained rapid traction by being simple to install, bundling in some core features and being simple to create themes and plugins for. In my mind, the simplicity of making plugins has also been one of it's most annoying aspects. There are thousands of plugins that are free ... unless you want 'advanced' features. Many of the plugins are simply a wrapper to a very loosely coupled service on an entirely different architecture. WP is starting to show it's age in other ways .. it's not built with modern html5 and JS frameworks front and centre. Many perl devs have created templated solutions and aren't in a hurry to start another effort from scratch, but perhaps there could be some value in creating a reference implementation with sufficiently isolated functional components to make them easily replaceable with alternatives and that encourages. For my own part I still use code that I wrote 5 years ago to do templated stuff and have never been quite convinced to use the more popular templating approaches in perl. I have been quite impressed with mojo and I know that it's time I updated my core toolset so I'm quite interested in helping out where I can.
For me, I'd love to see a solution that has the following features:

• html5 - includes ability to include Sass or whatever CSS/JS build tools are decided.
• ability to hook into Firebase and provide a quick setup for OAuth providers.
• a smooth path to encourage / incorporate richer semantic structure to the content
• websocket hooks and api included in the base fucntionality
• simple installer including http server of choice for mac,windows,ubuntu,debian that is trivial to install on Amazon ec2
• cli tool to allow management as per wp-cli

Suggested quickstart sprint: ( aprx 2 weeks - compare multiple appraoches )

• auth / user management
• page content / nav
• admin console
• installer