-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Repeating Date module to BackdropCMS.org #942
Comments
Issue #942: Add Repeating Dates module.
Yes, I've added it to the beta.b.org branch. However, beta.b.org is currently having space problems. I'll ping @larsdesigns about it, will post an update here when the module is installed and beta is back up. |
@stpaultim, the Repeating Dates module is set up on beta.b.org. Does it meet your needs? If so, we can put it on b.org, but if not, we'll remove it from beta.b.org. |
I'm marking this as something to experiment with and test during our current Infrastructure week. |
@stpaultim, did your "experiment with and test" on beta.b.org result in wanting this on b.org? |
We have been trying with limited and sporatic success to always keep 3-4 Office Hours on the schedule manually.
In the past, we avoided repeating date module to avoid a calendar that is simply full of Office Hours with everything else pushed off the page. However, after discussing the issue with @Wylbur and @yorkshire-pudding, we think it's time to try Repeating Dates.
We recognize that there might be a few other adjustments we need to make for this to be effective. For example:
We can experiment with this a bit, once we have the repeating dates module.
@bugfolder - Can we install this module on the beta site for BackdropCMS.org and do some experimentation there?
ALSO: We expect that if we use repeating dates, we MIGHT need to link to other nodes for the events themselves. I would suggest that we have a single landing page for Office Hours where we can keep up all the details, such as start times, etc. Other events can link to other sites or special nodes created for the event.
The text was updated successfully, but these errors were encountered: