Yes. The template reads any WordPress post meta key by name. Map trademark_number, jurisdiction, class, and any other field you store on the post. The rendered image picks up the values automatically when the post saves, so counsel does not need to retype anything that already lives in WordPress.

Yes. If a single post represents a multi-jurisdiction filing, store the jurisdictions as a taxonomy or repeating meta and the template can render them as a list in the meta line. You can also split one filing into multiple posts and let each one render its own card if that fits your editorial flow better.

By default the trademark card renders at 1200 by 1200 for LinkedIn feed posts. The same template can also emit a 1200 by 630 OG image and a 1200 by 675 Twitter card, all from one definition. You pick which sizes to enable per page group.

Yes. Use the featured image or a dedicated meta field as the wordmark slot. Each post can carry its own wordmark, which is helpful if you have sub-brands or product marks that file under separate registrations. The template scales the asset to the reserved area without manual cropping.

Save the post again. SleekPixel regenerates the cached image during the save hook, so the next request for the card returns the corrected version. Social platforms that cached the previous image can be refreshed through their respective debuggers, but your site and internal links serve the new file immediately.

Yes. The template reads any meta key WordPress stores, so ACF, Meta Box, Pods, and plain update_post_meta all work the same way. Point the template at the meta key your fields plugin writes to and the value flows into the image without further wiring.

Yes. Class is just another meta field. You can render it on the badge, the meta line, or as part of the subtitle. If the description is long, the template wraps it or you can store a short version in a separate field for display while keeping the full description in the post body.

It is cached. The first request after publish generates the PNG and stores it. Subsequent requests serve the cached file straight from your media library or CDN. Editing the post invalidates the cache and triggers a regeneration so the file always matches the current post content.