npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

frix

v0.3.16

Published

A CMS based on atomic design principles.

Downloads

45

Readme

frix

npm version Build Status Dependency Status DevDependency Status Coverage Status Code Climate License

A lightweight, modular CMS inspired by Brad Frost's Atomic Design.

Basics

With Frix there is a number of default components:

  • Templates
  • Pages
  • Organisms
  • Molecules
  • Atoms

Templates

Templates consist of organisms but can, like all components, contain normal HTML too. An organism should, as described in Brad Frost's article, be a distinct section of the interface. For example an article.

Molecules, Atoms, etc.

Every Component in Frix can contain components that are one level lower, for Templates, this would be Organisms, for Organsims Molecules and so on. This goes on until the most basic components - in the default case, this is an Atom - which contains only valid HTML.

Pages

Pages are instances of templates using the content from a specified JSON file and resolving all the organisms to valid HTML. This is what the end user sees.

Modules

Modules are a number of functions to be executed whenever a specific type of content is set. At the moment html-content and json-content exist.

  • html-content is called everytime the inner HTML of an element is set.
  • json-content is called for every entry in all content files.

So how does it all work out?

There has to be a key.json to choose a URL with which a template and JSON file are associated like this:

{
  "/index": {
    "template": "index.html"
    "content": "main.json"
  }
}

This serves our index.html with inserted content and resolved organisms - so, valid HTML. The templates get resolved when the Node.js server starts, so theres practically no overhead when serving files during runtime.

Example Usage

Server Code

  const express = require('express');
  const Frix = require('frix');
  let frix = new Frix();
  let app = express();
  
  app.use(frix.requestHandler);

Note that the class Frix takes an optional config as first argument which describes where all dependencies like the key.json, templates, content etc. are stored.

File System

See the example files at /test/files.

Installation

$ npm install frix

API Reference

new Frix([opts])

  • opts Object a config to be merged with the default one:
  {
    key: 'key.json',  
    folders: {  
      organism: 'templates/organisms',
      molecule: 'templates/molecules',
      atom: 'templates/atoms'
    },
    content: 'content',
    pages: 'templates/pages',
    attributes: {
      name: 'name',
      type: 'type',
      content: 'content'
  } 

Returns a new instance of Frix.

frix.addModule(target, module)

  • target String the target module(see Modules)
  • module Function a function to add to the modules Array for the target. The modules array is executed in chronological order.

frix.addModule({ target, module })

  • target String the target module(see Modules)
  • module Function a function to add to the modules Array for the target. The modules array is executed in chronological order.

frix.isDone(onLoad)

  • onLoad Function a function to be executed when Frix has finished resolving all templates and inserting content.

License

MIT