內容簡介
Titula 外掛專注於提升文章的可讀性與結構，提供一致的標題樣式、穩定的目錄錨點，並改善表格在手機上的可讀性，讓讀者更容易掃描與理解內容。
【主要功能】
• 提供一致的標題樣式
• 自動生成穩定的目錄
• 改善表格在手機上的顯示
• 編輯評估功能，提供改善建議
• 內部連結建議，易於接受或忽略
外掛標籤
開發者團隊
原文外掛簡介
Titula is about how an article reads. It gives your headings a consistent
treatment, builds a table of contents with stable anchors, puts the answer
where a reader looking for it will find it, and makes tables legible on a
phone. The markup it produces is semantic, scoped and small, and your post
content is never rewritten.
Better structure and readability make an article easier for a visitor to scan,
navigate and understand, and a clearer foundation for search-friendly content.
No plugin can promise a ranking, and this one does not.
What makes it different
Article design first. Heading styles you can see before you choose them, a
table of contents with anchors that stay readable in Arabic, Spanish and
French, answer-first components that render only when you have filled them in,
and tables that scroll or stack rather than overflowing. One screen, grouped by
what it is for, with a live preview where the choice is visual.
Editorial review, not a score. Open a post and Titula says whether it is
Excellent, Good or Needs attention, then lists the few improvements worth
making, most useful first: “The section Where to stay runs 820 words without
a subheading”, “The introduction runs 340 words before the first section”, “One
page is linked 3 times”, “2 images have no alt attribute”. It also notices
heading levels that skip, runs of dense paragraphs, long stretches a phone
reader has nothing to land on, long articles with no internal links, and
statements that will date. There is no word-count target, no keyword density
and no number to chase. Nothing is rewritten; every item is advice.
Internal link suggestions you approve. Titula reads your published articles
and finds places where one could link to another. Each suggestion shows the
source, the destination, the sentence around it, a score and the reason. You
accept or ignore it.
Accepting one never rewrites your post. The decision is stored and the link is
applied when the page renders, so your content stays exactly as you wrote it
and any choice can be undone. The anchor is always a phrase your article
already contains — nothing is reworded, and no keyword is forced in. Links are
never placed inside existing links, headings, code or captions.
Arabic and RTL, handled properly
Measurement built for the Latin alphabet gives wrong answers in Arabic, and
most plugins never notice. PHP’s own str_word_count() returns zero for Arabic
text, so reading times on Arabic sites are frequently nonsense.
Titula counts by Unicode word boundaries, strips diacritics and the tatweel
before measuring since neither is a letter, discards punctuation-only tokens,
and times Arabic and Latin words at separate adjustable speeds. Heading anchors
stay readable in Arabic instead of collapsing into numbered fragments.
Three optional extras for Arabic publishers:
Latin permalink suggestions. WordPress percent-encodes Arabic slugs, so a
title becomes a URL of the form %d8%a7%d9%84. Valid, but unreadable once
copied, printed or read aloud. Titula suggests a transliteration in the
editor with a checkbox to apply it, warns you when the post is published and
changing it would break existing links, and never changes anything on its
own. Arabic permalinks are a legitimate choice.
Hijri dates, shown beside the Gregorian date rather than replacing it.
The machine-readable date in the markup stays Gregorian, as the HTML
specification requires. Where the intl extension is available the Umm
al-Qura calendar is used; otherwise a tabular calculation, which can differ
from an announced date by a day, so a manual adjustment is provided.
Arabic typography. Raises line height, which the script needs because
letters carry taller ascenders and deeper descenders and diacritics sit above
and below the line. Just as importantly it resets letter-spacing: Arabic
letters join, and spacing them apart pulls the joins open. Themes designed
for Latin text set letter-spacing on headings routinely, and it looks correct
in their previews because those previews are in English.
Reading experience
Reading profiles – Editorial, Travel, Technology, Knowledge, Arabic Editorial
and Minimal – that set the rhythm between paragraphs, lists, figures, tables
and quotations. Fonts always stay your theme’s. Any post can use its own.
Table of contents from your H2 and H3 headings, with stable anchors that stay
readable in Latin, Arabic and accented scripts, in six visual styles. It
marks the section being read, closes itself on a phone after a jump, and, if
you want it to follow the reader, docks in the empty margin beside the
article rather than covering the text. An optional two-pixel progress line.
A Sources list at the end of an article: title, address, publisher and date,
as plain semantic HTML.
Sixteen heading treatments and eight accent choices, so an article looks like
your site rather than like a plugin.
Quick Answer, Key Takeaways and Article Summary, shown above the table of
contents so a reader who wants only the answer finds it first.
FAQ, facts, pros and cons, steps, checklist, related reading and an author
box. Every component optional; one with an empty field renders nothing.
Tables that take their colours from your theme’s own palette rather than
imposing a second one, and that reorganise on a phone instead of asking the
reader to drag them sideways. A table of three to seven columns becomes one
card per row, each value labelled with its own column heading. Very wide
reference tables keep their scroll, because a card that long stops being
readable. Nothing is ever hidden: a phone reader sees exactly what a desktop
reader sees.
Everything is free
There is no paid version, no upsell, no locked feature and no account.
Performance
Rendered articles are cached and reused until the post or a setting changes.
Content analysis is manual, batched and resumable. It never runs on a visitor
request. Also available as wp titula scan.
Stylesheets load only on singular views of a supported post type, and are
split by feature: the table rules are requested when a table is detected in
the content or when dynamic content might render one, rather than on every
article. The script loads only when the article actually has a table of
contents or images, and is deferred.
The editor analysis reads each article once and shares that reading between
every check.
No external requests, no tracking, no jQuery.
Articles built as raw HTML are left alone
If you publish some articles as a complete, self-contained HTML layout pasted
into a Custom HTML block, Titula detects them and does nothing to them at all:
no table of contents, no heading anchors, no components, no wrapper, and not
even a stylesheet request.
Detection is deliberately cautious, since wrongly skipping an ordinary article
is far worse than wrongly processing one. It looks for signals an ordinary post
never produces: a style element in the content, most of the article sitting
inside Custom HTML blocks, or heavy inline styling. A long article containing
one small embed block is not affected.
Every post also carries a Processing control in the editor, in both the block
and classic editors, so you can force either answer. Excluded articles are
still valid destinations for links from elsewhere: leaving an article alone
means not modifying it, not refusing to point at it.
What Titula does not do
It writes no SEO title, meta description, canonical URL, robots directive,
Open Graph or Twitter tag, sitemap or redirect.
It produces no structured data – not for FAQs, articles, breadcrumbs or
sources – and never modifies schema from another plugin.
It never changes an article’s published or modified date, and never
optimises, converts or resizes an image file.
It generates no text and contacts no external service or AI model.
It cannot promise a ranking, a Google AI Overview placement or a citation in
any AI assistant. No plugin can, and this one does not claim to.
It styles nothing outside the article container, so your theme is untouched.
