RNG Ecosystem: Planning for supporting features #76
Description
I've had private correspondence with individuals interested in additional functionality for RNG, so I am posting this issue to gather feedback in a public location. I have the best intentions of addressing some of these feature requests over time. However I would like to request input on the design of these features from the community, in the aim of building a product that is generalised and useful to the majority of site builders. There is nothing stopping the community from creating solutions outlined in this issue, I am open to adding necessary API's to the core module if absolutely necessary.
If you require any of these features, I encourage you to detail what your expectations are for the full experience of site builders, event managers, and registrants, in their respective issue. Technical implementation details are of course optional.
As my time is limited, I am accepting sponsorships for the creation of these modules. Please contact me privately if you are interested.
Much like Drupal, RNG is designed to be modular, maintaining a solid core, and an open API. The following features would be implemented as separate modules:
Automatic open and close of events based on the current date.
Please post ideas and feedback to https://github.com/dpi/rng_date_scheduler
I think I have nailed down what would be useful to many site builders, but I am open to suggestions.
Conference track support / conflicting events
Please post ideas and feedback to https://github.com/dpi/rng_conflict
The module is very barebones, ideas for improvement are welcome.
Wait lists
Wait lists are a black box, there are so many differing opinions on how they should operate.
Post your ideas to #76
More event managers
Event manager (ability to add more event managers)
Approved core features
Any approved feature request in the RNG issue queue is destined for the main RNG module.
Your feature request.
Your feature request here.