Project

General

Profile

Feature #502

Create Site Templates

Added by Matt Gold almost 9 years ago. Updated 11 months ago.

Status:
Duplicate
Priority name:
High
Assignee:
Category name:
WordPress Themes
Target version:
Start date:
2010-12-19
Due date:
% Done:

0%

Estimated time:

Description

If and when we install the Site Template plugin as described in ticket 501 , we should create a slate of templates that we might offer to users when they first create a blog. While working through this process, we should consult with Joe Ugoretz at MHC, because this is their plugin and they can advise us on how they use it in their install.


Related issues

Related to CUNY Academic Commons - Feature #501: Install WP Site Template PluginResolved2010-12-19

Related to CUNY Academic Commons - Feature #8836: Redesign site launch processAssigned2017-10-20

Is duplicate of CUNY Academic Commons - Feature #9943: Site templatesResolved2018-06-15

History

#1 Updated by Boone Gorges over 8 years ago

Here's how these "templates" work. (Keep in mind that I have not installed the Site Template plugin from MHC, but instead the Site Creation Wizard plugin http://wordpress.org/extend/plugins/site-creation-wizard/)

Both "Templates" and "Features" are, essentially, blogs whose settings are going to be copied over. In the case of Templates, everything - theme, theme options, settings, content - is copied over to the new blog. That's why you can only select one of them. In the case of Features, the plugin will copy over all non-theme-related settings from the Feature blog(s) in question that are not already set on the new blog.

I guess the idea is that you might have a "Research Blog" template (say) and Features like "Rich Media" or "Math and Science features" (LaTeX etc).

I think that this has the potential to be quite confusing. Here's a suggestion: we start off with Templates only. Once we have whittled down our Templates list to something workable, we can think about adding separate feature sets.

As for process: We can't activate the plugin on the production site until there are template blogs in place. So, I suggest creating a number of blogs (they can have the highest privacy level - visible only to admins) and setting them up as templates, before this plugin is activated.

#2 Updated by Matt Gold over 8 years ago

If we can customize the theme chooser page a bit, I don't think this has to be that confusing. It could be as simple as "Choose one of these pre-fabricated blogs or choose your own theme and customize your own site!" We could set up sample blogs for the following:

-- personal portfolio
-- department blog (features: calendar, etc.)
-- project blog
-- research blog

And we can take a look at existing blogs (refer to the case studies in our recent talk) to give us ideas for what to enable on each.

#3 Updated by Boone Gorges over 8 years ago

  • Priority name changed from Normal to High
  • Target version changed from 1.2 to Not tracked

This should happen soon, but it's not necessary for the 1.2 release. I'm taking this out of a milestone but bumping up the priority so that it doesn't get forgotten about.

#4 Updated by Boone Gorges over 4 years ago

  • Category name changed from WordPress (misc) to WordPress Themes

#5 Updated by Boone Gorges over 3 years ago

Adding Sam as a watcher. I think this is still a good idea, but needs a good amount of high-level thought about what we're trying to accomplish, and how it fits in with current user flows.

#6 Updated by Stephen Real over 3 years ago

Chris, Sam,
Any further thoughts on this issue?

Thanks,
Steve

#7 Updated by Boone Gorges almost 2 years ago

  • Target version changed from Not tracked to 1.14

Tied to #8836, as well as upcoming work linked to OER collaborations.

#8 Updated by Boone Gorges almost 2 years ago

#9 Updated by Boone Gorges 11 months ago

  • Status changed from Assigned to Duplicate

This ticket has merged with #9943, so let's continue discussion there.

#10 Updated by Boone Gorges 11 months ago

Also available in: Atom PDF