WordPress 项目
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
本页面包含 Google 文档季接受的技术写作项目的详细信息。
项目摘要
- 开源组织:
- WordPress
- 技术文档工程师:
- tacitonic
- 项目名称:
- 一套完整且经过更新的文档样式指南
- 项目时长:
- 长时间运行(5 个月)
Project description
剧情简介:
WordPress 是一个全球性公益软件组织,致力于为全球社区提供注重无障碍性、性能、安全性和易用性的软件。WordPress 致力于在网络发布和开源软件普及化。在数字时代,网站是组织/个人的在线门面;而 WordPress 肩负着一项艰巨任务,即通过其软件高效地为数以亿计的用户提供服务(这得益于 WordPress 运行的互联网占比为 35%)。为了更高效地为这些用户提供服务,文档已被证明是必不可少的,并且大多数开发者、管理员和最终用户都会使用文档。因此,文档可以成为 WordPress 生态系统的主要因素。目前的 WordPress 文档未包含一套通用且统一的发布规则和样式指南。此提案的动机是制定一套全面且经过更新的文档样式指南,适用于所有 WordPress 文档。项目构想涉及整合设计和样式指南的各个方面,例如语义、语法、语法指南、标点符号、开发专用规则、设计属性和格式细节。它还纳入了语音、语气、时态、所有词性以及命名惯例等语言惯例。所用工具、语言和平台包括 WordPress CMS、GitHub、Markdown,可能还包括 PHP/MySQL、HTML/CSS 和 JavaScript。
项目计划:
WordPress 文档样式指南的现状:
WordPress 文档团队一直在实施一种未声明但统一的发布指南方法。但偶尔,系统会预先假定某些元素,而该过程就会变得推测性。对于在 WordPress 上撰写和发布文章,并没有固定的标准和标准。文档团队编写了项目专用的风格指南,但没有任何指南适用于所有项目。现有的大多数样式指南并未整合到一本手册中,或者已被废弃,需要更新。因此,需要设计和制定统一的风格指南,以实现 WordPress 文档的标准化。
目标:
超过 35% 的互联网网站都采用 WordPress 运行,这表明有数百万开发者和最终用户在使用 WordPress 的强大功能。文档是帮助这些开发者和用户高效且毫无麻烦地实现这些功能(即使在遇到不便的情况下)的重要元素。此项目提案的整体目标是实现设计和样式指南的标准化、统一现有样式指南并进行更新,以及补充新的 WordPress 文档法规和规范。这样一来,WordPress 文档将变得易于使用、简单明了且统一。
实施:
正如此项目的导师 (Jon Ang) 所建议的那样,该项目可分为 4 个阶段来完成:发现阶段、定义阶段、实现阶段和维护阶段。在项目开始之前,也就是实习前期,我会与导师合作,根据后续的时间表和交付成果,最终确定合适的时间表和时间安排。我将进一步熟悉 WordPress 系统和此项目的工作协议。
随着实习开始,我将与导师讨论并起草计划摘要。我们将确定相关要求和必要条件。首先,我将简要介绍文档流程和用户互动流程。接下来,我们将概述每个版块、类别和组件的布局线框。然后,我的导师会审核这些布局。如有需要,我们会重新设计布局,并添加/移除一些组件。然后,我将开展用户研究,以确定界面流程的可用性和可行性。随后,将按部分实现文档样式指南(如下图所示)。您也可以参考其他组织的样式指南(采用任何开源许可或知识共享许可),将其附加到我们的指南中。如果在此期间出现任何易用性问题,我会重新设计。
样式指南完成并与 HelpHub 集成后,我们将进行测试和优化。任何漏洞、冗余元素或组件都将得到纠正。我们将执行界面和代码测试,并根据需要修正不必要的 bug 和错误。我们会对完整样式指南的语言、语法、拼写、标点等进行最终质量控制。
由于意外延迟而待处理的任务将在缓冲期内完成。在项目实施过程中,如果确定其他功能或特性可行,则可以在完成最终测试后实现。我们将制定部署计划,并提交完成的产品。
文档将在协作平台(例如 Google 文档)上编译和编辑。如果需要通过 GitHub 发布,还可以实现 Markdown 或 GitHub Flavored Markdown 等标记语言。对于设计和样式标准,还可以参考开源样式指南。最后,系统会使用 WordPress 设置完成文档的格式并发布。
组件表:
以下是可在样式指南中实现的组件的完整列表。
文档指南 - 无障碍功能、文档结构、编码、外部来源、事实、字体、全球受众群体、包容性、合法性、多平台无障碍功能、不含歧义、避免过度声明、页面布局、政治正确性、协议、安全性、句子结构、简洁的写作、措辞和风格、不偏不倚
语言和语法 - 缩写和首字母缩略词、确认与否定、文章、大写、子句、直接/间接言语、第一/第二/第三人称、性别、术语表、名词、前缀和后缀、介词、代词、引用、俚语与术语、术语、拼写、拼写
标点符号 - 英文引号符和英文引号符、英文冒号和英文英文分号、英文逗号、英文省略号、英文感叹号、英文连字符和英文短划线、英文圆括号、英文句号、英文问号、英文正斜线
格式设置 - 摘要、前言、序言、品牌名称、产品名称、标题、代码段、代码块、日期和时间、时区、地点、货币、文件名、脚注、标题和标题、突出显示(粗体、斜体、下划线、删除线、引号)、缩进、索引、链接和网址、列表、项目符号、编号、媒体(图片、视频)和插图、备注、警告、提示、数字和电话号码、多语种、翻译、语言脚本、间距、表格、文本、商标、版权、专利、引文、教程和程序、界面元素、衡量单位
界面 - activity、按钮、代码段、代码块、命令行界面、对话框、菜单和下拉菜单、弹出式窗口和提醒、标签页、术语、界面元素、窗口
代码 - CSS、HTML、JS、Markdown、MySQL、PHP、语法、XML
字词用法词典/术语表 - A 到 Z
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis project aims to create a comprehensive and unified style guide for all WordPress documentation.\u003c/p\u003e\n"],["\u003cp\u003eThe guide will cover various aspects including document guidelines, language and grammar rules, punctuation, formatting, user interface elements, and code conventions.\u003c/p\u003e\n"],["\u003cp\u003eThe project will be implemented in phases: Discovery, Definition, Implementation, and Maintenance, involving user research, testing, and optimization.\u003c/p\u003e\n"],["\u003cp\u003eThe final style guide will be published using WordPress and potentially other platforms like GitHub.\u003c/p\u003e\n"],["\u003cp\u003eA key goal is to enhance the usability, consistency, and accessibility of WordPress documentation for its vast user base.\u003c/p\u003e\n"]]],["The project aims to create a comprehensive, unified style guide for WordPress documentation. Key actions include consolidating existing guidelines, adding new regulations, and standardizing documentation design and style. The project will involve four phases: discovery, definition, implementation, and maintenance. The guide will cover document guidelines, language, grammar, punctuation, formatting, user interface, and coding standards. The guide will be developed and tested using collaborative tools like Google Docs and potentially GitHub, and ultimately integrated with WordPress' HelpHub.\n"],null,["# WordPress project\n\nThis page contains the details of a technical writing project accepted for\nGoogle Season of Docs.\n\n### Project summary\n\nOpen source organization:\n: WordPress\n\nTechnical writer:\n: tacitonic\n\nProject name:\n: A Full and Renewed Set of Documentation Style Guide\n\nProject length:\n: Long running (5 months)\n\n### Project description\n\n#### Synopsis:\n\nWordPress is a global non-profit software organization that is dedicated to serving the global communities with software that emphasizes accessibility, performance, security, and ease of use. WordPress' cause strives to democratize publishing and open source software on the web. In our digital age, a website is quite literally the online facade of an organization/individual; and WordPress serves an immense task of efficiently serving hundreds of millions of users - attributed to the 35% of the internet it runs - with their software. To further efficiently serve these users, documentation proves to be essential and is used by most developers, administrators, and end-users. Therefore, documentation can be established as a principal factor of the WordPress ecosystem. The current WordPress documentation doesn't include a universal \\& unified set of rules and style guidelines for publishing. The motive of this proposal is to create a full and renewed set of documentation style guidelines, universally applicable for WordPress documentation. The project idea involves consolidating all aspects of design and style guidelines like semantics, syntactics, grammar guidelines, punctuation, development-specific rules, design attributes and formatting specifics. It also incorporates language conventions like voice, tone, tense, all parts of speech, as well as naming conventions. The tools, languages and platforms used will be WordPress CMS, GitHub, Markdown and may also consist of PHP/MySQL, HTML/CSS and JavaScript.\n\n#### Project Plan:\n\nCurrent State of WordPress Documentation Style Guides:\nThe WordPress Documentation Team has been implementing an undeclared but unanimous methodology of publishing guidelines. But once in a while, some elements are presupposed and the process becomes speculative. There doesn't exist any fixed standard and criterion for the purpose of writing and publishing articles for WordPress. The documentation team has written project specific style guidelines, but none that are universally applicable. Most style guidelines that exist are not consolidated in one handbook, or are deprecated and need to be updated. Hence, there is a need to design and develop a unified style guide to standardize WordPress documentation.\n\n#### Objectives:\n\nOver 35% of the internet's websites run on WordPress, which in turn indicates that millions of developers and end-users are utilizing WordPress' impressive functionalities. Documentation is an essential element in assisting these developers and users to efficiently fulfill these functionalities without any hassles, even in case of inconveniences. The overall objective of this project proposal is to standardize a design \\& style guide, unify existing style guides and update as well as append new regulations and specifications for WordPress documentation. This would enable ease of use, simplicity and uniformity in WordPress documentation.\n\n#### Implementation:\n\nAs suggested by the mentor (Jon Ang) for this project, the project can be approached in 4 phases: Discovery, Definition, Implementation and Maintenance phase. Before commencement of the project, during the pre-internship period, I will work with my mentor and finalize a suitable schedule and timeline going along the lines of my ensuing timeline \\& deliverables. I will familiarize myself further with the WordPress system and the work protocols for this project.\n\nAs the internship commences, I will discuss and draft the abstract of the plan with my mentor. The requirements and necessities will be determined. Firstly, I will outline the flow of the documentation and the user interaction process. Subsequently, the layout wireframes of each section, category and component will be outlined. These layouts will then be reviewed by my mentor. If required, the layouts will be redesigned and some components added/removed. I will then conduct user research for determining usability and feasibility of the interface flow. Subsequently, the Documentation Style Guide will be implemented (as illustrated in the diagram below) per section. Style guides from other organizations that are under any open source or Creative Commons licenses can be referenced to append our guide as well. If during this period, any usability difficulties occur, I will redesign them.\n\nTesting and optimizations will be carried out after the style guide is completed and integrated with HelpHub. Any vulnerabilities, redundant elements or components would be rectified. UI and code testing will be carried out and unwanted bugs \\& errors will be fixed, if required. A final quality control for the complete style guide will be conducted for language, grammar, spellings, punctuation, etc.\n\nTasks pending due to unforeseen delays would be completed in the buffer period. Additional functionalities or features that would be determined feasible along the course of the project can be implemented after final testing is done. A deployment plan would be constructed and the finished product will be submitted.\n\n#### Tools \\& Methodologies:\n\nThe documentation will be compiled and edited on a collaborative platform, such as Google Docs. If required to publish via GitHub, markup languages like Markdown or GitHub Flavored Markdown can be implemented as well. For design and style standards, open source style guidelines can also be referenced. Finally, the completed document would be formatted and published utilizing WordPress.\n\n#### Component Table:\n\nThis is an exhaustive list of components that can be implemented in the Style Guide.\nDocument Guidelines - Accessibility, Document Structure, Encoding, External Sources, Facts, Fonts, Global Audience, Inclusivity, Legality, Multi-platform Accessibility, Non-ambiguous, No Excessive Claims, Page Layout, Political Correctness, Protocols, Security, Sentence Structure, Succinct Writing, Tone \\& Style, Unbiased\n\nLanguage \\& Grammar - Abbreviations \\& acronyms, Affirmation \\& Negation, Articles, Capitalization, Clause, Direct/Indirect speech, First/Second/Third person, Genders, Glossary, Nouns, Prefixes \\& suffixes, Prepositions, Pronouns, Referencing, Slang \\& jargon, Spellings, Technical terms, Tense, Verbs, Voice\n\nPunctuation - Apostrophe \\& Quotation Marks, Colons \\& Semi Colons, Commas, Ellipses, Exclamation Marks, Hyphens \\& Dashes, Parentheses, Periods, Question Marks, Slashes\n\nFormatting - Abstracts, Introduction, Prefaces, Brand Names, Product Names, Captions, Code Snippets, Code Blocks, Date \\& Time, Time Zones, Places, Currencies, File Names, Footnotes, Headings \\& Titles, Highlighting (Bold, Italics, Underline, Strikethrough, Quotation), Indentation, Index, Links \\& URLs, Lists, Bullet Points, Numbering, Media (Images, Videos) \\& Illustrations, Notes, Warnings, Tips, Numbers \\& Phone Numbers, Polyglots, Translation, Language Scripts, Spacing, Tables, Text, Trademarks, Copyrights, Patents, Citations, Tutorials \\& Procedures, UI elements, Units of Measurement\n\nUser Interface - Activities, Buttons, Code Snippets, Code Blocks, Command Line Interface, Dialogs, Menus \\& Dropdowns, Pop-ups \\& Alerts, Tabs, Terminology, UI elements, Windows\n\nCode - CSS, HTML, JS, Markdown, MySQL, PHP, Syntax, XML\n\nWord Usage Dictionary/Glossary - A to Z"]]