NOTE: THREAD UPDATED

I am starting a thread to spell out my plans for the 2x build of OpenChurch. I would also like input from those of you who use OpenChurch so that I can make sure that this platform can meet your needs.

Introducing Panopoly

I finally put some time into reviewing Panopoly and I have been very impressed. So much so that I have begun work on OpenChurch 2x using Panopoly as my base. This really takes a lot of the maintenance burden off my shoulders as I am essentially delegating that burden to Panopoly.

Timeline

Drupal 8 is expected to be released some time this year. It won't be stable for a minimum of 6 months. My plan would be to release a bare-bones version of OpenChurch (homepage, theme, some blocks) some time after D8 is released. I would wait for Panopoly to get updated to 8x before I moved forward with the 2x port to D8.

Modules

There have been 2 persistent problems throughout this project.

1. Many users have difficulty with advanced site building modules.

Panopoly makes some things much easier on the editing site and uses Panels in place editor well (which we use on some pages now on OpenChurch). I am also scrapping Context for block placement and instead will use the normal Admin Block page for sidebar blocks (which isn't necessarily the 'Panopoly' way but this is better suited for my audience).

2. Maintenance challenges.

One of the big challenges with OpenChurch is module maintenance. My goal for 2x going forward is to delegate some of that work to Panopoly so that I only have to update the Panopoly version as opposed to needing to update and test a bunch of modules individually. I will also remove any modules that are not absolutely necessary from the OC package.

New Features

For 2x the biggest thing is going to be that the site building tools are going to be different and I would say easier to use. The tools I had for 1x were often too confusing (Context being one of the more challenging modules). The other big change is going to be in design.

Design

I would love to do a design refresh but I am also don't want to change things people like. The first dev iteration of 2x will look mostly the same with some smaller adjustments to make the site more naturally responsive. I am however still researching some ideas for a (modest) design update.

Theming

This will be the biggest change for 2x. The 7x version will use Responsive Bartik which emulates the Drupal 8 core theme (I am not sure which came first). While this theme is not as robust as Omega for instance it will suite the needs of 99% of my audience and really assist me greatly in the D8 port of Openchurch 2x. My goal is to make the theme fully responsive and beautiful on every page. I will be using Panopoly layouts for many of the pages which are easy to customize.

One big goal is to make OpenChurch more portable (see next paragraph). I would like to include a little bit of CSS in each module so that the page layouts will look good in other themes. I would love for people to be able to download and install other themes and for OpenChurch still to look beautiful.

For Drupal 8 my initial goal will be to set up the theme as a sub-theme of Bartik and add a small amount of code to the install profile so that we can at least port the theme + some blocks and some sample content to Drupal 8 without waiting a long time for Contrib modules to get ported. It will be barebones but pretty useful for many.

Portability

A big change going forward for 2x is I do plan to split off the core features of OpenChurch into a new module: openchurch_apps. This will contain the app store and features that you should be able to install on most existing Drupal sites, especially a Panopoly site. I would like the openchurch_apps module and the openchurch_theme to both be fully portable and not dependent on the main OpenChurch install profile.

Migration

I would plan to create an openchurch_migrate module which allows you to move content over from 1 site to the next. There will be no upgrade. The goal here would be to move content, users and taxonomy over from 7x to 8x. I also will try to create a migration path from 1x to 2x in Drupal 7.

Volunteers

1. First I would like a volunteer who has maintainer experience to perform security and other module updates for the D7 & 8 projects on a monthly basis. This would help me out a lot
2. Second, I would like to do a documentation sprint around the time of the initial release. All of my documentation is hosted at http://openchurchsite.com/documentation. We could knock out a lot of docs in a short time if we had volunteers who could help write instructions for each feature.
3. Issue queues, help in the issue queues are also always appreciated.

Comments

benthen’s picture

I would like to volunteer to create documentation, either document based or video walkthroughs.

drupalninja99’s picture

Excellent! So are you saying you want to do this when we roll out the d8 version?

benthen’s picture

Yeah when d8 is released I guess. If there is anything that urgently needed doing sooner for d7 I wouldn't be adverse

benthen’s picture

Issue summary: View changes

I am going to stick with the openchurch_theme project

wingmanjd’s picture

I would be interested in assisting.

I do not have "maintainer experience", but I'm willing to learn how to update the various modules/core, if someone would have the time to teach.

Thank you for your consideration.

drupalninja99’s picture

@wingmanjd your first homework assignment is to learn how to use drush make (and presumably drush as well). Updating the OpenChurch .make file(s) is actually pretty easy, you just find the most recent version number of the module/core and change it out. The thing is you need to manually download those updates as well for testing purposes.

wingmanjd’s picture

@drupalninja Do you have a Vagrant file that you test with? If not, I'll just use my own test server.
I do have some knowledge with drush. I'll look into the make file portion.

Thanks.

drupalninja99’s picture

I do not have a vagrant file although I would love someone to set one up for me! I am still learning about Vagrant.

drupalninja99’s picture

Also I am strongly considering using Panopoly as the base install which would simplify a lot of things for me so that I could focus on the OpenChurch specific features.

wingmanjd’s picture

@drupalninja99 Isn't Panopoly restricted to Drupal 7 at this time, or were you just considering it for the 7.x variant of OpenChurch?

drupalninja99’s picture

Well great point. So I am going to update this thread with my plans. My goal is to use Panopoly for OpenChurch 2x going forward. This includes 7.x and 8.x assuming that Panopoly makes it to 8x and I think it will in one form or another. I will update this thread with more notes.

drupalninja99’s picture

Title: Drupal 8 Implementation Goals » OpenChurch 2x Plans and Drupal 8
Issue summary: View changes
wingmanjd’s picture

Hi @drupalninja,

Back in January, you mentioned wanting a vagrant base for your development. I've been working on one here.

It should be able to build out a clean Drupal environment or restore a drush archive dump tar file from the import folder of the project.

Hope it helps!

pilchards’s picture

Hi

As you say, you would like input from those who use openchurch to perhaps improve v2 to suit needs.
I use it on www.chartwellchurch.org.za and love it until I need to teach someone how to do a difficult task that should be easy and not advanced.

My host will not up the limit to upload audio files for the podcast since they moved server software from apache to nginx, so I now have to upload the sermons via FTP (which makes loads of sense).

My problem is that I cannot attach the MP3 once I have uploaded it - I do not see it in the File Browser (the option next to upload).
- I figured out that if I wanted to see the file listed, I need to import the file, which makes no sense if the file is copied back to sites/default/files/ from sites/default/files/sermons
- I cannot use the sermons that I imported, as It gives me an error "The file used in the Audio field may not be referenced."
My solution? I use the Body text editor area to link the file
- My problem with this? I may as well go back to the old website that didn't use openchurch, as this is what was done before I suggested openchurch as a solution to make things easier for uploading sermons.

If possible can the homepage rotator be made easier to add a picture;
And the gallery able to show images uploaded via FTP in one easy step, without re-arranging file/folder structures.

That's all for now :)
Malcs

drupalninja99’s picture

I need to improve the audio field in a couple of ways. I need to use the media widget instead of the file upload widget and I need to support remote files

drupalninja99’s picture

Assigned: Unassigned » drupalninja99
dustinleblanc’s picture

I would suggest hosting your audo on a dedicated service like Libsyn anyway, running audio streams straight from your server isn't a good use of resources.

drupalninja99’s picture

Status: Active » Closed (fixed)

D8 OC has arrived! Closing