Feature Requests

Currently through Church Center, when you make an event as "Featured" in within the settings in Planning Center, it'll bring that event to the top of your events page. I would be so great if this carried over into Church Co's Planning Center Registrations integration also!

The implementation of the new pop-up element menubar is great, but it's also a bit frustrating: * The menu bar does dismiss itself when mousinf away from existing the element, * The size and positioning of the menu bar can obscure information that might be above it. In the example attached, you can see where the popup can hide the line above it, which might be needed for reference for the current editing action. Also If you mouse away from the active element, the menubar remains, even thought another element has the focus (in this example the paragraph above the menubar. I think it would be helpful if an Admin can invoke/hide the menubar by a right-click versus auto-displaying the menubar. Also, mousing off an element should probaly dismiss the menubar. I originaly raised this to Support and they suggested that this be a feature request.

We are glad that fill in the blank was implemented, because we use fill in the blanks every Sunday. Right now though, the fill in the blank field is pre-filled with underscores. We would like the field to be blank so they can fill it in without the underscores. Our current solution also has the ability to reveal the answer to the blank. This is helpful if people miss the point and can fill in the word.

This may seem like a bit of an odd request, but one I think is important to help with knowledge transfer when site admin(s) may change hands and/or when there are new content editors. This request is specific to a way for a page developer to be able to add notes to a page regarding custom content, where any such notes are only visible when a page is in edit mode. There may be cases where the design of a page is not straightforward and being able to document any "need to know" information on a page can be useful to someone who is new who may not see what's happening under the covers. Some examples of custom content that may not be apparent to someone unfamiliar with a page design: * Use of custom HTML * Use of forms * Use of customer-defined custom CSS classes * Use of ChurchCo-defined custom CSS classes * Page dependency assumptions Yes, this type of information can be documented separately, but that is not likely to happen and the ability to supply "in-place" page design notes would be easier to keep updated.

There are a number of occasions where we need to update a particular media artifact. At the moment, we have to delete the outdated one and upload the replacement. That results in our need to update any URL's so they point to the updated artifact. What would help streamline updates is to allow us to open a details page and be able to replace the outdated graphic, video, document or whatever with the updated one. This would allow us to keep the existing URL and any tagging we have coded.

The main event photo has no option be be a clickable link. For example: https://www.wcymca.org/event/turkey-trot , would like to have event banner photo link to runsignup.com/turkey-trot instead of being a static photo.

It would be great to be able to add shortcourses and introductory classes to churchco sites. For onboarding where videos need to be watched and questions answered and results sent in. or pre membership applications. Could use for water baptism signup etc. Lots of things.

At the moment, the only way to test the formatting of an email form action is to publish the form and run a test, which is a bit cumbersome, at least for the purposes of getting the email format and content to where you want it. Therefore, like we can with a Page or Event, it would be very useful if we had a way to display a review version of a email action. Since there would not be actual data for the field variables used in the email, perhaps you can just display the field's label surrounded by braces (e.g., {{First Name}}? Another option would be to allow the form preview function to be operational. That means, when previewing a form, you can actually execute a submit. At the moment, the Submit will display, but is non-functional. This enhancement would simply be to help with creating the look and feel of the email. Functional testing would still require working with a live form.