內容簡介
建立 WordPress 網站/佈景主題然後將其交給客戶進行日常更新是數位代理公司的常規做法。開發人員為了在複製設計師的視覺設計的同時，讓主題易於客戶使用而努力。當設計變得越來越複雜時，開發人員面臨著問題：客戶是否會記得包含 <blockquote> ？我們能否指望內容管理員記得將 class = "btn" 添加到該鏈結中？
從客戶的角度來看，這同樣令人沮喪。你不想學習 HTML，但你希望你的內容看起來和代理公司在啟動時放入相同的格式。代理公司發送了一份格式/樣式指南，但在需要時卻總是不見了。
WP Client Reference 嘗試通過將客戶文檔直接嵌入 WordPress 來解決這些問題。現在，代理公司可以在不用擔心客戶端的內容管理員不知道如何格式化複雜的號召語的情況下，包含樣式指南、教程、常見問題解答等等。對於任何類型的團隊來說，這也是在 WordPress 中記錄信息（帶有版本控制）的有用工具。
特別感謝
感謝 duckgoesoink 在 0.41 中發現的知識庫/用戶衝突並加以修復。
外掛標籤
開發者團隊
原文外掛簡介
It’s common practice for digital agencies to build a WordPress site/theme then simply hand it off to the client for day-to-day updating. The developers work hard to strike a balance between replicating the designer’s vision and making the theme easy for the client to use. As the design becomes more complex the developer faces questions: Will the client remember to wrap this in a
? 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.
Special Thanks
Thank you to duckgoesoink for catching the Knowledgebase/User conflict fixed in 0.41.延伸相關外掛
