Skip to content

Instantly share code, notes, and snippets.

@peterbraden
Last active August 29, 2015 14:02
Show Gist options
  • Save peterbraden/790cdb2c74fbeb78fde8 to your computer and use it in GitHub Desktop.
Save peterbraden/790cdb2c74fbeb78fde8 to your computer and use it in GitHub Desktop.
Front End Components

Front End Component Spec

In order to write reusable and modular FE code, we need a system to define modular components. This requires:

A Package Manager

FE components need to be installedto the right location with their dependencies.

Examples:

  • Bower
  • NPM
  • Component package system

An embedding syntax

Currently most component libraries neglect the common case of how to embed html components in other html components - a necessary part of atomic design.

Examples?

  • JS Manipulation (atomify)
  • iframse
  • Web Components

An Asset packaging Pipeline

The nature of Front End code requires that component assets can be minified/pre-processed and added to the page with knowledge of web-perf techniques.

Existing Libraries

component/component

  • Every component must be a separate repo (inflexible) ("error : can not require components below the root")
  • No notion of including components in html

atomify

  • dependency management skewed heavily towards js.
  • doesn't seem easy to include css
  • no html includes
  • minimal documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment