Clouddy

FAQ

How do I change the tag sizes?

In Settings → Clouddy set the minimum and maximum text size and the unit (rem/em/px). Each
tag’s size is interpolated between those values based on the tag’s popularity.

Can I style the cloud with my own CSS?

Yes. The default stylesheet only sets custom properties on the container; every value can be
overridden with regular CSS, and the default stylesheet can be dequeued entirely.

How do I embed the tag cloud?

Three ways, all rendering the same cloud from the global settings (Settings → Clouddy):

• Block — add the “Clouddy — Tag Cloud” block in the block editor.
• Shortcode — [clouddy] (accepts attributes, see below).
• Widget — the “Clouddy — Tag Cloud” classic widget (themes with widget areas).

Which shortcode attributes are supported?

Every attribute is optional and overrides the global setting for that single cloud, e.g. [clouddy mode="hybrid" number="40" order="name_asc"]:

• mode — which tags to include: popular, rare, random, hybrid. Default popular.
• number — total number of tags (integer, min 1). Default 30.
• order — display order: count_desc, count_asc, name_asc, name_desc, random, length_center, count_center, rare_center. Default count_desc. The *_center orders place the top-ranked tags in the middle (lens effect).
• rare_count — hybrid mode only: how many of the total are the rarest (integer, capped at number). Default 5.
• taxonomy — source taxonomy. Default post_tag.
• exclude — comma-separated term IDs to skip, e.g. exclude="12,34".
• min_size / max_size — smallest / largest text size (numbers). Defaults 0.8 / 2.0.
• unit — size unit: rem, em, px, pt. Default rem.
• color_a / color_b — hex colors of the rarest / most popular tags. Defaults #888888 / #222222.
• show_count — append the post count to each tag (true / false). Default false.
• aria_label — accessibility label for the cloud container. Default Tag cloud.
• ttl_minutes — cache lifetime in minutes. Default 720 (12 h).

What is the cache lifetime (TTL) and what does it do?

Clouddy caches the set of tags it queries (using the WordPress Transients API) so the database
is not queried on every page load. The cache lifetime (ttl_minutes) is how long that cached
set is kept before it is rebuilt from the database — default 720 minutes (12 hours). It is only
a safety net: the cache is also refreshed automatically whenever content changes (a post is
saved or deleted, or tags are added, edited or removed). You rarely need to change it; lower it
only if you want a tighter upper bound on how stale the cloud can be.

The “random” order does not change on every page reload. Why?

The order is computed in PHP when the page is rendered — Clouddy uses no JavaScript. If you use
a full-page caching plugin or a CDN (for example LiteSpeed Cache, WP Super Cache, W3 Total
Cache, or a host/CDN cache), the generated HTML — including that one random order — is stored
and served to visitors, so the order only changes when that page cache is regenerated. This is
expected for any server-rendered random content. To reshuffle on every view despite caching you
would need client-side randomization (JavaScript), which Clouddy intentionally avoids. Either
exclude that page from full-page caching, or accept that the order refreshes when the cache does.