SleekPixel for Lego builders: MOC release cards from posts
Every MOC you log in WordPress becomes an Instagram-ready release card with the piece count, the build number, the instructions link, and the cover render baked in. SleekPixel reads your custom project post type so each release looks like part of the same brand line, whether you publish one MOC a month or a fresh tutorial every week.
♾️ Lifetime License available
MOC project to feed-ready release card
The Lego MOC scene runs on Instagram and Rebrickable. The builder with the cleanest release card on launch day gets the resale, the Rebrickable downloads, and the followers. Rebuilding that release card for every modular, mech, or microscale build is what eats your evening. SleekPixel reads each moc_release post and renders the Instagram card with all the metadata already filled in.
Bind the template once: project title to headline, piece count from _piece_count to the mark slot, instructions URL from _instructions_url to the meta line, and the rendered cover image to the cover slot. When you publish a new MOC, the Instagram square, the story, and the OG image for the Rebrickable share all generate in the background. The release card looks like every previous release, because they all come from the same template.
If you tweak the piece count after a parts audit or add a free instructions link a week after release, the image regenerates with the new data on save. Your Instagram, your portfolio, and your Rebrickable listing all stay in sync without you re-exporting anything by hand.
Workflow
How SleekPixel renders your MOC releases
Add a MOC release post type
moc_release CPT or repurpose your existing portfolio post type with fields for piece count, instructions URL, and release number. SleekPixel reads ACF, Meta Box, or raw postmeta.
Bind the template once
Publish and render
Share to channels
Output
Sample MOC release card
A square Instagram card pulled from a modular bakery MOC post showing piece count in the mark slot and the instructions link in the meta line.
Comparison
Manual MOC card edits vs SleekPixel for Lego builder
Hand-built MOC release graphic
- Builder rebuilds the release card in Canva for each MOC even though the layout repeats
- Piece count gets mistyped from BrickLink BOMs into the social graphic each launch
- Instructions link gets pasted manually into Instagram bio and into the card itself
- After a parts audit the old piece count stays on Instagram even though the post was fixed
- Story, feed, and Rebrickable OG image become three separate manual exports per MOC
SleekPixel
-
Reads project title,
_piece_count,_instructions_url, and cover render from each MOC post - Build number renders in the mark slot so the release feels part of a numbered series
- Instructions link appears in the meta line and updates when you upload a new PDF
- Renders Instagram square, story, and Rebrickable OG image from the same post
- PNG regenerates whenever the MOC post is edited so all channels stay in sync
Features
What SleekPixel gives you for Lego builder
MOC post to release card
Each MOC project becomes an Instagram release card with the title, piece count, and instructions link pulled from postmeta. Publish the project in WordPress and the visual is ready before you close the editor.
Piece counts that stay accurate
Update the piece count after a parts audit and the next render carries the new number. Your Instagram feed never shows a stale BOM and the Rebrickable share image matches the actual BOM.
Instructions link in every share
Bind the meta line to your instructions URL so every release card carries a click target. When you swap a paid Rebrickable link for a free one the change propagates to every channel on the next render.
Use cases
Where Lego builders ship SleekPixel cards
Launch day release
Publish the MOC, hit save, and the Instagram square, the story, and the Rebrickable OG image all render before your scheduler picks them up at the launch time.
Tutorial drop
Tutorial posts share the same template but show a tutorial badge and link to the YouTube walkthrough so subscribers find both the build and the how-to from one card.
Convention recap
Convention recap posts use the same template with a convention badge and the event name in the brand line so a year of show recaps looks like a coherent series.
The bigger picture
Why automated release cards matter for MOC builders
MOC releases compete in a crowded Instagram feed where every modular bakery and every mech looks alike at thumbnail size. The builder who lands a consistent, branded release card week after week starts to look like a studio instead of a hobbyist, and the algorithm rewards that consistency. SleekPixel removes the design step from every release so the cadence becomes sustainable.
Piece counts stay accurate because they pull from the same field that drives your Rebrickable listing. Instructions links stay clickable because they pull from the same field that drives your free or paid download page. The release number ticks up automatically from a counter in your project post type so the build feels like part of a numbered series and collectors track the series across years.
When you finally hit your hundredth MOC the release card looks identical to the first one, and search engines find every project page because each has a real OG image at a real URL. The downstream effect is that a new builder discovers your work, sees a hundred consistent releases, and treats you like the established voice in the MOC corner you have actually built.
Questions
Common questions about SleekPixel for Lego builder
Yes. One template binds to fields, not to a single style. The cover image and the title carry the visual variation per build, so a modular bakery and a microscale spaceship can both render cleanly from the same template.
Yes. Edit the piece count field in the MOC post and the next render carries the new number. Existing scheduled posts can re-pull the image on the same URL so the corrected count goes out instead of the original.
Use two meta fields, one for the free link and one for the paid link, and bind the meta slot to whichever is appropriate per template variant. Free and paid release cards render from the same MOC post.
Yes. Each template emits multiple dimensions in one render, so the same MOC post becomes a 1080x1080 Instagram square, a 1080x1920 story, and a 1200x630 Rebrickable share image at the same time.
Yes. Store the release number in a postmeta field and use the SleekPixel auto-increment helper to assign the next number on publish. The mark slot shows the new number on the rendered card.
Yes, indirectly. Drop the BrickLink piece count into the MOC post field and the card pulls from there. SleekPixel does not parse BrickLink XML, but the manual step from XML to field is a single copy-paste.
Yes. The cover slot is bound to the featured image, so swapping the WordPress featured image triggers a re-render with the new cover and the same headline, mark, and brand line. The layout stays intact.
Yes. The brand line is configurable globally, so your Rebrickable handle, your Patreon, or your studio domain renders on every release card. Change it once and every card across the archive picks up the new line on the next render.
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