New contributors arrived and some additional people have started to use it.
In the meantime I have started to think about Bailador itself and in what way can it be unique. In what way can it fit task
better than any other framework.
Note! This site is about Perl 6.
If you are looking for a solution for Perl 5, please check out the Perl 5 tutorial.
A few ideas, some of them might be really bad:
API first - especially good for Microservices where the clients are other programs. See this issue for more details.
Gradual development of content driven sites. See this issue.
Out of the box User Management (register, login/logut, reset password, etc.) (can this be made backend independent or better have a standard, SQLite based implementation?)
Easy display of Relational databases: Given an existing database provide read and write access to the tables. Then allow better ORM modeling.
Easy use of various NoSQL databases (MongoDB, Cassandra)
What would you like to see?
Comment here, send me an e-mail, open an issue. Let us know what would you like to have in the Bailador project.
How to help?
If you are interested to get involved, we have a Slack channel for communication. Let me know by e-mail and I can send you an invite.
If you don't have time now, support the Bailador book that will give you more time to flash out the ideas and then to describe them in the book.
The Perl 6 Tricks and Treats newsletter has been around for a while.
If you are interested to get special notification when there is new content
on this site, it is the best way to keep track:
This is a newsletter temporarily running on my personal site (szabgab.com) using Mailman,
till I implement an alternative system in Perl 6.
Written by Gabor Szabo