alinea

Generate types (#271)

Up until now the TypeScript definitions that were available for the content
schema were fully inferred using the TypeScript compiler. While this had some
advantages it also came with stability issues and overall did not prove to be
the best solution. TypeScript definitions are now generated from the schema at
build time. The runtime type information should prove useful for the upcoming
GraphQL support as well. Since GrapQL does not come with namespacing we've
introduced a few breaking changes:

• The config file now supports a single schema at the root level, meaning
  the schema is used for every workspace.

• The generated package structure in turn became simpler because the workspace
  distinction is no longer needed:

  // Init pages now available from /pages
  import {initPages} from '@alinea/content/pages'
  
  // The Page type describes every content type of the schema
  // type Page = Page.TypeA | Page.TypeB
  import {Page} from '@alinea/content'
  

Remix run support (#273)

A few changes were necessary to get started with Remix. These changes should
make it easier to work with other frameworks as well.

• An example starter was added
• The local backend connects to the serve instance if it is running. Since
  Remix does not watch file changes in node modules this should make sure
  you're always viewing the latest changes.
• Export pages/backend as CJS (#270)

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)