Add photo, short bio.
\n
\n
17 months later, no usable interface. We switched to WordPress in two weeks.\n
Widgets & menus: drag-n-drop happiness.\n
Obsolete plugins example: RB Internal Links. No longer necessary, was once hyper critical. Also, Genesis has made Page Links To unnecessary.\n
Subdirectory vs. subdomain\n\nGenesis children\n\nGenesis screenshots will go on later slides.\n\n[SCL - can show off new framework. Also will talk about funky subdomain setup.]\n
Shootout highlights\n \nWordPress releases take 5 to 8 months. \nFast development cycles do mean frequent updates. However, functions are always deprecated instead of being removed altogether, so plugins and themes don't break with every major release unless the developer did something stupid. Some simple plugins that use the APIs correctly have not needed an update since version 1.5 -- seven years ago.\n
Shootout highlights\n \nWordPress releases take 5 to 8 months. \nFast development cycles do mean frequent updates. However, functions are always deprecated instead of being removed altogether, so plugins and themes don't break with every major release unless the developer did something stupid. Some simple plugins that use the APIs correctly have not needed an update since version 1.5 -- seven years ago.\n
\n
Ask if anyone's planning to run on IIS... the info on permissions is pretty LAMP-centric.\n
Low/no initial budget outlay\n\nFocus spending on customization and meeting campus needs\n\nAvailable commercial/premium support\n\nPut Shelley's budget slide here against ~$52k to launch OmniUpdate at a 2 year school.\n \n[Stephanie's budget: a lot less than that. I think all we bought was a Gravity Forms dev license. Did use our slave -- er, student worker pretty hard for about a month during and after the launch.] \n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
I think we should point to some instructions/blogs about installation. Leave the slide, point them to a resource, move on.\n
Decide subdomain vs subdirectory. \n\nMake sure your server meets the requirements. \n\nChange the wp-config setting.\n\nAccess the network admin menu.\n
[screenshots: step 1 (wp-config stuff), step 2, Network Admin screens, single site options screen w/ plugin & theme permissions]\n
Stephanie - Domain plugins\n
\n
Common problems: Missing .htaccess file; bad permissions on wp-includes or wp-content; wp-includes didn’t completely upload; plugin conflicts or bad plugin/theme code.\n
\n
\n
\n
\n
\n
\n
\n
Don't use Thesis\n\nSK- talk about what a framework means on a network site, show child theme options, framework settings, etc. Talk about framework specific plugins.\n
\n
\n
\n
\n
I am OK with ditching this slide if you think it's beside the point or too technical or whatever\n
\n
\n
\n
\n
Old versions do not get security fixes. You must stay up to date with WP and all the plugins and themes you have installed.\n\nAuto-upgrading is by far the easiest thing to do. If you need to FTP the files for some reason, be sure to skip wp-content and .htaccess.\n \nNinjas can stay updated via Subversion. The wp-config.php file can be moved up one directory level so you don't overwrite it. \n
\n
High-traffic WordPress sites NEED caching, but it's not built in! Why? The developers want you to find the solution that works best for your site and server.\n
\n
\n
checklist handout\n
checklist handout\n
\n
Themes on Extend go through an extensive vetting process.\n\nPLUGINS DO NOT. Any moron can upload a plugin to the repository. However, they are monitored for evil code. Still, getting things from wordpress.org helps you avoid the nasty stuff.\n
\n
\n
Core features\nFlexibility\nExtensions/plugins\nUse examples\n\nRoadmap\n
\n
\n
\n
\n
Built by the same guys who developed Custom Post Type UI.\n\nAdds basic project management to WP. Great tool for internal project team. Lacks functions for managing communication with stakeholders outside immediate department.\n\nGood example of the type of thing possible with Custom Post Types.\n
CollabPress screenshots\n
\n
\n
\n
\n
Ecwid\nwpCommerce\nwpShop\nWooCommerce\n
Google Summer of Code project and one of Jane's babies, ScholarPress is the WP answer to bloated courseware like Blackboard. It provides classes, assignments, gradebook, student/teacher roles and more. Today it isn’t ready to handle the courseware needs of a complete institution, but I’m seriously considering it for faculty/staff CMS training and on-campus professional development.\n\nproject goals\n - accessibility\n - usability\nroadmap\nknown issues?\n
\n
\n
\n
\n
\n
\n
\n
\n
SK - my campus directory is one real-world example that comes to mind.\n\nhttp://wpshout.com/10-awesome-things-to-do-with-wordpress-custom-fields/\n\nAlso, your course system.\n
\n
\n
Taxonomies can be hierarchical -- like categories, where you can nest them -- or non-hierarchical -- like tags, where you just type new ones into a text field\n
\n
\n
\n
Post types can also be hierarchical (like pages) or non (like posts).\n\nYou can specify which fields your type supports -- title, page attributes, excerpt, revisions, author, the big editor. You can turn those off, then use custom fields to add new ones. You'll have to customize your loop to display the additional stuff.\n
\n
\n
\n
\n
This is reality, even if the wiki says otherwise.\n
This is reality, even if the wiki says otherwise.\n
\n
VIP Support - Automattic: http://goo.gl/DLlXR\n\nSK: Huge fan of premium plugins and themes because the support offered tends to be top notch. Communities build up around these. Good examples are Genesis and GravityForms.\n
\n
\n
\n
I can open up my site and walk through it. You'll have to show the plugins you wrote :P\n