Beaker Docs
  • Welcome
  • Getting Started with Beaker
  • Joining the Social Network
  • Why use Beaker?
  • Beginner
    • Creating New Hyperdrives
    • Changing a Drive's Title or Thumbnail
    • Using the Editor
    • Detaching the Editor
    • Creating Files and Folders
    • Importing and Exporting Files
    • Sharing Hyperdrives
    • Hosting Hyperdrives
  • Intermediate
    • Your Profile Drive
    • Your Address Book
    • Your System Drive
  • Advanced
    • Webterm
    • Creating Mounts
    • Editing File Metadata
    • Forking Hyperdrives
    • Comparing and Merging Hyperdrives
  • APIs
    • beaker.capabilities
    • beaker.contacts
    • beaker.hyperdrive
    • beaker.markdown
    • beaker.peersockets
    • beaker.shell
    • beaker.terminal
  • Developers
    • Introduction to Hyperdrive
    • Index.json Manifest
    • Content-Type Negotiation
    • Frontends (.ui folder)
    • .Goto Files
  • Help
    • Hole-punchability
Powered by GitBook
On this page
  • Manifest schema
  • .title
  • .description
  • .forkOf
  • .csp

Was this helpful?

  1. Developers

Index.json Manifest

Every hyperdrive has a manifest file at /index.json. This file is used by the browser to store various kinds of metadata, including the title and description of the drive.

Note: the manifest schema is still under development and may change.

An example manifest:

{
  "title": "My Hyper Website",
  "description": "An example hyperdrive"
}

Manifest schema

.title

A string identifying the title of the drive.

.description

A string providing a description of the drive's contents.

.forkOf

A string identifying the URL of a drive which this drive has forked.

.csp

PreviousIntroduction to HyperdriveNextContent-Type Negotiation

Last updated 5 years ago

Was this helpful?

A string specifying the to use in all drive resources.

Content-Security Policy header