Welcome to the official home of the WordPress documentation team.
This team is responsible for coordinating all documentation initiatives around WordPress, including the Codex (moving to HelpHub and DevHub), handbooks, parts of developer.wordpress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, admin help, inline docs, and other general wordsmithing across the WordPress project.
Want to get involved?
There are many ways in which you can help the Docs team. Every small contribution counts and helps! You can report an issue or typo you found in the docs, or even help us write new documentation for parts that are still missing. These are some helpful links to find out more about what we do and how to collaborate:
From May 11-June 8, technical writers are welcome to review the proposed list of project ideas and ask questions related to proposal development. Mentors, thank you for being on hand to help think through project proposals related to our initial ideas or ones the writers may devise. Technical writer applications are due July 9th; We look forward to working with you!
What’s next?
Technical writers interested in working on one of our project ideas, please add your questions as a comment to this post.
Project name: A full and renewed set of documentation style guide Description: We’ve written some style guides along the way but many of those applied to specific handbooks or projects we worked on.
That said, there is not a unified style guide nor is it actually complete.
We propose developing a new style guide while fixing up older ones or simply adopt a great existing one with compatible licenses.
Description: There are plenty of security breaches issues reported. We plan to create documentation of some of the most common issues with suggested fixes so that users can learn and solve their issues.
Related material:
Link to the open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project that needs documentation – https://wordpress.org/support/article
We can have documentation with two to three attacks issues, explain what effect they have on websites, how to prevent, and the fastest way to fix and protect your website.
Project name: Tracking Doc Suggestions / Updates Description: We do not have a unified tracking system for when a doc needs updates. People do it on MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.TracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. (which is really for code changes to WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/), report them on SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and sometimes via Twitter. It’s impossible for people to know if a doc is going through updates or is simply outdated. Some projects use TrelloTrelloProject management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. for short term purposes. Some projects use GitHubGitHubGitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
We really ought to have a unified tracking system so that we can track these requests and the work to fulfill such requests. And we need to create a process to utilize this system properly.
Project Name: WordPress Development Configuration Guide
Description: Code misconfiguration and setup can introduce security bridges and break security endpoints, thereby leaving the door open for malware infections and cryptographic attacks. Creating a configuration guide or overview for developing in WordPress will be very useful. Some of these exist but are not organized or put together in a single place. For example, the configuration Guide will have several sections as files and directories, debugging, nonces, database, WordPress salt, constants, queries, global vars, htaccess, password, httpsHTTPSHTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information., etc.
The configuration guide will be broken down into sections that will address specific issues or setup. For existing resources, they can be referenced accordingly. The main idea behind this configuration guide is to organize WordPress configuration settings into a single base.
Project Name: Curate Existing HelpHub Article To Create Pillar Contents Description: We are continuously creating more content in HelpHub, but basic questions like “Locally Host WordPress” or “How To Secure WordPress”, are answered with separate CPT and not one article to answer completely or links to existing content. While the current configuration is good for SEO, it is confusing for our users. Related material:
I am proposing ‘Pillar Content” that will be curated collection of existing content that will direct guide users in finding more authenticated information. Like “How To Secure WordPress” will give precise guideline and will link and resources from following contents
Project name: Improve Existing Development Documentation and Handbooks Description: We have a lot of developer documentation. CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.’s documentation is mostly automated.
However handbooks that describe how one would create a theme, make a pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party, use the REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. or automate things via the CLICLICommand Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. do not receive updated documentation. In turn, this requires that all handbook maintainers know all the changes in each core releaseReleaseA release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. to be able to write something useful.
In some cases, the handbooks are updated but don’t provide enough examples for new developers to get started. We would like to close these gaps.
Related material:
BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor Handbook: https://developer.wordpress.org/block-editor/
Common APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. Handbook: https://developer.wordpress.org/apis/
Description: During the design process, it was discovered that categories are not used to classify documentation articles and an article may have more than two categories instead of using tags to related articles. This makes it difficult for users to search, as they can click on a categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. > article, and hit the return button only to find themselves in an entirely different category. Another issue is the titles which in some cases do not properly describe what the article is about.
Description: Documentation on developing on top of Block Editor is, depending on the topic, either scarce, outdated, or non-existent. Considering that Block Editor is a significant language leap for WordPress developers, I think the project itself would benefit from having detailed documentation in a form of guides or tutorials, on how to utilize and extend core functionality and what the best practices are.
Features that need documenting: creating custom blocks (basic webpack setup, what plugins are used and why), using editor’s components in custom blocks, using core blocks in custom blocks, using data stores, using all the hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., block settings, plugin sidebars, RichText format types etc. Really, everything.
Description: It is not enough to say that creating a WordPress theme is easy if we do not show it in practice in the documentation. Currently we have a good article on how to start with WordPress, I believe we could do more to make the theme development manual better, as it does not provide a kind of tutorial that really ends with the creation of a functional theme.
Related Material:
Link to the open source project that needs documentation: https://wordpress.org/support/article
It can be divided into stages: Creating a htmlHTMLHTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. template, adding simple styles, separating those from html files and finally converting to one of the templates for the WordPress theme
BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor End-User Documentation (BEEDocs):
@collinsmbaka: Published issuu, crowdsignal, and reverbnation blocks & reviewed the TrelloTrelloProject management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board.
@tacitonic: Arranged the task list spreadsheet priority-wise, got in touch with the contributors who have claimed blocks but are not worked upon.
@bph: Started looking at WordPress.comWordPress.comAn online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ documentation to see what can be ‘harvested’, reviewed contributors documents, in the works and already published, with @atachibana worked on Block Directory documentation, started on a third worksheet in our spreadsheet with WordPress 5.5 and more task listing: BlockPattern, Image Editing, Block Directory.
@milana_cap reported that she didn’t manage to do anything new on this agenda. But she’ll be sharing Google docs soon with this so we all can comment and join the discussion. She also mentioned that the team is trying to change the strategy because it’s impossible to label websites as “commercial” and “personal” only. So they’ll focus on the license, which has to be compatible with GPLGPLGPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. 2+.
The July Coffee Break is set for this Thursday (July 30) at 1500 UTC.
Google Season of Docs 2020
@kenshino reported that they’re still evaluating proposals. The deadline for evaluating the proposals is 28th July.
Open Floor
@bph mentioned that the next Block Editor Enduser documentation team meeting will be on August 10.
@themiked mentioned that he’s concerned about the way of doing the ‘keep the content promotion free’ part. He also mentioned that defining content and promotion is going to be a challenge and he’s looking forward to seeing the first draft.
Please feel welcome to suggest revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in the comments.
Meeting MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
@chaion07 promised there will be a Doodle up soon with APAC-friendly options for choosing a day and time. He estimated that the next Coffee Break will happen in the last week of July.
Please feel welcome to suggest revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. in the comments.
*this is a cumulative doc/proposal from the Docs Onboard Team
Purpose
To create an area away from the high traffic active postings in the main channel that new and existing Contributors can go for assistance and support. Members can also ask a quick question in the new channel. This would declutter the existing #docs channel from error reports and questions, while distinguishing it exclusively for docs related discussions.
At this point, we’ve been direct messaging people and working with them one on one to get started, but this would allow us to have a hub to do so, while information supplied to others could also be of benefit as reference.
Presently, we’ve noticed (especially in the case of new contributors), they tend to get overwhelmed and also intimidated by asking for information in the channel. We’re also duplicating quite a bit of human effort in the case where we have potential solutions to make this process more efficient.
@atachibana reported that for the migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. and re-routing of Codex to Code Reference for Functions, 1033 of 1070 (96.5% <- 95.5%) pages have been completed. He thanked @stevenlinx for the contribution with open tickets. He also mentioned that we have to wait until version 5.5 releaseReleaseA release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. and enhancement of document fixes to Code Reference for 100%.
@makewebbetter offered to volunteer for working on migrating hooksHooksIn WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same..
@bph updated on the Bee-Docs (BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor End-user):
@tacitonic has been reviewing posts with new contributors.
We are looking at WordPress.comWordPress.comAn online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ to fill gaps in WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ documentation
The TrelloTrelloProject management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board finds more usage now that we have more team members on board.
@collinsmbaka will connect with the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-editors regarding plans for Hulu and Photobucket embeds blocks, if they are abandoned or if we should file issues for them.
WordPress 5.5 is coming fast now. GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party versions 8.5 and lower will come to core. Including the import button for external images. So we can keep drafting and collaborating on Google Docs and copy/paste for publishing. The button appears on each image block, and just needs click to get the image into the media library of wordpress.org
Also shared the betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.-tester plugin with the team in case they want to do some peek preview. We’ll keep and eye out for the denotes, too.
good news/bad news: We ran out of tasks for new contributors:
Homework for next week for all: thinking about new tasks for new contributors early wins.
The Bee-Docs team meets each Monday at 14:00 UTC in the #meta-helphub channel over Slack.
@Prubhtej_9 reported that he completed the Scribd block editor documentation earlier that week & thanked @tacitonic for reviewing the doc.
@christiano.zanca reported that @glorialchemica started testing italian helphub translation. The Italian Team is providing support to this ticket to onboard more contributors.
Categorization Project
@estelaris reminded that we can still leave comments on the p2 post and this agenda item will be on hold until the finalization of Technical Writers for this project on the Season of Docs.
@bph suggested that we might need to review how block editor end user documentation is presented. It’s kind of buried, and probably needs a separate entrance and TOC.
External Linking Policy
We’ve witnessed vivid discussion on this agenda item.
Anyone with a WordPress.org username can propose the link (as equivalent to anyone with a WordPress.org account can edit Codex). We could have a Google form or airtable or something similar. They need to fill out following fields (all mandatory):
External link
Placement link at wp.org (where this external link should be added to)
Short description (why this link is a good fit)
WordPress.org username
Consent (“I read the external linking policy rules…” checkbox)
If the proposed domain name appears to not follow the rules 3 times, the domain name gets on the “banned” list.
Review Process:
To make the review process less confusing, we can prepare the set of questions to which all answers have to be “yes” in order to allow a link.
3 members of docs team completes a review (to avoid bias)
The review results are published on #docs team blog
domain name gets 5 links approved get the “trusted” status and we add them to the public list of trusted resources
If one allowed external link gets changed after being approved in a way that is against the rules, all links from that domain get removed, domain name loses its “trusted” status (with possibility to land on “banned” list perhaps?)
The Rules: (Brainstorming Ideas)
The content (article/tutorial) must not include any plugin, theme, service (hosting and similar) that is not bundled with WordPress clean install (which can be downloaded at WordPress.org)
The content, in its entirety or parts, must not be behind the payment or any sort of compensation from the reader (like, share etc)
The page where the content is can not contain visible ads for paid products and services (link in menu is OK but banners are not)
@kenshino suggested When people submit links, one of 2 things can happen
The link is added directly
The content is copied because it’s really good and they get attributed
The discussion centered from trusted links to commercial blogs, tutorials, promoting products, banners, attribution and even GPLGPLGPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples. licensing.
We request input from everyone. There are many aspects to policy making. Please join the conversation on the respective p2 post on commercial blogs and trusted sources.
New Member Mentor Training
@Prubhtej_9 reported that for the month of July 22 new members had joined & 13 new members had joined #docs in the past week.
Due to the unavailability of @sukafia & @tomf the discussion on #docs-help channel was postponed to next week.
Monthly coffee break
@chaion07 reported that he’s still in the process of writing a p2 post, which he had volunteered for. @sukafia is assisting with the p2 post.
Google Season of Docs
@Kenshino(jon) suggested that the ‘Documentation Team’ badge be given to the selected Technical Writers and Mentors for Google Season of Docs. He also mentioned that @ChloéBringmann along with the Mentors are finalizing the selection of the Technical Writers which needs to be reviewed by Google as well.
Open Floor
@tacitonic reported that @Lucila Stancatohad contacted him regarding the following matter:https://wordpress.slack.com/archives/C02RP4WU5/p1594123868113500
@chaion07 offered to make a specific Meeting Summary and Meeting Agenda Document Template in Google Docs so that anyone as a New Contributor can find a direct guideline to assist with the Note taking process & requested to write a p2 post for the same.
@kenshino(jon) also reported that he had shut down the wp-helphub.com server.
@atachibana informed on the MigrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of Codex that 1022 out of 1070 pages had been completed. Currently the project is 95.5% completed which is a 0.70% improvement from last week. He also thanked @stevenlinx for processing complex cases with Open Tickets.
@christiano.zanca informed that the Italian team started translation of HelpHub. Currently Google Docs is being used as the base for checking and then publishing it.
@mkaz is continuing to work on theBlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Tutorial. Currently working on the developer’s environment portion through PR 23953 and more.
@tacitonic currently reviewing The Bee-Docs tasks as @collibnsmbaka and @khushbu.desai are publishing the final drafts on embed blocks. The Bee-Docs Meetings are held every Mondays at 14:00 UTC in #meta-helphub under the supervision of @bph as always.
@Prubhtej_9 is contributing to the Scribd block editor documentation including a few of the handbooks this week & had a small discussion with the Rest APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. team regarding their inputs for improving the Rest API handbook.
Categorization Project
@estlaris reminds everyone that we are looking forward to comments on the p2 post that she wrote earlier. @milana_cap is looking into the comment left by @annezazu previously that focuses on the Github issue.
You can join the conversation by visiting the p2 post related to this topic. We are expecting input from everyone.
New Member Mentoring Team
@softservenet reported that the New Member Mentor Training Team met recently to discuss support capabilities for new members.
@sukafia reported that the Mentoring Team is actively reaching out and checking up on new members. The team is ensuring that every member gets a Welcome Message and is provided with links to helpful resources and guidance relevant to #docs. 7 new members have joined since last week, raising the numbers for this month to 75. The Team is considering to write a p2 post on the proposal for a dedicated channel on Making WordPress Slack so that this can be discussed with the #meta team.
@chaion07 is writing a p2 post covering the monthly summary piece (with the assistance of @sukafia). The new Doodle for the coffee break will be shared in the channel soon. Since it’s not Asian and some timezone friendly, we’ll have to be rotating the time. We will try to rotate the timing in such a manner to suit as many geo-location as possible to gain maximum audience.
Are you an experienced writer? If you are familiar with writing docs and tutorials for WordPress and want to contribute in Open SourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., we have few amazing projects under Google’s Season Of Docs 2020, and the sweet part if you are accepted, you can get paid for it!
Season of Docs 2020 – WordPress
This year we have submitted a number of project ideas to be considered at Season of Docs, you could see we got accepted.
If you look at timeline, you will see we are in the final phase of “Technical writer applications“, deadline July 9, 2020 at 18:00 UTC.
I am personally mentoring for a project I proposed (look at the Project Five on the Idea List Docs), Curate Existing HelpHub Article To Create Pillar Contents, I am writing this post to guide prospective technical Writers to access the project properly, communicate with the mentor, and successfully submit the proposal in time.
I will compile the rest of the post as a resource, will mainly focus on my project, but it should be useable for other projects as well, just communicate with your mentor before you proceed. Remember here Mentor plays an important role if you look at this doc that describes the Mentor’s responsibilities you will realize.
I will rewrite this portion from official review criteria, as that’s how we will review the application when Google forward your proposal to us.
Prior Experience: For most of the project pas experience is important, and if you do not have past experience as a writer, you will mostly like won’t be a good fit. At the same time as this is a Technical Writing project, you need to be very aware how that particular technology works, for WordPress nothing is complex, and very well documented already, but as an example, if you are working with docs related to our new BlockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor, but have not explored that deeply, it will be very hard for you to complete the project.
Language & Communication Skills: Though it’s not must that English is your first language, but as we will be doing everything in English, your command over English is very important. So, we will want to see evidence that shows your English skill and overall Communication Skills.
Content & Doc Design: This is very important. Content style and design of the doc is very important if you look at the projects ideas, it’s more about how different mentors are planning to organize the future of documentation approach for WordPress, so any applicant needs to understand the format, style, and design of the doc of that particular projects.
Project Name: Curate Existing HelpHub Article To Create Pillar Contents Description: We are continuously creating more content in HelpHub, but basic questions like “Locally Host WordPress” or “How To Secure WordPress”, are answered with separate CPT and not one article to answer completely or links to existing content. While the current configuration is good for SEO, it is confusing for our users. Related material:
I am proposing ‘Pillar Content” that will be curated collection of existing content that will direct guide users in finding more authenticated information. Like “How To Secure WordPress” will give precise guideline and will link and resources from following contents
If you have read all the above carefully, then you should realize the requirements for my project. Discuss with me if you need clarification, so you get more clarity before you proceed to the final proposal. This is not an official requirement, but if you submit this before submitting the final proposal, you will have a clear idea, how I will review your proposal in the final stage, as I probably can’t take more than 2-3 writers here, and I am already getting a hand full of the proposal, and this is not a very simple content plan, I need expert hands to truly help WordPress Documentation.
And I would expect about 10Hrs/Week commitment for the duration of the project.
I will try to give feedback via slackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. 24hr, just knock me in Making WordPress slack (@asif2bd).
During discussion about external linking policy, we came to conclusion that we won’t allow, at least in the beginning and for the time being, any commercial blogs. So before you start arguing that some popular pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party’s blogs have valuable information, let me stop you right there.
Allowing “popular plugin’s/theme’s/services’ etc blogs” and all other commercial blogs will put us in a position to protect documentation from being abused as marketing media, to protect ourselves from accusations of being biased and to defend every decision we make along the way. And still, there will be dissatisfied sides claiming we weren’t fair and did them wrong. The idea of allowing external linking will become its own purpose.
Additionally, this will completely move focus from initial idea which is:
Benefit for the documentation user.
If this process should cost Documentation Team too much of a time for weighing, deciding and defending made decisions, then there’s no time for actual contributing and there’s no benefit for anyone.
So any WordPress plugin official blog, theme’s official blog, market’s or shop’s (with themes, plugins etc) official blog, hosting’s official blog, other service’s official blog etc regardless if they are selling anything or not, is not allowed. This is why word commercial is wrapped into quotation marks.
This is in accordance with HelpHub’s (end user documentation) practice that no plugin, theme, hosting etc will not be promoted or recommended. In HelpHub we are documenting only what’s in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. or will be in core.
The same applies here. If the website is dedicated to a specific WordPress product (free or not), it is not allowed. These sites usually have the product name in domain name but we are not going to limit the criteria there. I’m sure some cases will be unique and decision will have to be made specifically for it.
The bottom line is: we haven’t figured out the best way to deal with commercial blogs or sites in a fair manner and thus our focus is going to be on links that don’t drop into that grey zone. We do expect to eventually get towards discussing how we can safely include commercial blog links (if this even is possible).
Now that that’s clear
We need to determine what is not “commercial” website but doesn’t go under personal blog either, which can be allowed. For example, Stack Overflow or any of the Stack Exchange websites. This is not really non-commercial website but its completely neutral towards appearing on WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. This is not to say that being “neutral” in this regard is a requirement but merely pointing out that they have no interest in trying to abuse the opportunity for getting their link appear at wp.org.
Some tutorial websites also comes to mind but it seems we are stepping into a gray area here. Perhaps allowing websites with only free tutorials? Are those even exist?
Let us hear your opinions in comments. All examples, ideas, questions etc are welcomed.
If you have an opinion on the subject now is the time to share it. This is important initiative and we want to make the best possible decision that will benefit the users of the documentation. Thank you. For whole discussion follow #external-linking-policy tag.
