The Tiger Archive Description widget is a small, single-purpose dynamic widget built for one job: printing the description text that belongs to whatever archive context the current page represents. Under the hood it calls WordPress core’s own get_the_archive_description() function, which is the same function core themes use to resolve a category description, a tag description, a custom taxonomy term description, a registered post type’s archive description, or an author’s biographical info depending on which kind of archive is currently being viewed. Because Tiger Elements simply defers to that core resolver rather than reinventing the lookup logic, the widget inherits WordPress’s exact rules for which description shows where, which means it behaves predictably and stays in sync with whatever editors type into the “Description” field on a category, tag, or custom taxonomy term, or into a custom post type’s archive description setting.
This widget exists because Theme Builder archive templates need a placeholder that resolves per-context rather than a static text element. If you build one Archive template and assign it to every category and tag archive on the site, a plain text widget would show identical copy everywhere; the Archive Description widget instead pulls in the correct term’s own description automatically, so the same template produces different, relevant copy for “Category: Recipes” versus “Category: Travel” without per-term duplication.
Setting it up
The widget has no Content tab controls at all — there is nothing to configure about what it displays, only how it looks, because the text itself is fully dynamic and pulled from the archive being viewed. Everything lives under the Style tab, split across two sections: Description and Container.
In the Description section you get a responsive Alignment choose-control (Left, Center, Right, Justified), a Text Color control, a Link Color control and matching Link Hover Color control for hyperlinks inside a term description, a full Typography group control, a Text Shadow group control, a responsive Paragraph Spacing slider (0–60px, applied as bottom margin per paragraph), a responsive Max Width slider (px or %, which also auto-centers the block via margin-inline:auto), and a responsive Margin dimensions control.
The Container section adds a Background group control (classic or gradient only — no image option, since this is a text block, not a media container), a responsive Padding control, a Border group control, a responsive Border Radius control, and a Box Shadow group control. Together these let you wrap the description in a card, a tinted panel, or a bordered callout box without touching CSS.
Non-obvious behavior worth knowing
The widget’s render() method only attempts to pull a description when the current request satisfies is_archive() || is_author() || is_category() || is_tag() || is_tax(). On a normal single post, a static page, the blog home, or a search results page, none of those conditions are true, so the widget renders nothing at all (it does not even print an empty wrapper div). This matters if you drop it into a template reused across content types — on non-archive pages it stays invisible, by design.
When there genuinely is no description text — say, a category created without ever filling in its Description field — the widget also renders nothing on the live site, again by design, so you don’t end up with an empty bordered box in your layout. The exception is inside the Elementor editor: because the widget is marked as dynamic content, when the resolved description is empty during editing, it shows a placeholder sentence explaining what the widget is and where it will populate from, purely so you’re not staring at a blank canvas. That placeholder never appears to real visitors.
The description string returned by get_the_archive_description() is already run through the same content filters WordPress applies elsewhere and is safe for output, so the widget passes it through wp_kses_post() rather than plain-text escaping — any HTML markup an editor legitimately added to a term description (links, bold text, even embeds) is preserved, not stripped to plain text.
When to use this vs. related catalog widgets
Archive Description is deliberately narrow. If you need the archive’s heading — “Category: Recipes” or “Author: Jane Doe” rather than the paragraph beneath it — use the sibling Tiger Archive Title widget instead; the two are typically stacked together at the top of an archive template, title first, description second. For post-to-post navigation links, reach for Tiger Post Navigation, and for a trail of ancestor links use Tiger Breadcrumbs — neither touches term description text. The remaining dynamic widgets in this group (Post Comments, Related Items, Pagination, No Results) don’t overlap with this one either, since they handle comment threads, related-content grids, paged-results controls, and empty-query messaging respectively.
Practical tips
- Set Max Width to around 640–760px whenever the description sits inside a full-width archive header — term descriptions read far better at a readable line length than stretched edge-to-edge.
- Because empty descriptions render nothing live, this widget is safe to place in a shared Archive template used across dozens of taxonomies without worrying about empty containers on categories editors never described; just don’t rely on the editor-only placeholder as a signal, since it disappears in production.
- If a term description contains links, set both Link Color and Link Hover Color explicitly — by default they inherit the theme’s global link styling, which can clash with a custom description box background.
- Pair the Container background and padding with a subtle Border Radius and Box Shadow to turn the description into a distinct “about this category” callout card, rather than plain unstyled text floating under the title.