Review and correct the catalog record for GMK βeta. Your changes become a pull request for maintainer review.
Tell us about the design and its original release. Fields marked with an asterisk are needed to produce a valid catalog record.
The slug stays fixed for an existing keyset.
Separate multiple names with commas.
Checking image…
This image appears first. Use a direct HTTPS image URL, or select a release or item image.
Any image can be the main image, including one assigned to an item.
Other release images
Add direct HTTPS image URLs and their credits. A keyset can have up to 50 images total, including hero and item images.
No additional release images added.
Define a color once, then assign every key group and use it serves.
Add colors when you know them; they are optional.
Record kits, artisans, deskmats, cables, and other products associated with the release.
Minimum order quantity for this kit.
Used only when dated sales history is unavailable.
Choose a main or release image to assign here. Each item has one image; its replaced image returns to the general gallery. The main image can also be assigned to an item.
Alpha legends
Describe primary legends and sublegends, including script and typeface.
Modifier legends
Record text, icons, placement, and any distinct typeface treatment.
Add the vendors first, then prices by item and dated cumulative sales reports. All fields are optional.
Vendor roster
A vendor can be listed even when kit pricing is unknown.
Price matrix
Enter a price only where a vendor sold that item.
Sales history
Record cumulative units sold for each kit on a given date.
No sales reports added.
This name will appear in the private pull request for maintainers.
Submitting creates a branch, commit, and pull request in the KeysetDB dataset for maintainer review. Nothing is published until that pull request is approved. You can add a private maintainer comment in the final confirmation.