nelsonpecora

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.

Data Layer

Prisma 2

PROS:

• no separate server needed
• nested mutations (OpenCRUD)

nelsonpecora

"""
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

nelsonpecora

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) {

nelsonpecora

Clay Retrospective

The Good

• allowing maximum flexibility in component design
• standardized editing interfaces across components
• style variations!
• page templates were a good idea (but needed better organizational ux)
• simplified permissions structure was a good idea
  • with friction for certain changes

nelsonpecora

1. page history / pass user to plugins (for specific page updates)
2. break out amphora-fs plugin
3. break out amphora-memoization plugin
4. deprecate lists
   • autocomplete → elasticsearch
   • new page templates api
5. nginx / kong
6. streams!
7. break out amphora-scheduling plugin
8. break out amphora-webhooks plugin

nelsonpecora

What Amphora Does

• saves + retrieves data from db
  • components
    • @published
    • model.js
    • alternate render ext.model.js
    • upgrade.js
    • extensions
  • pages

nelsonpecora

CSS Considerations

These 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.

• maintainability
  • ease of creating new components
  • ease of creating new sites
  • ease of updating components
  • ease of updating sites
• developer / designer happiness

nelsonpecora

Kiln 5.0 Documentation

Narrative

Introduction

• npm installation stuff
• clay-kiln component
• kilnInternals component list
• user experience

nelsonpecora

# site transclusion
someField:
  _label: Some Field
  _has:
    - label
    -
      fn: description
      value: Some site-specific field
    -
      fn: site-specific

nelsonpecora

// sites/di/ad.css

@import 'mixins';
@import 'styleguide';

.ad {
  display: none;
  margin: 0 auto;
  position: relative;
  text-align: center;