Uplink Editorial Semantics adds editorial markup tools to Rich Text fields in the WordPress Block Editor. The saved content uses standard HTML and does not require front-end JavaScript.<\/p>\n\n
Inline formats:<\/p>\n\n
q<\/code>) with optional BCP 47 language and citation URL attributes.<\/li>\n- Citation<\/strong> (
cite<\/code>) for the title of a creative work.<\/li>\n- Abbreviation<\/strong> (
abbr<\/code>) with a required expanded form.<\/li>\n- Defining instance<\/strong> (
dfn<\/code>) for the occurrence of a term being defined.<\/li>\n- Inline span<\/strong> (
span<\/code>) with optional sanitized CSS classes and one custom data-*<\/code> name\/value pair for cases where no semantic element is appropriate.<\/li>\n- Link attributes<\/strong> for adding one custom
data-*<\/code> name\/value pair and an optional aria-label<\/code> to an existing native hyperlink.<\/li>\n<\/ul>\n\nThe Editorial Quotation<\/strong> block saves a figure<\/code> containing a blockquote<\/code> and an optional figcaption<\/code>. Its quotation area accepts Paragraph, Heading, and List blocks. The plugin supplies no front-end styling, allowing the active theme to control presentation.<\/p>\n\nDevelopment<\/h3>\n\n
Human-readable source is included in the plugin's src<\/code> directory, and the build configuration is included in package.json<\/code>. Public source and contribution history are also available at https:\/\/github.com\/stphnwlkr\/uplink-editorial-semantics.<\/p>\n\nTo build the production assets, install Node.js and npm, run npm install<\/code>, and then run npm run build<\/code>. The compiled files are written to the build<\/code> directory.<\/p>\n\n\n\n- Install and activate the plugin.<\/li>\n
- Open a post or page in the Block Editor.<\/li>\n
- Select text in a Rich Text field to use the added formatting controls, or insert the Editorial Quotation block.<\/li>\n<\/ol>\n\n\n
\nWhere are the inline formats?<\/h3><\/dt>\nSelect text in a supported Rich Text field. The available controls appear with the editor's other inline formatting tools.<\/p><\/dd>\n
When should I use Citation?<\/h3><\/dt>\nUse cite<\/code> for the title of a work, such as a book, article, film, or report. Do not use it merely to italicize a person's name.<\/p><\/dd>\nWhen should I use Inline Span?<\/h3><\/dt>\nUse it only when no semantic HTML element describes the text and you need a stable CSS or JavaScript hook. The plugin adds its own base class, sanitizes the custom class tokens you enter, and can add one custom data attribute. Enter the part after data-<\/code> using lowercase letters, numbers, and hyphens; for example, the name state<\/code> and value active<\/code> save as data-state=\"active\"<\/code>.<\/p><\/dd>\nHow do I add attributes to a link?<\/h3><\/dt>\nPlace the text cursor inside an existing hyperlink or select linked text, then choose Link attributes<\/strong> from the inline formatting toolbar. You can enter the part after data-<\/code> and its value, an aria-label<\/code>, or both. The plugin preserves these attributes when the link is later edited with WordPress's native link controls.<\/p>\n\nAn aria-label<\/code> replaces the link's visible text as its accessible name. Normally, include the visible link text in the complete label. For example, a visible Download report<\/strong> link that opens a new tab could use Download report (opens in a new tab)<\/code>.<\/p><\/dd>\nDoes the plugin add front-end scripts or styles?<\/h3><\/dt>\nNo. It saves standard HTML and leaves its presentation to your theme.<\/p><\/dd>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\nPublished HTML remains in the content. The custom formatting controls and Editorial Quotation editing interface are unavailable until the plugin is reactivated.<\/p><\/dd>\n
Does the plugin collect data?<\/h3><\/dt>\nNo. It stores no plugin settings, sends no network requests, and performs no tracking.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n\n- Initial WordPress.org release.<\/li>\n
- Added inline quotation, citation, abbreviation, defining-instance, and controlled inline-span formats.<\/li>\n
- Added an optional custom
data-*<\/code> name\/value pair to inline spans.<\/li>\n- Added a companion control for custom
data-*<\/code> attributes on native hyperlinks.<\/li>\n- Added an optional
aria-label<\/code> field with accessibility guidance for native hyperlinks.<\/li>\n- Added the Editorial Quotation block with an optional attribution.<\/li>\n<\/ul>","raw_excerpt":"Adds semantic inline formats, controlled inline spans, and a structured quotation block to the WordPress Block Editor.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/357683","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=357683"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/stphnwlkr"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=357683"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=357683"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=357683"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=357683"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=357683"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=357683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}