My goals for c/ss

[chrisdmacrae]

Mission statement

c/ss is zero-config static sites -- for any architecture.

This means it is not create-react-app. It is a project like Neutrino.

Goals

• [ ] Make top-quality web architecture easy (code splitting, service workers, standard config, typescript, webpack, postcss, css-in-js, etc)
  • Autoprefixing
  • Browser targeting
  • Any JS tooling (webpack first, then rollup, then...)
  • Managing image resources (easy-bake minification, sprite generation, etc)
  • Service worker and manifest
  • PWA
  • Hot-reloading dev servers (browsersync)
• [ ] Make starting a new project FUCKING EASY. NO MORE FUCKING SETUP. FUCK. 😰
• [ ] Make testing static websites easier
  • Unit testing your JS
  • Linting your content
  • Linting your code
  • Regression testing on webpages
• [ ] Make this a framework for more specific tools (create-hugo-site, create-jekyll-site)

Targets

• [ ] Jekyll
• [ ] Hugo
• [ ] Eleventy
• [ ] Gatsby
• [ ] Vuepress

Each target could be a separate project w/ domain-specific knowledge

Features

• [ ] Abstract the build config for a website
• [ ] Semantic versioning
  • [ ] Of the tool
  • [ ] Of the project config underneath the tool
• [ ] Make discovery easy (enforce a naming convention on public templates)

Usability

• [ ] Make it extremely easy to create your own templates
  • [ ] Eat an existing projects config and abstract it to a public repo
  • [ ] Publish configs to public github repositories
• [ ] Make it extremely easy to understand the CLI (see gatsby)
• [ ] Make updates extremely easy to get (see npm)

Error Handling

• [ ] Make errors human-readable
• [ ] Catch and log all errors

[chrisdmacrae]

The Core Tools & Setup

• The core toolset offers NPM packages for making your own build templates easy
  • Webpack toolset (similar to gatsby)
  • PostCSS helpers exposed (not to projects)
  • A dev server (browsersync underneath) with presets
  • Jest presets for easily adding testing to your project
  • Unit testing your JS
  • Regression testing your frontend
  • A basic reference build template
  • A basic reference website template

The Core API Workflow

• c/ss looks to the project for deps & config overrides
• the source folder from the project is used and allocated to memory/temp
• the source folder is then processed by the build template into memory/temp
• the memory/temp files are then processed by the website (SSG) template and written to memory/temp
• the temporary memory store is then written to the dist directory
• the operation information is cached to speed up future tasks