v0.2.4

• The previous release was missing the generated css file in the @alinea/css
  package. Build outputs are now cached in the ci step using wireit but this
  file was not included.

v0.2.3

• The url property of entries can now be controlled using the entryUrl
  function in the type options. Urls are computed during generation and this can
  help to keep them constant if you're using a web framework that does file
  system routing. The available paramters are path, parentPaths and
  locale.
  For example: making sure a doc page always has an url in
  the form of /doc/$path you can specify entryUrl as the following:

  type('Doc', {...fields}).configure({
    entryUrl({path}) {
      return `/doc/${path}`
    }
  })

• The iframe used in the BrowserPreview component now supports top level
  navigation so it becomes possible to link the user to a cms route from within.
  (#246)

• The index of newly created entries will be based on the first child of parent.
  This makes them consistently sortable when published. (#241)

v0.2.2

• Alinea cloud handshake now automatically includes git information when hosted
  on Vercel, to allow for a prefilled project setup

v0.2.1

• Alinea cloud connection now sends the shortKey part of API key during authentication to uniquely identify project

v0.2.0

• The exports of the alinea package are restructed. This is a breaking change
  because the input fields are no longer exposed directly but bundled in the
  "alinea" namespace. A few less used exports were removed and can be
  found in the @alinea packages.

• Client code is shielded from being included server side when compiling with
  the "worker" condition enabled.

• Initial support for selecting external links in the link field. The RichText
  ui component is adjusted to correctly render links. A custom component or tag
  can be passed to render links.

  <RichText a={<a className="custom-link" />} doc={doc} />
  <RichText a={CustomLinkComponent} doc={doc} />

v0.1.19

• Added a new field type for raw json data

v0.1.18

• Minor fix in the handshake procedure between Alinea and Alinea cloud

v0.1.17

• The alinea serve command will try another port if the chosen port is in use
  (#179)
• Avoid duplicate entries after publishing in the development server (#214)
• The generated types for pages depended on a type that would be namespaced
  when using typeNamespace. It did not take the namespace into account, but
  does now.
• The connection with Alinea Cloud should now handle previewing drafts
  correctly.

v0.1.16

• Alinea Cloud can now handle relative urls & authentication is automatically
  redirected.

v0.1.15

• The alinea cli will now forward commands placed after the serve or generate
  commands. It will wait until the alinea package is generated before doing so
  to make sure userland code can always depend on the package being available.
  It also simplifies running the dashboard and development server without
  requiring tools like npm-run-all. In practice, for a next.js website, this
  means one can configure scripts like so:

  {
    "scripts": {
      "dev": "alinea serve -- next dev",
      "build": "alinea generate -- next build"
    }
  }