{"id":42119,"date":"2019-03-18T00:00:00","date_gmt":"2019-03-17T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit"},"modified":"2020-02-18T13:44:55","modified_gmt":"2020-02-18T10:44:55","slug":"polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","title":{"rendered":"User Documentation: What Makes It Bad and How to Fix It","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"User Documentation: What Makes It Bad and How to Fix It\" src=\"\/wp-content\/uploads\/2019\/03\/4381d63e81fbb299384255cb54dd34b5.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSoftware documentation is just a set of articles. But even those can be frustrating. First, you spend a long time searching for the right instruction. Then, you struggle with obscure text. You follow the instructions, but the problem remains unresolved. You look for another article, feeling anxious... An hour later, you give up and walk away. That's how poor documentation works. What makes it that way, and how can it be improved\u2014read more below.<br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<blockquote><p>Our old documentation had many shortcomings. For almost a year, we have been overhauling it so that the scenario described above does not affect our clients. Take a look, <noindex><a rel=\"nofollow\" href=\"https:\/\/doc.ispsystem.ru\/index.php\/\">how it was<\/a><\/noindex> and <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ispsystem.ru\/\">how it is now<\/a><\/noindex>.<\/p><\/blockquote>\n<p><\/p>\n<h2>Problem 1. Unclear, poorly written articles<\/h2>\n<p>\nIf the documentation is impossible to understand, what is the point? But no one writes unclear articles on purpose. They happen when the author doesn't consider the audience and purpose, fills the text with fluff, and fails to check for errors.<\/p>\n<ul>\n<li><b>Audience<\/b>. Before writing an article, one must think about the reader's level of expertise. It\u2019s logical that in an article for beginners, basic steps shouldn\u2019t be omitted, and technical terms shouldn\u2019t be left unexplained, while in an article about a rare feature needed only by professionals, the meaning of the term PHP shouldn\u2019t be overly elaborated.<\/li>\n<li><b>The goal<\/b>. Another thing to consider in advance is that the author should have a clear objective, define the useful action of the article, and decide what the reader will do after reading it. If this isn't done, it will result in a description for the sake of description. <\/li>\n<li><b>Fluff and errors<\/b>. Too much unnecessary information and bureaucratic language, along with errors and typos, hinder comprehension. Even if the reader isn\u2019t a grammar Nazi, carelessness in the text can turn them off.<\/li>\n<\/ul>\n<p>\nConsider the above tips, and the articles will become clearer\u2014guaranteed. To improve even more, take advantage of our <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/431456\/\"> 50 questions to ask when working on technical documentation<\/a><\/noindex>.<\/p>\n<h2>Problem 2. Articles do not answer all questions<\/h2>\n<p>\nIt\u2019s bad when documentation can\u2019t keep up with development, fails to answer real questions, and errors remain uncorrected for years. These are issues not just for the author, but also for the organization of processes within the company.<\/p>\n<h3>Documentation lags behind development<\/h3>\n<p>\nThe feature is already released, and marketing plans to highlight it, yet it turns out that there is still no new article or translation in the documentation. Because of this, we even had to delay the release. You can ask everyone to pass the task to the technical writers on time as much as you want, but it won\u2019t work. If the process is not automated, the situation will repeat itself.<\/p>\n<p>We have made changes in YouTrack. The task to write an article about the new feature is assigned to the technical writer at the moment the capabilities start testing. Marketing learns about it at that time to prepare for promotion. Notifications are also sent to the corporate messenger Mattermost, so it is impossible to miss news from the developers.<\/p>\n<h3>The documentation does not reflect user requests.<\/h3>\n<p>\nWe are used to working this way: the feature is released, and we tell about it. We describe how to enable, disable, and fine-tune it. But what if the client uses our software in a way we did not anticipate? Or if they encounter errors we haven't considered?<\/p>\n<p>To make the documentation as complete as possible, we recommend analyzing support inquiries, questions on thematic forums, and search engine queries. The most popular topics should be passed to the technical writers so they can supplement existing articles or write new ones.<\/p>\n<h3>Documentation is not improving.<\/h3>\n<p>\nIt is difficult to make everything perfect right away; mistakes will still occur. One can hope for feedback from clients, but they are unlikely to report every typo, inaccuracy, or unclear or missing article. Besides clients, employees read the documentation, which means they see the same mistakes. This can be used! We just need to create conditions in which it is easy to report a problem.<\/p>\n<p>We have a group on the internal portal where employees leave comments, suggestions, and ideas for the documentation. Does support need an article, but it doesn't exist? Did a tester notice an inaccuracy? Did a partner complain to development managers about errors? Everything goes into this group! Technical writers correct some things immediately, move others to YouTrack, and take some under consideration. To ensure the topic doesn\u2019t fade away, we periodically remind everyone about the existence of the group and the importance of feedback.<\/p>\n<h2>Problem 3. The required article takes a long time to find.<\/h2>\n<p>\nAn article that cannot be found is no better than an article that does not exist. The motto of good documentation should be the phrase \"Easy to search, easy to find.\" How can this be achieved?<\/p>\n<p><b>Organize the structure and determine the criteria for topic selection<\/b>. The structure should be as transparent as possible so that the reader does not wonder, \"Where can I find this article?\" In general, there are two approaches: from the interface and from tasks.<\/p>\n<ol>\n<li>From the interface. The content mirrors the sections of the panel. This was the case in the old ISPsystem documentation.<\/li>\n<li>From tasks. The titles of articles and sections reflect user tasks; headings almost always contain verbs and answers to the question \"how to do it.\" We are currently transitioning to this format.<\/li>\n<\/ol>\n<p>\nWhichever approach you choose, make sure that the topic aligns with user queries and is covered in a way that the user can definitively resolve their question.<\/p>\n<p><b>Establish centralized search<\/b>. In an ideal world, the search should work even if you make a typo or get the language wrong. Our search in Confluence currently cannot provide this. If you have many products and the documentation is general, adapt the search to the page the user is on. In our case, search on the main page works for all products, and if you are already in a specific section, only for articles within it.<\/p>\n<p><b>Add a table of contents and breadcrumbs<\/b>. It\u2019s beneficial when each page has a menu and breadcrumbs \u2014 a pathway for the user to the current page with the ability to return to any level. In the old ISPsystem documentation, one had to exit the article to get to the table of contents. This was inconvenient, so we corrected it in the new version.<\/p>\n<p><b>Place links within the product<\/b>. If people repeatedly come to support with the same question, it makes sense to add a hint with its solution in the interface. If you have data or understanding of when the user encounters an issue, you can also notify them through a mailing. This shows care and alleviates the load on support.<\/p>\n<p><img decoding=\"async\" alt=\"User Documentation: What Makes It Bad and How to Fix It\" src=\"\/wp-content\/uploads\/2019\/03\/ddf030647cf3271e0e34924ff5c8116f.jpeg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<i>On the right side in the popup window, there is a link to the article about DNSSEC setup in the ISPmanager domain management section<\/i><\/p>\n<p><b>Set up cross-links within the documentation<\/b>Articles that are interrelated should be \"linked\". If the articles form a sequence, be sure to add forward and backward arrows at the end of each text.<\/p>\n<blockquote><p>Most likely, a person will first seek answers not from you, but from a search engine. It\u2019s disappointing if there are no links to documentation for technical reasons. So, take care of your search engine optimization.<\/p><\/blockquote>\n<p><\/p>\n<h2>Problem 4. Outdated layout hinders perception<\/h2>\n<p>\nIn addition to poor text, the design can spoil the documentation. People are used to reading well-structured materials. Blogs, social media, media \u2014 all content is presented not only beautifully but also conveniently for reading and pleasant to the eye. Therefore, it's easy to understand the frustration of someone who sees the text as in the screenshot below. <\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/hsto.org\/webt\/en\/8-\/3q\/en8-3qj_jpwfiie91efwo_igqtk.png\"><img decoding=\"async\" alt=\"User Documentation: What Makes It Bad and How to Fix It\" src=\"\/wp-content\/uploads\/2019\/03\/0a0762670770950d062e1cd4c0f33f1d.jpeg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<i>In this article, there are so many screenshots and highlights that they hinder rather than help perception (the image is clickable)<\/i><\/p>\n<p>You shouldn't create a long read out of documentation filled with numerous effects, but basic rules need to be taken into account. <\/p>\n<p><b>Layout<\/b>. Determine the width of the main text, font, size, headings, and margins. Involve a designer, and to review the work or manage it independently, read Artem Gorbunov's book \"Typography and Layout\". It presents just one perspective on layout, but it's quite sufficient.<\/p>\n<p><b>Highlights<\/b>. Determine what requires emphasis in the text. Usually, this includes paths in the interface, buttons, code snippets, configuration files, and \"Note\" sections. Specify how these elements will be highlighted and document it. Keep in mind that the fewer highlights there are, the better. When there are too many, the text becomes \"noisy\". Even quotation marks create noise if used too frequently.<\/p>\n<p><b>Screenshots<\/b>. Agree with the team on when screenshots are necessary. It's not essential to illustrate every step. A large number of screenshots, including individual buttons, hinder perception and ruin the layout. Define the size and format of highlights and captions on the screenshots, and document it. Remember that illustrations should always correspond to the written content and be up-to-date. Again, if the product is updated regularly, it will be difficult to keep track of every change.<\/p>\n<p><b>Text length<\/b>Avoid overly long articles. Break them into sections, and if that's not possible, add a table of contents with anchor links at the beginning of the article. A simple way to make an article visually shorter is to hide technical details needed by a narrow audience under a spoiler.<\/p>\n<p><b>Formats<\/b>Combine multiple formats in articles: text, video, and images. This will enhance readability. <\/p>\n<blockquote><p>Don't try to cover up problems with pretty formatting. Honestly, we hoped that a 'wrapper' would save outdated documentation \u2014 it didn't work. The texts had so much visual noise and unnecessary details that the regulations and new layout were powerless.<\/p><\/blockquote>\n<p>\nMuch of what is described above will depend on the platform you use for documentation. For us, it's Confluence. It took some work as well. If you're interested, read the story from our web developer: <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/438236\/\">Confluence for public knowledge base: changing the design and configuring language separation<\/a><\/noindex>.<\/p>\n<h2>Where to start improvements and how to survive<\/h2>\n<p>\nIf your documentation is as vast as ISPsystem's and you don\u2019t know where to begin, start with the most serious issues. If customers don\u2019t understand the documentation \u2014 focus on improving the texts, create regulations, train writers. If the documentation is outdated \u2014 address internal processes. Start with the most popular articles about the most in-demand products: ask support, check website analytics, and search queries. <\/p>\n<p>Let's be clear \u2014 it won\u2019t be easy. And it probably won\u2019t be quick either. Unless you\u2019re just starting and doing it right from the beginning. One thing we know for sure \u2014 it will get better over time. But the process will never end :-).<\/p>\n<p>Source: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ispsystem\/blog\/443648\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a \u0441\u043e\u0444\u0442\u0443 \u2014 \u044d\u0442\u043e \u043f\u0440\u043e\u0441\u0442\u043e \u043d\u0430\u0431\u043e\u0440 \u0441\u0442\u0430\u0442\u0435\u0439. \u041d\u043e \u0434\u0430\u0436\u0435 \u043e\u043d\u0438 \u043c\u043e\u0433\u0443\u0442 \u0432\u044b\u0432\u0435\u0441\u0442\u0438 \u0438\u0437 \u0441\u0435\u0431\u044f. \u0421\u043d\u0430\u0447\u0430\u043b\u0430 \u0434\u043e\u043b\u0433\u043e \u0438\u0449\u0435\u0448\u044c \u043d\u0443\u0436\u043d\u0443\u044e \u0438\u043d\u0441\u0442\u0440\u0443\u043a\u0446\u0438\u044e. \u041f\u043e\u0442\u043e\u043c \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0435\u0448\u044c\u0441\u044f \u0432 \u043c\u0430\u043b\u043e\u043f\u043e\u043d\u044f\u0442\u043d\u043e\u043c \u0442\u0435\u043a\u0441\u0442\u0435. \u0414\u0435\u043b\u0430\u0435\u0448\u044c \u043a\u0430\u043a \u043d\u0430\u043f\u0438\u0441\u0430\u043d\u043e, \u0430 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u043d\u0435 \u0440\u0435\u0448\u0430\u0435\u0442\u0441\u044f. \u0418\u0449\u0435\u0448\u044c \u0434\u0440\u0443\u0433\u0443\u044e \u0441\u0442\u0430\u0442\u044c\u044e, \u043d\u0435\u0440\u0432\u043d\u0438\u0447\u0430\u0435\u0448\u044c\u2026 \u0427\u0435\u0440\u0435\u0437 \u0447\u0430\u0441 \u043f\u043b\u044e\u0451\u0448\u044c \u043d\u0430 \u0432\u0441\u0451 \u0438 \u0443\u0445\u043e\u0434\u0438\u0448\u044c. \u0422\u0430\u043a \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043f\u043b\u043e\u0445\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f. \u0427\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u0442\u0430\u043a\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-42119","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/en\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f: \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u043f\u043b\u043e\u0445\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/en\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-03-17T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-02-18T10:44:55+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47User Documentation: What Makes It Poor, and How to Fix It | ProHoster","description":"Documentation for.","canonical_url":"https:\/\/prohoster.info\/en\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"en_US","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0430\u044f \u0434\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f: \u0447\u0442\u043e \u0434\u0435\u043b\u0430\u0435\u0442 \u0435\u0451 \u043f\u043b\u043e\u0445\u043e\u0439, \u0438 \u043a\u0430\u043a \u044d\u0442\u043e \u0438\u0441\u043f\u0440\u0430\u0432\u0438\u0442\u044c | ProHoster","og:description":"\u0414\u043e\u043a\u0443\u043c\u0435\u043d\u0442\u0430\u0446\u0438\u044f \u043a.","og:url":"https:\/\/prohoster.info\/en\/blog\/news\/polzovatelskaya-dokumentatsiya-chto-delaet-eyo-plohoj-i-kak-eto-ispravit","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-03-17T21:00:00+00:00","article:modified_time":"2020-02-18T10:44:55+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"42119","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 07:20:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:05:22","updated":"2026-01-22 07:20:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/42119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/comments?post=42119"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/posts\/42119\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/media?parent=42119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/categories?post=42119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/en\/wp-json\/wp\/v2\/tags?post=42119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}