As Prisma 1 is feature-frozen and Prisma 2 is going in some directions (no generated SDL schemas, code-first) that might not fit our needs, I've started research on some alternatives.
PROS:
- no separate server needed
- nested mutations (OpenCRUD)
""" | |
Content is the interface for all of our varied types of records. | |
When serving content over the API, only the Content ID is exposed, not | |
the internal IDs from concrete record tables. | |
""" | |
interface Content { | |
id: ID! | |
contentType: ContentType! # e.g. ARTICLE, BUNDLE, IMAGE, etc | |
memberOf: [Content!]! | |
# When records are members of another type of content, they have a |
const _ = require('lodash'); | |
const cuid = require('cuid'); | |
function renderText(renderBranch, renderLeaf) { | |
return (acc, node) => { | |
if (node.doc) { | |
return renderText(renderBranch, renderLeaf)(acc, node, node.doc); | |
} else if (node.content) { | |
return renderBranch(acc, node, node.content); | |
} else if (node.text) { |
amphora-fs
pluginamphora-memoization
pluginamphora-scheduling
pluginamphora-webhooks
pluginThese are considerations that we want to keep in mind as we design systems for styling components and sites. Not all considerations must be met 100%, but the weighting of relative importance will determine what we want the system to focus on.
# site transclusion | |
someField: | |
_label: Some Field | |
_has: | |
- label | |
- | |
fn: description | |
value: Some site-specific field | |
- | |
fn: site-specific |
// sites/selectall/styleguide.css | |
$text-color: #111; | |
$one-column-text-color: #333; | |
$link-color: #111; | |
$sponsored-link-color: #1782a9; | |
$link-border-color: #fcd400; | |
$serif-stack: Georgia, serif; | |
$sans-serif-stack: Arial, sans-serif; |