GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - digitalinteraction/alembic: ⚗️ Design toolkit for research projects

BranchesTags
Open more actions menu

Latest commit

 

History

276 Commits
276 Commits

Folders and files

NameName
Last commit message
Last commit date
.github/workflows
.github/workflows
 
 
.nova
.nova
 
 
research
research
 
 
scripts
scripts
 
 
source
source
 
 
.editorconfig
.editorconfig
 
 
.gitignore
.gitignore
 
 
.node-version
.node-version
 
 
.prettierignore
.prettierignore
 
 
CHANGELOG.md
CHANGELOG.md
 
 
README.md
README.md
 
 
USERS.md
USERS.md
 
 
eleventy.config.js
eleventy.config.js
 
 
package-lock.json
package-lock.json
 
 
package.json
package.json
 
 
tsconfig.json
tsconfig.json
 
 

Repository files navigation

⚗️ Alembic

A Design System for Open Lab research projects.

Go to the docs →

Release process

  1. Run the build
  2. Update API docs if needed
  3. Run npm version minor|major|patch
  4. Run npm publish

Uses

This library is used by several Open Lab projects:

  • openlab.ncl.ac.uk - repo
  • datadiaries.uk - repo
  • alembic.openlab.dev - (this repo)
  • Coffee Club
  • Open Lab Hub
  • Nunjucks playground

Design

Goals

  1. Provide a step up (design-wise) for developers
  2. Reduce duplication in effort/code/work
  3. Improve collaboration on projects and focus evolution in the same direction

What

  • A library of components and patterns
  • A documentation site to describe the design system

To explore

  • More accessibility concerns
  • Document the reason behind decisions / solutions
  • Think about adaptability, evolution and collaboration

Coding conventions

TODO: find a better place for these

css variables

  • "axioms" are single words like --measure
  • everything else is type-prefixed like --color-background or --border-thin

imports

module.js is the main entrypoint, sub-modules are self-named files in their own folder e.g. lib/lib.js or layouts/layouts.js.

misc

  • group source by the module, js + css alongside eachother is fine. It makes it easy to work on a module.
  • avoid JavaScript's default exports
  • sub-modules should explicitly export things, avoid export * from '...'-type code
  • pure functions where possible
  • exported code prefixed with _ (an underscore) is internal, should not be used and may change between major releases

This project was set up by puggle

About

⚗️ Design toolkit for research projects

alembic.openlab.dev

Topics

design-systemeleventygithub-pagesopenlab-alembic

Resources

Readme
Activity
Custom properties

Stars

3 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Used by

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.