{"id":3899,"date":"2021-10-14T18:27:10","date_gmt":"2021-10-14T12:27:10","guid":{"rendered":"https:\/\/betterdocs.co\/?p=3899"},"modified":"2021-10-18T13:16:57","modified_gmt":"2021-10-18T07:16:57","slug":"documentation-best-practices-guide","status":"publish","type":"post","link":"https:\/\/betterdocs.co\/it\/documentation-best-practices-guide\/","title":{"rendered":"Documentation Best Practices: Guide To Make It Effective"},"content":{"rendered":"<p><span style=\"font-weight: 400\">If you want to guide your users or customers to use your service or product, well-written documentation can help them the best. You can implement <\/span><a href=\"https:\/\/betterdocs.co\/it\/blog\/benefits-documentation-customer-support\/\" target=\"_blank\" rel=\"noopener\"><b>documentation best practices<\/b><\/a><span style=\"font-weight: 400\"> and give access to all information that the readers need to have. Let\u2019s learn all about documentation best practices in this blog.<\/span><\/p>\n<p><!--more--><\/p>\n<p><span style=\"font-weight: 400\">\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <img fetchpriority=\"high\" decoding=\"async\" class=\"aligncenter size-full wp-image-3933\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720.jpg\" alt=\"documentation best practices\" width=\"1280\" height=\"720\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720.jpg 1280w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720-300x169.jpg 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720-1024x576.jpg 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720-768x432.jpg 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/Blog-Banner-Documentation-Best-Practices-Guide-To-Make-It-Effective_1280_720-18x10.jpg 18w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/span><\/p>\n<p><span style=\"font-weight: 400\">Documentations are the source of finding the desired answers for the users or the customers. Nowadays, people tend to research and find their own solutions online. You can utilize it and create useful and <\/span><b>effective documentation to reduce pressure<\/b><span style=\"font-weight: 400\"> from your support team. No matter if you own a WooCommerce store or a plugin developer, you can easily benefit from creating proper documentation for your users.<\/span><\/p>\n<h2><b>How Documentation Can Help Your Users?<\/b><\/h2>\n<p><span style=\"font-weight: 400\">Before you start writing any documentation, think about <strong>how it will benefit your users<\/strong> or customers. When users have trouble understanding a product or are unsure about a process, they typically look up related documentation. As a result, it serves as a guideline for both technical and non-technical people. Let\u2019s learn how documentation can effectively help your users or customers easily. <\/span><\/p>\n<p><img decoding=\"async\" class=\"size-full wp-image-3900 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2.png\" alt=\"Documentation best practices\" width=\"1280\" height=\"720\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2.png 1280w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2-300x169.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2-1024x576.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2-768x432.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/2-18x10.png 18w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/p>\n<p><span style=\"font-weight: 400\">\ud83d\udca1Forbes statistics say that more than<\/span><a href=\"https:\/\/www.forbes.com\/sites\/blakemorgan\/2015\/01\/19\/moving-from-transactional-to-meaningful-customer-relationships\/#2aef24a03ad3\" target=\"_blank\" rel=\"noopener\"><b> 40% of customers prefer self-service<\/b><\/a><span style=\"font-weight: 400\"> to contact any human support team. That is where a documentation guide can come to use to provide consistent support and help for your customers. Your customers can be from around the world and might need help at any moment. Instead of directing them to <\/span><b>contact your support team<\/b><span style=\"font-weight: 400\">, you can hand down the solution following documentation best practices.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400\">\ud83d\udca1As documentation can provide answers before your customers even ask for it, you will reach the <\/span><a href=\"https:\/\/wpdeveloper.net\/instant-answer-knowledge-base\/\" target=\"_blank\" rel=\"noopener\"><b>ultimate level of customer satisfaction<\/b><\/a><span style=\"font-weight: 400\"> and increase the customer retention rate. If you think of using documentation solutions or plugins, you can even get feedback from your customers on your documentation.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400\">\ud83d\udca1 If you have written documentation but no one can find it using an online search engine, it is useless. Customers will be able to <\/span><b>find your documentation<\/b><span style=\"font-weight: 400\"> more easily if it is SEO optimized. As a result, you must follow documentation best practices when writing your documentation.\u00a0<\/span><\/p>\n<h2><b>Documentation Best Practices That You Can Follow<\/b><span style=\"font-weight: 400\">\u00a0<\/span><\/h2>\n<p><span style=\"font-weight: 400\">Creating documentation and maintaining it is a continuous process. From <\/span><b>drafting to updating documentation<\/b><span style=\"font-weight: 400\">, you need to keep following the documentation guide for better results. Let\u2019s learn some of the top best documentation best practices step by step and understand the significance of each step.<\/span><\/p>\n<h2><b>1. Thoroughly Create Documentation Plan<\/b><\/h2>\n<p><b><\/b><span style=\"font-weight: 400\">As documentation is a guideline for your users, you need to sit and plan how you will guide them through the process step-by-step to make their experience easier. You need to do <\/span><b>extensive research<\/b><span style=\"font-weight: 400\"> before you start. Suppose you have a WooCommerce shop and you want to guide your customers about how to purchase a product through your website. Assume that the person does not know how to use a website for purchasing.<\/span><\/p>\n<p><span style=\"font-weight: 400\">According to the ideal documentation guide, you can <\/span><b>jot down the key steps<\/b><span style=\"font-weight: 400\"> first and create a map or flowchart for your documentation. While a customer seeks help about how to make a purchase from your website, they can easily see the steps at one glance from your documentation. So the recommended <\/span><b>documentation best practice<\/b><span style=\"font-weight: 400\"> is to create a thorough plan beforehand. Let\u2019s learn some of the steps to make a documentation plan below:\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Set a goal before starting your documentation<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">While creating a documentation plan, you should set a target for yourself. What will be the <\/span><b>primary goal of writing documentation<\/b><span style=\"font-weight: 400\">, and how will it benefit the customer? You must assess whether the documentation displays your product&#8217;s installation process or assists customers in configuring the settings. You can&#8217;t put <\/span><b>everything in a single document<\/b><span style=\"font-weight: 400\">. As a result, you&#8217;ll need to separate each solution into its own set of documentation.\u00a0 That is why the first and most important stage is to set a goal for the documentation.\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Recheck all the resources you have in hand<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">The second documentation guide will be to <\/span><b>recheck the existing resources<\/b><span style=\"font-weight: 400\"> to avoid creating duplicate documentation. No matter if you are writing documentation for yourself or others, you need to check the available resources first. It will eventually save your customers or users from being confused.\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Determine a style guide for your documentation<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><b>Set the tone for your documentation<\/b><span style=\"font-weight: 400\"> before you start writing it. Consider the readers who will be relying on your documentation for direction. Many technological organizations prefer their technical documentation to be <\/span><b>written in a straightforward and simple way<\/b><span style=\"font-weight: 400\">. Some businesses, on the other hand, may use elaborate language in their documents. As a result, you must define a tone for your content based on your intended audience. <\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Create documentation structure\u00a0<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">Just like writing anything we create a draft or content skeleton, one of the documentation best practices will be creating a roadmap before you start. For example, if you are writing documentation about installing something, you can write down the topics and subtopics that might be related to it.\u00a0<\/span><\/p>\n<h2><b>2. Design Or Style Your Documentation With Consistency<\/b><\/h2>\n<p><b><\/b><b>Documentation presentation<\/b><span style=\"font-weight: 400\"> is important for users or customers because it can determine the usability of your documentation. Of course, you have written documentation that is well-researched and well-written but if the doc format does not <\/span>look convenient,<span style=\"font-weight: 400\"> readers will skip it. We have some suggestions on the documentation guide below about designing or styling your documentation.<\/span><\/p>\n<p><img decoding=\"async\" class=\"size-full wp-image-3903 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5.png\" alt=\"documentation best practices\" width=\"1280\" height=\"720\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5.png 1280w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5-300x169.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5-1024x576.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5-768x432.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/5-18x10.png 18w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Use ready templates to design documentation<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">Suppose you have a WordPress WooCommerce website and want to publish documentation on a topic. You can use a <\/span><a href=\"https:\/\/wordpress.org\/plugins\/betterdocs\/\" target=\"_blank\" rel=\"nofollow noopener\"><b>documentation plugin <\/b><\/a><span style=\"font-weight: 400\">and get access to <\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/betterdocs-ready-blocks-elementor\/\" target=\"_blank\" rel=\"noopener\"><b>ready templates to design<\/b><\/a><span style=\"font-weight: 400\"> your documentation page. Documentation best practices will be using ready templates and styling your documentation to enhance its readability.\u00a0<\/span><\/p>\n<h2><b>3. Write Documentation Following A Pattern<\/b><span style=\"font-weight: 400\">\u00a0<\/span><\/h2>\n<p><span style=\"font-weight: 400\">As you have made a plan, set a tone and configured a design or style to present your documentation, it\u2019s time to write down the first draft step by step. Let\u2019s see some of the simple documentation best practices below and make your documentation more attractive.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3904 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6.png\" alt=\"documentation best practices\" width=\"1280\" height=\"720\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6.png 1280w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6-300x169.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6-1024x576.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6-768x432.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/6-18x10.png 18w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/p>\n<p><span style=\"font-weight: 400\">The language of documentation must not be complicated and the length should be precise. Instead of pushing all the<\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/how-to-configure-doc-single-page\/\" target=\"_blank\" rel=\"noopener\"><b> information in one document<\/b><\/a><span style=\"font-weight: 400\">, you can create multiple knowledge bases for your reader\u2019s better understanding. So compose a compact yet useful documentation that is easy to follow.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400\">While writing documentation, you also need to understand how to make it interactive and engaging. There is no alternative to <\/span><b>images, infographics and videos <\/b><span style=\"font-weight: 400\">when it comes to documentation. A text-heavy document is not appealing to any reader. So you can add useful and related images to enhance the quality of your documentation.<\/span><\/p>\n<h2><b>4. Add Logical Navigation Structure To Your Documentation<\/b><\/h2>\n<p><span style=\"font-weight: 400\">According to the documentation guide, you can use navigation options or buttons to organize your documentation page and make your reader&#8217;s experience more pleasant. Navigation options or buttons are able to guide your readers through finding any content they are looking for. Let\u2019s see some of the most useful navigation tools for your documentation website below:\u00a0<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Table Of Content For Your Documentation Knowledge Base\u00a0<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">It will be easier for readers to see what single documentation will offer them if you<\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/table-of-contents-elementor\/\" target=\"_blank\" rel=\"noopener\"><b> use a table of content for your documentation<\/b><\/a><span style=\"font-weight: 400\"> pages. This is the most effective technique to provide a thorough overview of the content and better organize it. So that your document&#8217;s readers have a clear idea of what they&#8217;re getting into before they start reading it.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3905 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/7.gif\" alt=\"Documentation best practices\" width=\"1199\" height=\"620\" title=\"\"><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><span style=\"font-weight: 400\"><strong>Add Advanced Live Search Bar<\/strong>\u00a0<\/span><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">The advanced live search bar is a great way to help website visitors quickly find their desired content just by searching for it. If you have more documentation on your site, you can <\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/documentation-live-search\/\" target=\"_blank\" rel=\"noopener\"><b>add a search bar<\/b><\/a><span style=\"font-weight: 400\"> so that people can navigate easily without being confused. <\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3906 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8.png\" alt=\"documentation best practices\" width=\"1744\" height=\"812\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8.png 1744w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8-300x140.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8-1024x477.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8-768x358.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8-1536x715.png 1536w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/8-18x8.png 18w\" sizes=\"(max-width: 1744px) 100vw, 1744px\" \/><\/p>\n<ul>\n<li style=\"font-weight: 400\">\n<h3><strong>Add Tags &amp; Categorize Documentation<\/strong><\/h3>\n<\/li>\n<\/ul>\n<p><span style=\"font-weight: 400\">Categorizing documentation can help you to be organized and broad grouping identical documentation. On the other hand, tags are used to narrow down the focus on the specific topic. You can create a taxonomy of your documentation page and score better in SEO results. You can <\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/manage-categories-tags\/\" target=\"_blank\" rel=\"noopener\"><b>add tags and categories to your documentation<\/b><\/a><span style=\"font-weight: 400\"> using a knowledge base plugin like BetterDocs.\u00a0<\/span><\/p>\n<h2><b>5. Create An Update Schedule For Documentation\u00a0<\/b><\/h2>\n<p><span style=\"font-weight: 400\">As mentioned before, creating documentation is a continuous process and the best practice is to keep updating it from time to time. According to the documentation guide, you can create a <\/span><b>schedule and update documentation<\/b><span style=\"font-weight: 400\"> one by one when needed. This simple step can make sure that your customers or readers are getting to the point solution from you. You will have a streamlined process if you start applying these <\/span><b>documentation best practices<\/b><span style=\"font-weight: 400\"> while planning and writing your own documentation.\u00a0<\/span><\/p>\n<h2><b>6. Translate Documentation For International Readers\u00a0<\/b><\/h2>\n<p><b><\/b><span style=\"font-weight: 400\">The ideal documentation guide suggests<\/span><a href=\"https:\/\/betterdocs.co\/it\/blog\/betterdocs-and-wpml-partnership-documentation\/\" target=\"_blank\" rel=\"noopener\"><b> increasing the accessibility of your documentation<\/b><\/a><span style=\"font-weight: 400\"> as well. It means, when you have international readers from around the world, you can translate the documentation page for them to make it more accessible. If you use the <\/span><a href=\"https:\/\/betterdocs.co\/it\/\" target=\"_blank\" rel=\"noopener\"><b>BetterDocs <\/b><\/a><span style=\"font-weight: 400\">plugin to create a documentation page all from scratch, you can easily translate any single document as BetterDocs has compatibility with the most popular <\/span><a href=\"https:\/\/betterdocs.co\/it\/docs\/translate-single-docs-wpml\/\" target=\"_blank\" rel=\"noopener\"><b>multilingual translation plugin WPML<\/b><\/a><span style=\"font-weight: 400\">.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3907 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9.png\" alt=\"documentation best practices\" width=\"1280\" height=\"720\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9.png 1280w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9-300x169.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9-1024x576.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9-768x432.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/9-18x10.png 18w\" sizes=\"(max-width: 1280px) 100vw, 1280px\" \/><\/p>\n<h2><b>Bonus: Ultimate Guide For Creating The Best WordPress Documentation Site<\/b><\/h2>\n<p><span style=\"font-weight: 400\">If you are planning to create a <\/span><a href=\"https:\/\/betterdocs.co\/it\/blog\/documentation-pages-using-elementor\/\" target=\"_blank\" rel=\"noopener\"><b>WordPress documentation site for your customers<\/b><\/a><span style=\"font-weight: 400\"> or readers, you can do so using the ultimate documentation plugin <\/span><a href=\"https:\/\/betterdocs.co\/it\/\" target=\"_blank\" rel=\"noopener\"><b>BetterDocs<\/b><\/a><span style=\"font-weight: 400\">. Along with multiple ready templates, you will get options to style your documentation pages, add tables of content, live search options or even instant chatbot. <\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-3908 aligncenter\" src=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10.png\" alt=\"documentation best practices\" width=\"1166\" height=\"368\" title=\"\" srcset=\"https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10.png 1166w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10-300x95.png 300w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10-1024x323.png 1024w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10-768x242.png 768w, https:\/\/betterdocs.co\/wp-content\/uploads\/2021\/10\/10-18x6.png 18w\" sizes=\"(max-width: 1166px) 100vw, 1166px\" \/><\/p>\n<p><span style=\"font-weight: 400\">If you have successfully implemented these suggestions while creating documentation, then congratulations! You have successfully used all the documentation best practices already. To read more informative blogs like this <\/span><a href=\"https:\/\/betterdocs.co\/it\/blog\/\" target=\"_blank\" rel=\"noopener\"><b>subscribe to our blog<\/b><\/a><span style=\"font-weight: 400\"> and share your thoughts on documentation practices by joining our <\/span><a href=\"https:\/\/www.facebook.com\/groups\/wpdeveloper.net\/\" target=\"_blank\" rel=\"noopener\"><b>Facebook community<\/b><\/a><span style=\"font-weight: 400\">. <\/span><\/p>","protected":false},"excerpt":{"rendered":"<p>This blog will help you in learning all of the current documentation best practices that you should be aware of before generating any documentation.<\/p>","protected":false},"author":18,"featured_media":3933,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_eb_attr":"","inline_featured_image":false,"_eb_data_table":"","_analytify_skip_tracking":false,"footnotes":"","_wpscppro_dont_share_socialmedia":false,"_wpscppro_custom_social_share_image":0,"_facebook_share_type":"","_twitter_share_type":"","_linkedin_share_type":"","_pinterest_share_type":"","_linkedin_share_type_page":"","_instagram_share_type":"","_medium_share_type":"","_threads_share_type":"","_google_business_share_type":"","_selected_social_profile":[],"_wpsp_enable_custom_social_template":false,"_wpsp_social_scheduling":{"enabled":false,"datetime":null,"platforms":[],"status":"template_only","dateOption":"today","timeOption":"now","customDays":"","customHours":"","customDate":"","customTime":"","schedulingType":"absolute"},"_wpsp_active_default_template":true},"categories":[182,58],"tags":[192,26,164,190,103,193,191,28,97],"class_list":["post-3899","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-guide","category-tutorial","tag-best-practices-for-documentation","tag-betterdocs","tag-betterdocs-wpml-partnership","tag-betterdocs-documentation-best-practices","tag-betterdocs-wordpress-documentation","tag-creating-knowledge-base","tag-documentation-best-practices","tag-knowledge-base","tag-translate-betterdocs-wordpress-documentation"],"nelio_content":{"autoShareEndMode":"never","automationSources":{"useCustomSentences":false,"customSentences":[]},"efiAlt":"","efiUrl":"","followers":[18,12],"highlights":[],"isAutoShareEnabled":true,"networkImageIds":[],"permalinkQueryArgs":[],"series":[],"suggestedReferences":[]},"_links":{"self":[{"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/posts\/3899","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/comments?post=3899"}],"version-history":[{"count":9,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/posts\/3899\/revisions"}],"predecessor-version":[{"id":3939,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/posts\/3899\/revisions\/3939"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/media\/3933"}],"wp:attachment":[{"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/media?parent=3899"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/categories?post=3899"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/betterdocs.co\/it\/wp-json\/wp\/v2\/tags?post=3899"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}