Agiled Docs

Descriptions and images help customers understand what they are buying and help your team choose the right catalog item.

Write product copy for the place where it will be reused: finance documents, checkout pages, storefronts, and internal catalog search all need clear names and descriptions.

Short Description

Use Description for a short summary. Keep it useful in compact places such as tables, line items, checkout choices, and document blocks.

Good short descriptions explain the outcome, package scope, or item variant in one or two sentences.

Avoid internal shorthand. A customer should understand the line item even if they never saw your internal package name.

Write for Each Surface

Product information can appear in several places. Write copy that still works when reused on:

checkout links
storefront product cards
invoice and estimate line items
internal catalog search
order review pages

The short description should explain the item quickly. The long description can carry scope, exclusions, and fulfillment details.

Long Description

Use Long description for complete selling or fulfillment context. This can include scope, deliverables, exclusions, timeline, renewal terms, or what the customer should expect after purchase.

Use the long description for promises and boundaries. If a service excludes support, revisions, setup, or rush delivery, write that clearly.

Featured Image

Use Featured image for the main product image URL. This is the image users should expect to represent the item in public or customer-facing views.

Use images that show the actual product, package, deliverable, or service context. Avoid placeholder images on live checkout or storefront pages.

Gallery Images

Use Gallery images JSON when the product needs more than one image. Enter a JSON array of image URLs.

Example:

["/images/product-1.png", "/images/product-2.png"]

Each URL should point to an image customers can load without signing in. Keep the array valid JSON: use quotes around every URL, separate URLs with commas, and do not leave a trailing comma after the last image.

Service Products

For services, use images that show the deliverable, outcome, team, workspace, or service context. If no image is useful, prioritize clear text over a generic stock image.

For package-based services, describe what is included, what is excluded, and what happens after purchase. This reduces support questions after checkout.

Copy Checklist

The name is clear without internal shorthand.
The short description makes sense in a table or line item.
The long description explains scope and expectations.
Image URLs are reachable.
Images match the item being sold.

Image Checks

Open image URLs in a private browser window. Confirm they load without requiring your signed-in session and that they are large enough for public display.

Troubleshooting

If an image does not appear publicly, check the URL, file permissions, and whether the image host blocks hotlinking.

If descriptions look cramped in finance documents, shorten the short description and keep detailed scope in the long description or document terms.

If the wrong image appears on a storefront, confirm whether the storefront is using the featured image or a gallery image. Then update the product and reload the public page in a private browser window.

Product Descriptions and Images