[sudo-discuss] [omni-sys] development of new wordpress site for omnicommons.org

[Matt Senate]

Huh, it's interesting you point that out. Can you give concrete details
that point out the significant differences between the two calendars?

I find it surprising because I've noted over the years that in fact the
current calendar is very buggy and inconsistent on desktop and mobile. I've
had to manually repair several debilitating bugs with the UI. It's very
heavy in the use of JavaScript, creating lots of interaction, hover, and
modal issues. As for mobile, take notice of how the current calendar
scrolls across an iframe window in the page on an android mobile browser,
it's really restricting--and you can't read the full names of events.

The style differences of the new calendar are still in development as the
theme is still under development. However, at the very least, it's all very
basic HTML so it actually loads a lot more clearly on mobile browsers
(before we've made any changes at all) than the current calendar which
obfuscates a lot more information. I agree it's not right on yet, adding
some padding/margins/font-size-changes will make a significant difference.
Further, my view has been that the end calendar output is the last part
that needs to be polished up since it's all the back end mechanisms and
their reliability that have taken the majority of my attention in this
effort so far.

I'm happy to report after much searching, this plugin reliably replaces all
the integral calendar features of our old calendar plugin except the form
submission aspect (which did have to be customized by yar for the current
calendar plugin as well)--which is why I wrote my original email. If you
don't have any desire to participate in that, no problem. It's a niche and
specific task.

Finally, I believe that if we have a good looking blog that is integrated
with our calendar and the rest of our site, I think we will have more
compelling reasons for our existing active users and new users to write
blog posts that will get read. I hope to get to that point very soon. I
think the end is in sight, and not being able to replace the calendar
prevents us from advancing to replace the whole omnicommons.org site.

Sure, we could stay with the old calendar if necessary, or even just in the
short-term. I never said that was off the table.

On Sun, Jun 26, 2016 at 12:37 AM, Jenny Ryan <tunabananas at gmail.com> wrote:

> Its not nearly as nice-looking as the original, particularly on mobile,
> and given how much other work needs to be done (ie fundraising, actually
> writing blog posts) I don't really see the point in expending effort on
> this. Sorry.
> On 25 Jun 2016 23:23, "Matt Senate" <mattsenate at gmail.com> wrote:
>
>> Hey all,
>>
>> I've been working on https://omnicommons.org/blog as a replacement to
>> omnicommons.org and seeing how far we can go to simplify our lives in
>> that regard. I'm not married to any of the content, and most of the style.
>> This theme is selected because it's a really simple mobile-oriented
>> genesis-based (therefore super-fast-loading) child theme. I'd be down to
>> style it out a lot or just a little to move us forward.
>>
>> Events Manager and the ESS feed are not working, so that's got to end.
>> This is the most promising event plugin I've found so far:
>> http://www.e-dynamics.be/wordpress/?cat=33
>>
>> I love it! However, the "frontend submit" form plugin (an extension to
>> the basic eme plugin) leaves something to be desired. See here how we can
>> customize it a bit:
>> https://wordpress.org/plugins/events-made-easy-frontend-submit/faq/
>>
>> Attached is a form template I started working on, but that doesn't quite
>> implement the drop-down menu for locations properly (locations do not get
>> successfully saved).
>>
>> If anyone has bandwidth, I could use a hand fixing up a better custom
>> form that especially can:
>>
>>    - Restrict locations to those pre-defined in wordpress and made
>>    available as a drop-down menu on the front end.
>>    - Allow for submitting recurring event requests (only single works
>>    right now as far as I can tell, but the admin event add forms allow for
>>    recurrence)
>>    - Adds the additional fields necessary to successfully replace our
>>    current booking form.
>>
>> LMK if anyone wants to meet up to hack on this.
>>
>> _______________________________________________
>> sysadmins mailing list
>> sysadmins at lists.omnicommons.org
>> https://omnicommons.org/lists/listinfo/sysadmins
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sudoroom.org/pipermail/sudo-discuss/attachments/20160627/77ec9673/attachment.html>