{"id":358928,"date":"2026-08-29T22:02:18","date_gmt":"2026-08-29T22:02:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/titula\/"},"modified":"2026-09-11T08:39:03","modified_gmt":"2026-09-11T08:39:03","slug":"titula","status":"publish","type":"plugin","link":"https:\/\/he.wordpress.org\/plugins\/titula\/","author":23555200,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.1.4","stable_tag":"1.1.4","tested":"7.1.1","requires":"6.0","requires_php":"7.4","requires_plugins":null,"header_name":"Titula","header_author":"ACAART","header_description":"Beautiful articles, clear structure. Editorial analysis, internal link suggestions you approve, an automatic table of contents and answer-first components \u2014 with word counts, permalinks and typography that are correct for Arabic. Adds no schema and no meta tags, so it works alongside your SEO plugin instead of competing with it.","assets_banners_color":"fcfcfd","last_updated":"2026-09-11 08:39:03","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/acaart.com\/","rating":5,"author_block_rating":0,"active_installs":0,"downloads":161,"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"abourri","date":"2026-08-29 22:02:03","revision":3671909},"1.1.4":{"tag":"1.1.4","author":"abourri","date":"2026-09-11 08:39:03","revision":3691059}},"upgrade_notice":{"1.1.4":"<p>One visible change: if your table of contents still collapsed after eight\nentries because that was the old default, it now shows every section. Set a\nnumber under Contents to bring the button back.<\/p>","1.1.3":"<p>Safe to upgrade. The new back-link arrow defaults to the shape 1.1.2 used, so\nnothing changes on your articles until you choose another.<\/p>","1.1.2":"<p>Safe to upgrade. Admin screens only; no setting is renamed, moved or reset, and\nnothing on the front end changes.<\/p>","1.1.1":"<p>Safe to upgrade. No setting is renamed, moved in storage or reset; the admin\nscreens are reorganised and every old address still works.<\/p>","1.1.0":"<p>Safe to upgrade. Your current behaviour is preserved: the new direction\nhandling stays off, and generic custom-field names keep working, until you\nchange them yourself. No settings are reset and no content is altered.<\/p>","1.0.0":"<p>First public release.<\/p>"},"ratings":{"1":0,"2":0,"3":0,"4":0,"5":1},"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3671909,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3671909,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3671909,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3671909,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.4"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1113,19933,12158,5811,10851],"plugin_category":[],"plugin_contributors":[278217],"plugin_business_model":[],"class_list":["post-358928","plugin","type-plugin","status-publish","hentry","plugin_tags-arabic","plugin_tags-internal-linking","plugin_tags-readability","plugin_tags-rtl","plugin_tags-table-of-contents","plugin_contributors-abourri","plugin_committers-abourri"],"banners":{"banner":"https:\/\/ps.w.org\/titula\/assets\/banner-772x250.png?rev=3671909","banner_2x":"https:\/\/ps.w.org\/titula\/assets\/banner-1544x500.png?rev=3671909","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/titula\/assets\/icon-128x128.png?rev=3671909","icon_2x":"https:\/\/ps.w.org\/titula\/assets\/icon-256x256.png?rev=3671909","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Titula is about how an article reads. It gives your headings a consistent\ntreatment, builds a table of contents with stable anchors, puts the answer\nwhere a reader looking for it will find it, and makes tables legible on a\nphone. The markup it produces is semantic, scoped and small, and your post\ncontent is never rewritten.<\/p>\n\n<p>Better structure and readability make an article easier for a visitor to scan,\nnavigate and understand, and a clearer foundation for search-friendly content.\nNo plugin can promise a ranking, and this one does not.<\/p>\n\n<h4>What makes it different<\/h4>\n\n<p><strong>Article design first.<\/strong> Heading styles you can see before you choose them, a\ntable of contents with anchors that stay readable in Arabic, Spanish and\nFrench, answer-first components that render only when you have filled them in,\nand tables that scroll or stack rather than overflowing. One screen, grouped by\nwhat it is for, with a live preview where the choice is visual.<\/p>\n\n<p><strong>Editorial Readiness.<\/strong> Open a post and Titula reports five dimensions \u2014\nAnswer Clarity, Content Structure, Reader Experience, Internal Linking, Search\nand AI Readiness \u2014 with a plain sentence and a short list of what to fix. It\nnames specific problems: a skipped heading level, an introduction that buries\nthe answer, a section running long without a subheading, images missing\ndimensions. There is no word-count target, no keyword density and no keyword\nrepetition in the model, because none of those measure whether an article is\ngood.<\/p>\n\n<p><strong>Internal link suggestions you approve.<\/strong> Titula reads your published articles\nand finds places where one could link to another. Each suggestion shows the\nsource, the destination, the sentence around it, a score and the reason. You\naccept or ignore it.<\/p>\n\n<p>Accepting one never rewrites your post. The decision is stored and the link is\napplied when the page renders, so your content stays exactly as you wrote it\nand any choice can be undone. The anchor is always a phrase your article\nalready contains \u2014 nothing is reworded, and no keyword is forced in. Links are\nnever placed inside existing links, headings, code or captions.<\/p>\n\n<h4>Arabic and RTL, handled properly<\/h4>\n\n<p>Measurement built for the Latin alphabet gives wrong answers in Arabic, and\nmost plugins never notice. PHP's own <code>str_word_count()<\/code> returns zero for Arabic\ntext, so reading times on Arabic sites are frequently nonsense.<\/p>\n\n<p>Titula counts by Unicode word boundaries, strips diacritics and the tatweel\nbefore measuring since neither is a letter, discards punctuation-only tokens,\nand times Arabic and Latin words at separate adjustable speeds. Heading anchors\nstay readable in Arabic instead of collapsing into numbered fragments.<\/p>\n\n<p>Three optional extras for Arabic publishers:<\/p>\n\n<ul>\n<li><strong>Latin permalink suggestions.<\/strong> WordPress percent-encodes Arabic slugs, so a\ntitle becomes a URL of the form <code>%d8%a7%d9%84<\/code>. Valid, but unreadable once\ncopied, printed or read aloud. Titula suggests a transliteration in the\neditor with a checkbox to apply it, warns you when the post is published and\nchanging it would break existing links, and never changes anything on its\nown. Arabic permalinks are a legitimate choice.<\/li>\n<li><strong>Hijri dates,<\/strong> shown beside the Gregorian date rather than replacing it.\nThe machine-readable date in the markup stays Gregorian, as the HTML\nspecification requires. Where the <code>intl<\/code> extension is available the Umm\nal-Qura calendar is used; otherwise a tabular calculation, which can differ\nfrom an announced date by a day, so a manual adjustment is provided.<\/li>\n<li><strong>Arabic typography.<\/strong> Raises line height, which the script needs because\nletters carry taller ascenders and deeper descenders and diacritics sit above\nand below the line. Just as importantly it resets <code>letter-spacing<\/code>: Arabic\nletters join, and spacing them apart pulls the joins open. Themes designed\nfor Latin text set letter-spacing on headings routinely, and it looks correct\nin their previews because those previews are in English.<\/li>\n<\/ul>\n\n<h4>Reading experience<\/h4>\n\n<ul>\n<li>Table of contents from your H2 and H3 headings, with stable anchors that stay\nreadable in Latin, Arabic and accented scripts, in six visual styles. Long\nlists collapse behind a \"View all sections\" control.<\/li>\n<li>Sixteen heading treatments and eight accent choices, so an article looks like\nyour site rather than like a plugin.<\/li>\n<li>Quick Answer, Key Takeaways and Article Summary, shown above the table of\ncontents so a reader who wants only the answer finds it first.<\/li>\n<li>FAQ, facts, pros and cons, steps, checklist, related reading and an author\nbox. Every component optional; one with an empty field renders nothing.<\/li>\n<li>Tables that take their colours from your theme's own palette rather than\nimposing a second one, and that reorganise on a phone instead of asking the\nreader to drag them sideways. A table of three to seven columns becomes one\ncard per row, each value labelled with its own column heading. Very wide\nreference tables keep their scroll, because a card that long stops being\nreadable. Nothing is ever hidden: a phone reader sees exactly what a desktop\nreader sees.<\/li>\n<\/ul>\n\n<h4>Everything is free<\/h4>\n\n<p>There is no paid version, no upsell, no locked feature and no account.<\/p>\n\n<h4>Performance<\/h4>\n\n<ul>\n<li>Rendered articles are cached and reused until the post or a setting changes.<\/li>\n<li>Content analysis is manual, batched and resumable. It never runs on a visitor\nrequest. Also available as <code>wp titula scan<\/code>.<\/li>\n<li>Stylesheets load only on singular views of a supported post type, and are\nsplit by feature: the table rules are requested when a table is detected in\nthe content or when dynamic content might render one, rather than on every\narticle. The script loads only when the article actually has a table of\ncontents or images.<\/li>\n<li>No external requests, no tracking, no jQuery.<\/li>\n<\/ul>\n\n<h4>Articles built as raw HTML are left alone<\/h4>\n\n<p>If you publish some articles as a complete, self-contained HTML layout pasted\ninto a Custom HTML block, Titula detects them and does nothing to them at all:\nno table of contents, no heading anchors, no components, no wrapper, and not\neven a stylesheet request.<\/p>\n\n<p>Detection is deliberately cautious, since wrongly skipping an ordinary article\nis far worse than wrongly processing one. It looks for signals an ordinary post\nnever produces: a <code>style<\/code> element in the content, most of the article sitting\ninside Custom HTML blocks, or heavy inline styling. A long article containing\none small embed block is not affected.<\/p>\n\n<p>Every post also carries a Processing control in the editor, in both the block\nand classic editors, so you can force either answer. Excluded articles are\nstill valid destinations for links from elsewhere: leaving an article alone\nmeans not modifying it, not refusing to point at it.<\/p>\n\n<h4>What Titula does not do<\/h4>\n\n<ul>\n<li>It writes no SEO title, meta description, canonical URL or robots directive.<\/li>\n<li>It produces no structured data, and never modifies schema from another plugin.<\/li>\n<li>It generates no text and contacts no external service or AI model.<\/li>\n<li>It cannot promise a ranking, a Google AI Overview placement or a citation in\nany AI assistant. No plugin can, and this one does not claim to.<\/li>\n<li>It styles nothing outside the article container, so your theme is untouched.<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>Install through Plugins &gt; Add New, or upload the ZIP.<\/li>\n<li>Activate it.<\/li>\n<li>Open Titula in the admin menu. The Overview carries a five-step setup guide;\nfollow it to Appearance and pick one of the four starting points: People\nFirst, Travel, Technology or Editorial. That is the whole setup.<\/li>\n<li>Optional: run a scan from Analysis to see what your published articles are\nmissing, or from Internal Linking to review link suggestions.<\/li>\n<\/ol>\n\n<p>Everything is configured in that one screen; there is no separate Titula page\nunder Settings. Every individual setting is still there, but you should not\nneed it on day one.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20this%20replace%20rank%20math%20or%20yoast%3F\"><h3>Does this replace Rank Math or Yoast?<\/h3><\/dt>\n<dd><p>No, and it is designed not to. Titula adds no schema and no meta tags. Keep\nusing your SEO plugin exactly as you do now.<\/p><\/dd>\n<dt id=\"will%20it%20change%20my%20theme%20or%20my%20other%20pages%3F\"><h3>Will it change my theme or my other pages?<\/h3><\/dt>\n<dd><p>No. Every CSS rule is scoped inside the article container. Your header, footer,\nsidebar, widgets and every page outside the selected post types are untouched.<\/p><\/dd>\n<dt id=\"does%20it%20modify%20my%20post%20content%20in%20the%20database%3F\"><h3>Does it modify my post content in the database?<\/h3><\/dt>\n<dd><p>No. Components and approved internal links are applied when the page renders.\nYour content stays exactly as you wrote it, and anything you enable can be\nswitched off with no trace left behind.<\/p><\/dd>\n<dt id=\"does%20it%20require%20advanced%20custom%20fields%3F\"><h3>Does it require Advanced Custom Fields?<\/h3><\/dt>\n<dd><p>No. Titula uses ACF when it is present and plain post meta when it is not.<\/p><\/dd>\n<dt id=\"will%20it%20change%20my%20arabic%20permalinks%3F\"><h3>Will it change my Arabic permalinks?<\/h3><\/dt>\n<dd><p>Only if you tick the box in the editor and save. Nothing happens in bulk,\nnothing happens on activation, and the panel warns you first when the post is\nalready published.<\/p><\/dd>\n<dt id=\"how%20accurate%20is%20the%20hijri%20date%3F\"><h3>How accurate is the Hijri date?<\/h3><\/dt>\n<dd><p>It is calculated, not announced. In most countries the start of a Hijri month\nis declared by observation of the crescent, and no formula predicts that. The\nsettings screen tells you which method your server uses and offers a manual\nadjustment of up to two days.<\/p><\/dd>\n<dt id=\"does%20it%20send%20my%20content%20anywhere%3F\"><h3>Does it send my content anywhere?<\/h3><\/dt>\n<dd><p>No. All analysis runs on your own server. The plugin makes no external requests\nof any kind.<\/p><\/dd>\n<dt id=\"what%20happens%20to%20my%20data%20if%20i%20uninstall%3F\"><h3>What happens to my data if I uninstall?<\/h3><\/dt>\n<dd><p>Plugin settings are removed. Editorial decisions stored on individual posts,\nsuch as which link suggestions you accepted, are left in place so that\nreinstalling does not lose your work.<\/p><\/dd>\n<dt id=\"will%20it%20improve%20my%20rankings%3F\"><h3>Will it improve my rankings?<\/h3><\/dt>\n<dd><p>It cannot promise that, and no honest plugin can. What it does is make articles\nclearer, better structured and better connected to each other.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.1.4<\/h4>\n\n<p>The table of contents shows the whole article again, and four issues Plugin\nCheck raised are fixed.<\/p>\n\n<ul>\n<li>The list no longer folds away after eight entries. A table of contents exists\nto show the shape of the piece, and on a guide with twelve sections it was\nshowing two thirds of it and a button. Sites still sitting on that old\ndefault are moved to the full list on upgrade; a site that chose its own\nnumber keeps it.<\/li>\n<li>Fixed: on a theme that does not define <code>screen-reader-text<\/code>, the icon-only\nback link printed the word \"Contents\" beside the icon. The plugin now carries\nits own implementation of that class and no longer depends on the theme.<\/li>\n<li>The row is the target in the table of contents, not just the words: hover and\nfocus cover the whole entry, and the entry you are reading is marked on its\nedge without the text shifting.<\/li>\n<li>The heading you arrive at from the table of contents is outlined for a moment,\nso a jump down a long article lands somewhere visible.<\/li>\n<li>Headings wrap evenly rather than leaving one word on the last line.<\/li>\n<li>Focus rings on the contents panel, its \"view all\" button and its entries.<\/li>\n<li>A sticky contents panel stops scrolling the article when its list reaches the\nend.<\/li>\n<li>Plugin Check: translator comments on three strings, the percent-encoded\nArabic URL example moved out of a translatable sentence, and WPML's own\nfilter name documented rather than flagged.<\/li>\n<\/ul>\n\n<h4>1.1.3<\/h4>\n\n<p>The live preview moved to where it can be seen, and the back link got a choice\nof arrow.<\/p>\n\n<ul>\n<li>Live preview beside the heading controls instead of below them, following\nthe page as you scroll. It was at the foot of a long section, far enough down\nthat people did not know the plugin had one.<\/li>\n<li>Six shapes for the \"back to contents\" link: the original list-and-arrow, a\nplain arrow, a chevron, an arrow meeting a rule, a return arrow and a plain\nlist. Picked from cards that draw the real icon; mirrored in a right-to-left\narticle so an arrow still points back the way the reader came.<\/li>\n<li>Press \/ anywhere on the settings screen to jump to the finder, and the\nfinder now counts a picker once rather than once per card.<\/li>\n<li>The section list marks the group you are reading, opening a section takes\nyou to the top of it, and its heading takes focus so a screen reader says\nwhere you are.<\/li>\n<li>Printing an article no longer prints \"Contents\" beside every heading, keeps\na heading with the section it introduces, and avoids breaking a panel, a\ntable row or a figure across pages.<\/li>\n<li>The icon-only back link has a tap target a finger can hit, and a focus ring\na keyboard user can see.<\/li>\n<\/ul>\n\n<h4>1.1.2<\/h4>\n\n<p>Orientation. The dashboard now answers three questions before it is asked: what\nis this section set to, what else is in it, and where is that one setting.<\/p>\n\n<ul>\n<li>A finder above the settings. Type two letters and every matching control on\nthe screen is listed with the section it lives in; choosing one opens that\nsection, scrolls to the control and marks it.<\/li>\n<li>Each section shows what it is currently set to, read from your saved settings\n\n<ul>\n<li>the article style, the heading system, how many components are on.<\/li>\n<\/ul><\/li>\n<li>Every group of settings is now titled, and a section with several of them\nprints a short list of links to each.<\/li>\n<li>The sixteen components are grouped by the job they do rather than listed in\none run of sixteen.<\/li>\n<li>A section you have edited but not saved is marked in the navigation, and the\nend of each design section offers the next one.<\/li>\n<li>The screen was redrawn on two surfaces - a navigation panel and the open\nsection - so a card no longer sits inside a card. The navigation follows you\ndown a long section.<\/li>\n<li>Fewer bytes: the settings form is printed only on a section that has\ncontrols, and the library summary only where a figure is shown.<\/li>\n<\/ul>\n\n<h4>1.1.1<\/h4>\n\n<p>One administrative home, and a clearer product. Every setting is now edited in\nthe Titula dashboard, grouped by what it is for: Article design, Article\nhealth, Optional and Advanced. Nothing moved in storage and no setting was\nrenamed or removed.<\/p>\n\n<ul>\n<li>Saving returns you to the section you were editing. The form's return address\nis written by the server for the open section instead of being taken from the\nrequest URL, which is why a save used to land on Overview.<\/li>\n<li>Settings &gt; Titula is no longer a separate destination. The old address still\nworks and forwards to the section that replaced it, as do the old tab\naddresses.<\/li>\n<li>Information Quality is gone from the dashboard. The measurement itself stays:\nit is one of the five Editorial Readiness dimensions in the post editor.<\/li>\n<li>Internal Linking keeps every feature and moves under Optional. Topic\nstructure and decision history are shown inside it rather than as tabs of\ntheir own, and it no longer supplies the dashboard's headline figures.<\/li>\n<li>How It Works is replaced by a five-step setup guide on the Overview.<\/li>\n<li>Arabic typography, text direction, reading speed, Latin permalinks and Hijri\ndates moved from the linking screen to Appearance, where reading comfort is\ndecided. The editorial preset moved to Components; the interface language to\nAdvanced.<\/li>\n<li>The scoped reset buttons print after everything they reset, rather than in\nthe middle of the section.<\/li>\n<li>Analysis reports what articles are missing; its link counts moved to Internal\nLinking.<\/li>\n<li>Fewer queries: the library summary is read only by the screens that show it.<\/li>\n<li>Narrow screens no longer scroll sideways, and the link-rules table scrolls\ninside its own box.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<p>Presentation, compatibility and correctness. An existing site keeps its current\nbehaviour on upgrade: the two settings introduced here that could change what a\nvisitor sees are written to their previous values during the upgrade, and only\nchange if you choose to change them.<\/p>\n\n<p><strong>New<\/strong><\/p>\n\n<ul>\n<li><strong>Headings Studio<\/strong>: a Headings screen with a visual style picker instead of\na dropdown of names, six coordinated heading systems that set H2, H3 and H4\ntogether, hierarchy controls for weight, accent strength, decoration width,\nnumbering and alignment, and a live preview with desktop, tablet, mobile,\nLTR and RTL views. Nothing is saved until you press Save Changes.<\/li>\n<li>Sixteen heading treatments and six table-of-contents styles.<\/li>\n<li>Seven accent palettes plus a custom colour. The default still follows the\ncolour detected from your theme.<\/li>\n<li>Text direction read from the article's own words rather than the site\nlanguage, so an article written in a different script from the site is no\nlonger laid out the wrong way round. Off for existing sites until enabled.<\/li>\n<\/ul>\n\n<p><strong>Fixed<\/strong><\/p>\n\n<ul>\n<li>Component stylesheets are chosen from a single list of every component, so an\narticle using only Facts, Verdict, Pros and cons, Checklist, Key takeaways,\nSummary, Author or Related no longer renders unstyled.<\/li>\n<li>Language is no longer guessed from text direction. Persian and Urdu are not\nArabic and French is not English, so a <code>lang<\/code> attribute is now written only\nwhere a multilingual plugin, the site locale or a filter actually knows the\nanswer, and omitted otherwise.<\/li>\n<li>Generic meta names such as <code>faq<\/code>, <code>summary<\/code> and <code>steps<\/code> are no longer read on\nnew installations, where they collide with ACF fields, themes and other\nplugins. Existing installations keep reading them, and no field belonging to\nanother plugin is ever written to or deleted.<\/li>\n<li>Custom fields returning repeaters, groups, image arrays, relationships or\nnested arrays no longer produce \"Array to string conversion\" warnings.<\/li>\n<li>Live analysis in the editor now judges the content on screen rather than the\nlast saved version, including whether the article is excluded from\nprocessing.<\/li>\n<li>The table stylesheet is requested when a table is detected in the content or\nwhen a shortcode or dynamic block might render one, rather than on every\narticle on a site with tables enabled. Detection is deliberately cautious:\nit errs towards loading rather than risk an unstyled table.<\/li>\n<li>Admin confirmation dialogs and layout moved out of inline attributes into the\nenqueued stylesheet and script, keeping the messages translatable.<\/li>\n<li>Dashboard progress text is fully translatable instead of assembling an\nEnglish word onto a translated phrase.<\/li>\n<li>Uninstall now also removes the rebuildable content index and suggestion list,\nwhile keeping editorial decisions such as chosen styles, accepted links and\nreview dates.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First public release.<\/li>\n<\/ul>","raw_excerpt":"Better article design and a better reading experience: heading styles, a table of contents, answer-first components and readable tables.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/358928","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=358928"}],"author":[{"embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/abourri"}],"wp:attachment":[{"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=358928"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=358928"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=358928"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=358928"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=358928"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/he.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=358928"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}