Skip to content
QuireKit
Core docs
Alpha · evolving API
Build a productView Markdown ↗

Add images, fonts and other capabilities

Find the resource and service integrations a complete product needs beyond editing.

Displaying an image does not mean the application has saved its bytes. A complete product also needs resource storage, fonts and server integrations.

Images: save references and bytes

Typically, upload an image to storage to obtain a stable resource ID, then insert that ID through a content command. A resolver turns the ID into usable bytes or a display URL.

Blob URLs are temporary previews. Persist both resource identity and bytes, and verify the original insertion target when asynchronous uploads finish.

Classic accepts a sink and resolver through media, with host file capabilities through host. Custom workspaces provide View's mediaResolver and matching media services for conversion.

Fonts: refresh layout after loading

Fonts affect width, wrapping and page count. After loading, refresh measurements through the mounted View's public font capabilities. Changing interface CSS alone does not update document pagination.

Classic can use an optional web font library. The application obtains licensed fonts, handles failures and makes matching resources available for export.

Add capabilities as needed

CapabilityIntegrationApplication responsibility
Word and DOCXWord preset, model conversion and file servicesStorage, conversion feedback and media
Review and formsOptional @quirekit/classic-proObtain and configure the relevant package
CollaborationCollaboration extension and selected document protocolBackend, identity, permissions and conflicts
AIAI packages and feature declarationsModel connection, permissions and interface
Ribbon, menus and sidebarsYour interface or Classic pluginsLayout and business actions

Each capability has dependencies and licensing. The example's enabled features are not the entire framework, and creating Editor does not connect accounts, storage or collaboration servers.

Extend your workspace through the reference, or start with Classic configuration and plugins.

QuireKitQuireKit · Core, plugins and Classic docs