Arcade documents

Create arcade information together and keep it current.

Turn observed information into a shared document

Create a new arcade’s basic information and update location, hours, games, prices, facilities, photos, and social links through their editors. Changes can be reviewed in edit history.

The user journey

Reporting an arcade creates a draft before publication. Open the sample’s real basic information, game and GTK editors, make changes and see them reflected in the document after saving. Basic information also shows a before-and-after comparison.

Try the flow

The same feature components used in the service, with sample data. Inputs and verification results stay in this demo.

This draft represents one newly reported arcade. Use the real editors to change its basic information, game versions, quantities, locations, prices and notes, and facilities and visitor information (GTK). Save to update the sample.

Muse Game CenterAn unpublished sample arcade · Changes apply only to this demo document.

Pending publication

#Muse Arcade

Games

Facilities and amenities (GTK)

Indoor FacilitiesGame cards and equipment

Parking

Not Available

Basket

Available

Restroom

Available

Locker

Not Available

How the experience works

Domain-specific editors own validation and saving, then refresh detail and history after success. Game editing uses a base-state identifier to handle conflicts and change history.

Before you use it

Creating and editing require sign-in. Enter verified information and review changes before saving. Some actions depend on account permissions.

Where do I start?

Use “New arcade” on Home to start a document. Edit an existing arcade from “Edit” on its detail page or the relevant section’s edit button.

Open the feature

Back to developer guide

Musecat

All About Arcades