SleekPixel for GreenShift blocks
SleekPixel renders a 1200 by 630 OG image on save for any post built with GreenShift blocks. Reads title, category, and any custom field. Lives next to the blocks without changing them.
♾️ Lifetime License available
GreenShift extends Gutenberg, the share layer needs its own engine
GreenShift is one of the more capable block libraries on top of Gutenberg, including animation, query loop, and dynamic-content blocks that move WordPress sites closer to a full builder experience without leaving the block editor. Sites built with GreenShift cover most marketing and content needs natively. The share preview is the gap, since GreenShift does not generate per-post OG images.
SleekPixel covers the share layer at the post-meta level. It hooks save_post on any post type, reads native fields plus ACF, Meta Box, and any other custom field, and renders a 1200 by 630 PNG. GreenShift keeps composing the visible page, SleekPixel writes the og:image meta tag in the document head. Both layers update independently because they do not share code paths.
For sites running GreenShift query loops over a CPT, every detail post the loop links to gets a per-post share card. Editors define the loop and detail layout once in GreenShift, SleekPixel covers each detail URL automatically.
Workflow
From GreenShift save to share image
Enable post types
Map fields
Save the post
Meta tags update
Output
Sample card for a GreenShift post
Rendered from the post's title, category, and brand color. Same template, every GreenShift post.
Comparison
GreenShift default versus SleekPixel
SEO plugin fallback
- Every GreenShift post falls back to the SEO plugin's global OG image
- Block-level styles never reach the share preview
- Custom fields surfaced in GreenShift dynamic content stay invisible to the OG image
- Brand refresh leaves all past share cards in place
- Per-post Canva exports do not scale to a full GreenShift site
SleekPixel
- Hooks save_post for any post type GreenShift renders for
- Reads ACF, Meta Box, and native fields used in GreenShift dynamic content
- Self-hosted render with no per-image fees
- Template export moves between GreenShift sites
- Bulk regenerate covers a full GreenShift site
Features
What SleekPixel gives you for GreenShift blocks
Block agnostic
Runs on save_post regardless of which GreenShift blocks compose the page. The image renders from post-level data, not the block tree.
Dynamic content aware
Reads the same ACF, Meta Box, and native fields GreenShift dynamic content uses, available inside the SleekPixel template.
View-time neutral
The image renders once at save time and stores as a static PNG. GreenShift's animations and queries are unaffected.
Use cases
Where GreenShift sites benefit most
CPT-driven sites with query loops
Resources, courses, and case studies use GreenShift query loops for archives. Each detail post gets a card from its custom fields.
Animated landing pages
GreenShift handles motion and layout, SleekPixel handles the share preview pulled from page title and campaign tag.
Editorial blogs
Per-post share cards while GreenShift handles the article layout. Both layers update independently.
The bigger picture
Why GreenShift sites need automated share cards
GreenShift pushes Gutenberg further than most block libraries by adding animations, query loops, and dynamic-content blocks that push the editor toward parity with full builders. Sites built on GreenShift can compose almost any layout without leaving the block editor, which is exactly why the share-preview gap is more visible. The visible page is polished and consistent, the share preview falls back to a global SEO plugin image.
SleekPixel covers that with its own template engine sitting at the post-meta layer. The image renders once at save time, the output is a static PNG, and nothing extra fires when GreenShift's animations or queries run at view time. For CPT-driven sites that lean on GreenShift query loops, every detail URL the loop links to gets a per-post share card automatically.
Updates to either system ship independently because they do not share code paths.
Questions
Common questions about SleekPixel for GreenShift blocks
It runs on save_post, after Gutenberg saves. There is no GreenShift block to add. The image generates server-side from saved post data.
Yes. The query loop iterates over a CPT, and SleekPixel runs on each underlying detail post on save. Every URL the loop links to gets a card.
Yes. Drop the same hex values you use in GreenShift global colors into the SleekPixel template. The card stays visually aligned with the rest of the site.
No. SleekPixel renders an image server-side and writes a meta tag. It does not touch the page body, so GreenShift animations are unaffected.
No. The render runs once at save time and stores a static PNG. Nothing additional fires at view time.
Yes. SleekPixel reads post meta directly and does not depend on which GreenShift tier is active.
Yes. Bulk regenerate walks every post in enabled post types and re-renders share cards with the current template.
No. SleekPixel reads post meta and writes meta tags, neither of which depends on GreenShift internals.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout