Image Blogger

This document is intended for image bloggers of the KeaFlow platform: the Image Blogger role must be granted by an administrator. If you don't see the "Publishing" or "Products & Sales" menus, the role is not enabled — contact an administrator; accessing the URL directly shows an "Access denied" page, which is a normal protection, not a fault. For basic features (Overview, Assets, System Settings, buying images), see Regular User.

Publish an image

Path: Console → Publishing → Image Community

Publishing takes three steps: fill in → platform review → list.

Step 1: fill in and submit

Click Publish Image at the top right to open the drawer. The form has three sections: Basic / Details / Extended; fields marked ✓ are required, and on submission the form jumps to the first missing field with a hint.

How to fill each field:

Field	Required	How to fill
Image repository	✓	Choose the repository containing your image; options are labeled "Free image / Paid image"
Image	✓	Choose the repository first, then your image and Tag (version label) — two-level selection
Version	✓	Three number boxes auto-assemble into v1.0.0; keep the default for the first release and increment the corresponding part for updates; versions must be unique per image
Linked app	—	No manual input: the system auto-matches an app with the same name; no match does not block publishing
Model link	—	Optional. Once an app is matched, check the model files or whole repositories to attach; models are in place when users get the image
Business category	✓	Click a major category on the left (Vision / Audio / Text), then check sub-tags on the right (multi-select); buyers rely on it to filter images
Cover	✓	jpg / jpeg / png, original ≤ 3MB; auto-cropped to a 262×192 card cover; can be re-uploaded or deleted
Name	✓	Display name on the card, up to 50 characters; describe what environment the image provides
Type	✓	Chip environments the image supports, multi-select: NVIDIA / MetaX / CPU
VRAM (GB)	—	Suggested VRAM to run the image, shown in Recommended parameters on the detail page
CUDA version	—	e.g. 12.4, also shown in recommended parameters so users can check compatibility
Summary	✓	One or two sentences on purpose and scenarios, up to 100 characters
Usage guide	✓	Detailed tutorial in Markdown: edit on the left with live preview on the right, paste screenshots directly, full-screen editing and outline navigation supported
Service ports	—	SSH(22), RDP(3389), Jupyter(8888), VScode(8080) are preset; click Add Port for custom services (name + type + protocol + port 1–65535), at most 10 in total
Environment variables	—	Each entry is KEY=value; separate multiple entries with semicolons (😉

Click Publish Now when done. Two safety designs: republishing the same Tag of an image overwrites the old version (with a confirmation first); accidentally closing the drawer mid-edit also asks for confirmation, so content is not lost.

Step 2: wait for review

After submission the review status moves between Pending review → Approved / Rejected; rejected items can be revised and resubmitted.

Step 3: list

After approval click the inline List button: free images go live directly; paid images require a configured and published SKU first (see SKU Management) — otherwise a dialog explains the reason. Only listed images appear in the website's Image Community. Listed images can be Delisted at any time; edit, delete, and version history are also supported.

Publish a model

Path: Console → Publishing → Model Square

Click Publish Model to open the drawer and fill in: Linked app (required), Linked model file (required; selectable after choosing the app), Model name, Cover (jpg/jpeg/png ≤ 3MB, auto-cropped to 262×192), Model size (number + unit), Base model (required), Model type (required), Introduction (required; Markdown with pasted images supported).

Same Submit for review → List flow as images; list / delist / edit / delete supported.

Model relations

Path: Console → Publishing → Model Relations

Associate models with images: when the client downloads an image, the associated models are placed into the specified directory automatically, so users don't have to find the path themselves.

When adding a relation, fill in four things: app → source repository → whole repository or single file → linked files and download path. Edit and delete are supported.

SKU Management

Path: Console → Products & Sales → SKU Management

An SKU is "a purchasable image version + price + payment methods". A paid image must have a published SKU before it can be listed.

Three steps:

1. Click Configure SKU:
   • Linked image: only your own image versions that are approved and not yet listed can be bound;
   • Price: the amount (CNY);
   • Payment methods: check WeChat / Alipay / voucher (multi-select; voucher must be checked if you want to issue vouchers).
2. Click Save and submit for review and wait for the platform review.
3. After approval click Publish; the SKU takes effect and the image can be listed for sale. Disabling an SKU delists the image accordingly.

Edit and delete are supported (deleting also cleans up platform-side data).

Sales Dashboard

Path: Console → Products & Sales → Sales Dashboard

View by period (All / Last 7 days / Last 30 days / This month / Custom):

• Core metrics: sales revenue, successful orders, paying users, actual payments, voucher redemption amounts, average order value;
• Trend chart: sales trend;
• Breakdowns and rankings: payment-method breakdown, image / SKU sales rankings.

Voucher Management

Path: Console → Products & Sales → Voucher Management

① Generate vouchers

Click Generate vouchers and fill in:

• Batch name (required): vouchers generated together belong to one batch; the batch number is the generation timestamp;

• Scope (choose one):

  Scope	Effect
  General credit	Offsets the face value on any image platform-wide that allows voucher payment
  Specified SKU	Only applies to the linked image version of the selected SKU
  Specified image	Bound to an image with an existing SKU; applies to all its versions

• Face value: what the voucher is worth (≤ ¥999);

• Quantity: 1–100;

• Validity: Permanent / 30 days / 90 days / Custom.

⚠️ Only SKUs that are your own + published + voucher payment enabled support voucher generation; images without an SKU, with a disabled SKU, or without "voucher" checked cannot be selected.

② Distribute vouchers

Three ways to send vouchers to users: specific users (pick people), system auto-match (by registration time), Excel upload (batch by phone number, template downloadable). Success / failure statistics are shown after distribution.

③ Batch details

Inside a batch you can: search codes, void vouchers individually or in batch (unused only), delete expired codes, and view the orders produced by a voucher redemption.

Order Info

Path: Console → Products & Sales → Order Info

Read-only orders generated when others buy your images: buyer, amount, payment method, status, time; filtering and detail view are supported. Distinguish it from "My Orders" (what you bought).

Status quick reference

Object	Status	Notes
Image / Model / SKU review	Pending review → Approved / Rejected	Reviewed by the platform after submission
Listing status	Listed / Not listed	Only listed items are visible and purchasable
Orders	Pending payment / Completed / Closed	Closed automatically after a 10-minute timeout
Vouchers	Undistributed / Unused / Redeemed / Expired	Voided vouchers expire immediately; excess face value is not refunded
Invoices	Applying / Issuing / Issued / Cancelled	Emailed when ready; downloadable repeatedly

FAQ

Can't see a menu? "Publishing" and "Products & Sales" require the Image Blogger role; contact an administrator. Regular accounts always have Overview, Assets, and System Settings. Accessing the URL directly shows an "Access denied" page.