| 开发者 |
stevegrunwell
VanPattenMedia |
|---|---|
| 更新时间 | 2012年10月5日 08:55 |
| 捐献地址: | 去捐款 |
| PHP版本: | 3.3 及以上 |
| WordPress版本: | 3.3 |
<blockquote>? Can we count on the content manager remembering to add class="btn" to that link?
It can be equally frustrating from the client side. You don't want to deal with learning HTML but you want your content to look just as well formatted as the stuff the agency put in at launch. The agency sent over a formatting/style guide but it never seems to be around when you need it.
WP Client Reference attempts to solve these problems by embedding client documentation directly into WordPress. Now agencies can include style guides, tutorials, FAQs, and more without worrying about content managers on the client side not knowing how to format that complicated call-to-action. It's also useful for any type of team to keep track of information (with versioning) right within WordPress.
wp-client-reference plugin directory to /wp-content/plugins/WP Client Reference looks for a wpclientref-views directory in your current theme's directory. If it finds front.php (the default view), single.php (a single article), or wpclientref.css (article styles), it will use those files instead of the plugin's defaults.
Yes! If you need to change the name of the custom post type (default is client_reference) you can do so in the "Article Options" page. This will also update the posts in wp_posts accordingly.
Version 0.4 of the plugin used menu position 70 as its default, which is normally occupied by the Users menu. It's been patched in version 0.41 but any users who installed pre-0.41 should manually change the menu position (Articles > Options) to a position not occupied by a native WordPress menu (71 is the new default for WP Client Reference).
WPClientReference::get_template_url() when loading static assets from {THEME}/wpclientref-views/ (Issue #3). Special thanks to Chris VanPatten for tracking this down!