內容簡介
Burnpedia Image Maker 是一款專為 WordPress 設計的 Pinterest 圖片設計外掛，提供 130 種模板，讓使用者能夠快速創建社交媒體圖片，無需離開控制台，提升內容分享的效率。
【主要功能】
• 130 種設計模板可供選擇
• 直接在 WordPress 控制台內設計圖片
• 支援多種顏色調色板和自訂品牌顏色
• 可使用文章中的圖片或媒體庫中的圖片
• 自由調整文字位置、大小和樣式
• 無需註冊帳號即可設計和下載圖片
外掛標籤
開發者團隊
② 後台搜尋「Burnpedia Image Maker – Social Image Designer with 130 Templates」→ 直接安裝（推薦）
原文外掛簡介
Burnpedia Image Maker is not affiliated with, endorsed by or sponsored by
Pinterest, Inc. Pinterest is their trademark, named here only to say what the
images are for and where the one optional feature posts them.
Every post you publish deserves a Pin, and making one is usually a trip to another
website: export the photo, upload it somewhere, fight a template, download it,
come back. This plugin puts the whole thing inside WordPress.
It is a Pinterest pin designer that lives in your dashboard – a pin maker
that already knows the post you are writing about, so there is no upload step and
no second tab. It is made by Burnpedia.
Open a post and the canvas is already composed — the featured image in place,
the post title as the headline, a sensible template, a 2:3 Pinterest canvas, the
permalink attached. Change what you want and download it. Most Pins take under a
minute.
Do I need an account? No — not to design, not to download, not to save to your
Media Library. All of that runs in your browser, on your own site, with no limit,
no watermark and no sign-up. An account is needed for two optional things:
posting the finished Pin to Pinterest for you, and AI help that writes a Pin’s
words or makes its background photo. Both use a free account at
burnpedia.app; AI help also uses Burnpedia points. Both
are described plainly under External services below.
What you get
130 templates across two families — text laid over a full-bleed photo, and
layouts that hold the photo inside a designed frame (magazine cover, side split,
ticket stub, arch pair, window pane, and many more).
40 colour palettes, or your own brand colours.
Your photos — the post’s featured image, any image already in the post, your
Media Library, or a file from your computer. Crop with 1–4× zoom and pan.
Text you can move — drag the headline anywhere on the canvas, resize it,
restyle it. Seven type choices, colour, size and a legibility scrim.
Extra elements — up to 12 text blocks, badges and stickers.
A brand kit — your logo, your colours, your font, saved for this site, so
every Pin from this blog looks like this blog and every author here gets it.
Start it in one click from your theme’s own colours, and carry it to the other
sites you run if you have a Burnpedia account.
Any size from 400 to 3000 pixels, exported as PNG, JPG or WebP, with a
warning when a shape is a poor fit for Pinterest.
A set of Pins for one post – draw up to six at once, each on a different
template and using a different one of the post’s photos, then send them all
with one press. They go out one a day, which is the pace Pinterest rewards.
Optional AI help – have the Pin title and description written for you, or
a background photo generated from a sentence. The price in Burnpedia points and
your balance are shown before you press, a failed attempt costs nothing, and
the photo is saved to your Media Library. An administrator can also let
editors and authors use it, with a daily limit per person.
Seasonal and niche template packs – holiday packs appear about two months
before the day (Halloween, Thanksgiving, Christmas, New Year, Valentine’s Day,
Easter, summer, back to school), alongside packs for recipes, product
roundups and quotes.
Pins for your older posts – a list of every published post that has no
Pin yet, with a Design a Pin button on each. Tick the ones you want and they
go out one a day, never on a day that is already full, so an archive of
hundreds of posts becomes weeks of steady pinning instead of a burst.
A Pin drafted when you publish – with a brand kit saved, every new post
gets a Pin drawn in your brand and template, waiting in the editor for you to
approve, edit or discard. Nothing is posted until you press approve.
How your Pins did – views, saves, close-ups and visits to your site for
the Pins sent from this site, and which of your templates people save most.
New Pins start with small numbers, and the screen says so.
A getting-started checklist – design, download, and, if you want Pins
posted for you, connect and send. The last two steps are marked optional.
Undo and redo, and an autosaved draft so a closed tab does not lose work.
Every pin template is a real design, not a filter: the same layouts a designer
would build for vertical Pinterest graphics, with your photograph and your
headline dropped into them.
What you can do with a finished Pin
Download it — full resolution, no watermark, ever.
Save it to your Media Library.
Set it as the post’s featured image.
Insert it into the post (it asks first, and it only ever appends).
Send it to Pinterest — optional, and the only part that needs an account.
Works on a phone
wp-admin gets used on phones, so the editor does too: the canvas takes a finger,
the controls stack, and nothing is smaller than a thumb.
Nothing is locked
There is no pro version of the editor, no watermark and no trial, and nothing in
the editor stops working without an account. Two optional extras are services
Burnpedia runs, and they are the only things that can cost anything: posting to
Pinterest, which is metered by how many Pins a day you post, and AI help, which
uses Burnpedia points and shows the price before you press. Everything else here
is simply free.
External services
This plugin is a client for Burnpedia (https://burnpedia.app), a Pinterest
scheduling service we operate. It is used for one optional feature: sending a
finished Pin to Pinterest.
Nothing is sent anywhere until an administrator either saves a Burnpedia API
key or presses “Connect this site”. Until one of those two things happens, the
plugin makes no outbound request of any kind — except a bug report you choose to
send, and the plugin list the More plugins screen asks WordPress.org for when
you open it (both described at the end of this section). There is no telemetry, no
analytics, no phone-home and no third-party asset — every script, style and font
in this plugin is served from your own site.
Pressing Connect this site makes exactly one kind of request, and it carries
nothing about you or your site:
POST https://burnpedia.app/api/site-connect/claim — after you press
Connect this site, while you are approving the connection on burnpedia.app.
Sends: two random strings this site generated for that one connection, and the
plugin’s name and version. Receives: a short status word – whether you have
approved it yet – and, once you have, your new API key, which the plugin saves
for you. Nothing else comes back. Your site’s address and name are shown on the
approval page because they travel in the link your browser opens; they are never
sent by the plugin itself. If you approve nothing, no key is ever created and
the request stops on its own after fifteen minutes.
When a key is saved, these requests are made, and only these:
GET https://burnpedia.app/api/v1/me — when an administrator opens the Send
panel or the Connection screen, and when a key is saved; and, only if an
administrator has switched on AI help for the team, when an editor or author
opens the AI panel (so the price is shown before they press anything). Sends:
your API key. Receives: your plan, how many Pins you have posted today, your
AI points balance and prices, and whether a Pinterest account is connected.
GET https://burnpedia.app/api/v1/boards — when an administrator opens the
Send panel, to list your Pinterest boards. Sends: your API key. Receives: board
names and ids.
POST https://burnpedia.app/api/v1/pins — only when you press Send to
Pinterest. Sends: your API key, the public URL of the Pin image you just
saved to your Media Library, the Pin title, the post’s permalink, and the board
you chose (or a board name taken from the post title). Pinterest then downloads
the image from your site at that URL.
GET https://burnpedia.app/api/v1/analytics/site — only when an administrator
opens How your Pins did in the editor, at most once every fifteen minutes.
Sends: your API key and this site’s address. Receives: the impressions, saves
and clicks Burnpedia has already recorded for Pins that link to this site. It
does not ask Pinterest anything.
GET https://burnpedia.app/api/v1/brand-kit — only when an administrator
presses Use my account’s kit here in the Brand kit panel. Sends: your API
key. Receives: the colours, font and logo address saved on your Burnpedia
account, so the same brand can be used on more than one site.
PUT https://burnpedia.app/api/v1/brand-kit — only when an administrator
presses Save to my Burnpedia account. Sends: your API key and this site’s
brand kit – three colour values, a font name, and your logo’s address.
POST https://burnpedia.app/api/v1/copy — only when an administrator presses
Write it for me in the optional AI panel. Sends: your API key, the Pin
title you have typed, and the post’s permalink. Receives: a suggested title,
description and keywords, and how much AI credit that used.
POST https://burnpedia.app/api/v1/images — only when an administrator presses
Generate the photo in the optional AI panel. Sends: your API key and the
description of the photo you typed. Receives: the address of the generated
image, and how much AI credit that used.
GET https://burnpedia.app/api/uploads/... — immediately after the request
above, to download that image so it can be saved into your own Media Library.
Sends: your API key. Receives: the image file. Only an address that
burnpedia.app itself just returned is ever fetched.
The AI panel is optional and appears only when a key is saved. Designing,
editing, downloading and saving a Pin to your Media Library never make any
request at all — those work with no account, and nothing in this plugin charges
for them.
Your brand kit is stored on this site and works with no account at all. Those
two requests happen only when you press one of those two buttons, and never on
their own.
Every request also carries the plugin’s name and version, so we can tell which
version of the plugin a request came from.
Burnpedia’s terms: https://burnpedia.app/terms
Burnpedia’s privacy policy: https://burnpedia.app/privacy
Pinterest itself is never contacted by this plugin. You connect Pinterest once,
on Burnpedia, through Pinterest’s own login screen; this plugin never sees or
stores a Pinterest credential.
Burnpedia is our own service and is not affiliated with Pinterest, Inc.
The install count (optional, off by default). WordPress.org does not tell
plugin authors how many sites are running their plugin — for this plugin it
publishes no figure at all. If you switch this on under Image Maker → Connection, this site
sends a short report:
POST https://burnpedia.app/api/plugin-insights — once when you switch it on,
then at most once a week while an administrator is using wp-admin, once if you
deactivate the plugin, and once if you delete it. Sends exactly nine things: a
random ID generated on this site, which plugin and which version, which of
those four events it is, your WordPress version, your PHP version, your site
language, whether this is a multisite network, and whether an API key is saved
(true or false — never the key). Receives: nothing your site uses.
Your website address is not in that report and is never sent, so we cannot
tell which website you are. The random ID is made up on your server and means
nothing outside it. Switch the setting off and the ID is deleted, so counting
stops and a later change of mind cannot be joined to it. It is off until you
choose it, no feature depends on it, and nothing about any reader or any
logged-in user is in it.
Report a bug (only when you send one). The Image Maker → Report a bug screen
sends what you type straight to the people who build this plugin. Nothing is sent
until you press Send report, and the screen lists what goes with it first:
POST https://burnpedia.app/api/plugin-bug-report — sends your description,
the email address you leave for a reply (optional — leave it empty and we
cannot answer), this plugin’s name and version, your WordPress version, PHP
version, theme name and version, site language, whether this is a multisite
network, and whether an API key is saved (true or false — never the key).
Your site’s address is sent only if you leave “Include this site’s address”
ticked. Receives: a reference number for your report. We use a report only
to answer you and to fix the problem. No API key or account is needed.
More plugins (only when you open it). The Image Maker → More plugins screen
lists our other free plugins. When an administrator opens it, WordPress asks
WordPress.org (https://api.wordpress.org/plugins/info/) for that list through
its own plugins_api() — the same request WordPress makes on Plugins → Add
New — and keeps the answer for twelve hours. Installing one uses WordPress’s
own installer and downloads it from WordPress.org. Nothing is installed or
activated unless you press its button, and nothing is sent to Burnpedia.
