No, SleekPixel is read-only against Loco's storage. It opens the PO file through Loco's Loco_fs_File API to extract header data, then closes it without writing. Translation work, plural form handling, and string saves remain Loco's responsibility entirely, so there is zero risk of the integration corrupting a translation file.

From the Language header in the PO file, which Loco populates from the WordPress locale code when the file is created. For a German pack the header reads Language: de_DE, and SleekPixel renders just DE as the mark for visual clarity. You can override the mark per post via a sleekpixel_mark custom field if needed.

Yes. The template supports an alternate variant that renders a small SVG flag in the corner mark slot, using the locale to country mapping from WordPress core. The flag variant is helpful for community pages that want a more visual identity, especially when sharing across multiple cultures simultaneously.

If the PO file lives only in the plugin's own languages directory and not under wp-content/languages/loco, the integration still reads it through Loco's filesystem API. Loco indexes both bundled and user storage files, so SleekPixel can render shares for plugin-shipped translations and for user-edited ones equivalently.

By default the count reflects what Loco itself reports in its admin panel, which is the total number of source strings in the project, not just the translated ones. A separate template field can render translated count over total, useful for in-progress translation posts that show progress like 942 of 1284 translated.

SleekPixel reads PO and MO files, which are the WordPress core localisation format that Loco manages, independent of WPML or Polylang. If you also run Polylang the front end might serve different locales per URL, but the PO based card on release posts works the same way because the post itself is in one canonical locale.

Yes. The standard SleekPixel REST registration adds a sleekpixel_image field to every post type bound to a template, including the post type or tag where your translation release posts live. A static site generator or release dashboard can read the image URL alongside the title in a single REST call.

The PO project name encodes the original plugin slug, so the brand label on existing release cards continues to read the old slug. Regenerate the cache through the SleekPixel admin or WP-CLI to refresh the brand label using the renamed slug if you want history cards to reflect the rename consistently.