v1.2.0

Author: dz4k

.config/mise/config.toml

@@ -0,0 +1,26 @@
+[env]
+BROWSERSLIST="> 0.9% and last 2 versions and not dead"
+
+
+[tools]
+esbuild = "latest"
+deno = "2.4"
+
+
+[tasks]
+build = { depends = ["build:*"] }
+lint = { depends = ["lint:*"] }
+serve = { depends = ["lume -s"] }
+
+"build:www" = { depends = "lume" }
+"build:css" = [
+  "esbuild --bundle --outdir=dist src/missing.css src/missing-prism.css",
+  "esbuild --minify --outdir=dist --entry-names=[name].min dist/missing.css dist/missing-prism.css",
+]
+"build:js" = "rm -rf dist/js && cp -r src/js dist/js"
+
+lume = { hide = true, run = "cd www && echo \"import 'lume/cli.ts'\" | deno run --unstable -A -" }
+
+
+[alias]
+esbuild = "npm:esbuild"

.config/mise/tasks/lint/css.ts

@@ -0,0 +1,33 @@
+#!/usr/bin/env -S deno run -A --no-lock --node-modules-dir=none
+
+import stylelint from 'npm:stylelint';
+import browserCompat from 'npm:stylelint-browser-compat';
+import { resolve } from 'jsr:@std/path/resolve'
+
+const result = await stylelint.lint({
+  cwd: resolve(import.meta.dirname, '../../../..'),
+  files: 'src/**/*.css',
+  formatter: 'string',
+  config: {
+    plugins: [browserCompat],
+    rules: {
+      'plugin/browser-compat': [
+        true,
+        {
+          allow: {
+            features: ['at-rules.supports'],
+            flagged: false,
+            partialImplementation: false,
+            prefix: true,
+          },
+          browserslist: [Deno.env.get("BROWSERSLIST")],
+        },
+      ],
+    },
+  },
+});
+
+if (result.errored) {
+  console.log(result.report);
+  Deno.exit(1);
+}

.github/workflows/npm-publish.yml

@@ -2,10 +2,12 @@
 node_modules
 
 dist
+www/_site
+www/missing-js
 _bin
 
 # Local Netlify folder
 .netlify
 
 # esm.sh :[
-deno.lock
+# deno.lock

.gitignore

@@ -0,0 +1 @@
+Changelogs are kept in `www/releases` and can be found on our website: [/releases](https://missing.style/releases).

.vscode/settings.json

@@ -0,0 +1,142 @@
+
+# Contribute to missing.css
+
+
+## Issues
+
+PRs are not the only form of contributing. Reporting issues is also important
+and helps a lot. And, like PRs, issues that don't match the project's goals or
+standards of quality will not be accepted.
+
+Don't be afraid! We take it upon ourselves to help people contribute. You might
+get follow-up questions or asked for more information when you submit an issue.
+It's not productive to close issues just because we don't like them.
+
+For feature requests, prefer [Discussions][] instead of Issues, unless the
+feature is directly in our [RFP][] or [Concepts][] pages. Otherwise, once a
+feature is agreed upon and there is interest in implementing it, issues can be
+created.
+
+missing.css is developed on a "free to use, pay to demand" basis. Contributors
+are not beholden to users and can work on whatever they like. If you need a
+specific feature or bugfix for your business, consider putting up a bounty.
+(Not recommended: Making an unsolicited donation and then demanding specific
+work. That's not how you buy something).
+
+[RFP]: https://missing.style/rfp/
+[Concepts]: https://missing.style/concepts/
+[Discussions]: https://github.com/bigskysoftware/missing/discussions
+
+
+## Development Environment
+
+The Missing project uses [mise-en-place] to install tools and run tasks.
+
+  * Install your tools:
+    ~~~
+    mise install
+    ~~~
+
+  * Start a development server:
+      ~~~ sh
+      mise run serve
+      ~~~
+
+  * Build all of missing.css (CSS and JS):
+      ~~~ sh
+      mise run build
+      ~~~
+
+  * Build just the CSS:
+      ~~~ sh
+      mise run build:css
+      ~~~
+
+  * Build just the JS:
+      ~~~ sh
+      mise run build:js
+      ~~~
+
+  * Build the website:
+      ~~~ sh
+      mise run build:www
+      ~~~
+
+[mise-en-place]: https://mise.jdx.dev/
+
+
+## Branching
+
+We don't use the `master` or `main` branch. Instead, the `dev` branch
+is the default. This way, the default place to open a pull request is
+the right one.
+
+The `prod` branch will contain the last published version of the code.
+Changes to the website and docs can also be made directly against the
+`prod` branch.
+
+That's it! We don't expect to use feature branches that often, instead working
+directly on `dev` because CSS is hard to merge.
+
+
+## Publishing a release
+
+To publish a new release:
+
+  * Make sure there is a changelog in `www/releases/`:
+
+      ~~~ sh
+      cat >www/releases/4.2.0.md <<EOF
+      ---
+      release: 4.2.0
+      ---
+
+      # Changelog
+
+       - **Breaking:**{.color.warn} Removed everything
+      EOF
+      ~~~
+
+    Some older changelogs have a list of `artifacts` -- this is a leftover
+    from when we used our own distribution instead of npm.
+
+  * Create a git tag matching the regex `^v\d+\.\d+\.\d+` (i.e.: `v1.2.2`,
+    `v1.3.3-special-build-1`, NOT `1.1.2`, `v3`, `v1.2-alpha`). It's important
+    that the git tag has the correct format since we use the regex above in
+    code.
+
+
+## Dev Notes
+
+You can note your thoughts and leave notes for maintainers in the `JOURNAL.md`
+file. The structure is:
+
+  ~~~
+  ## YYYY-MM-DD
+
+  Your notes here
+
+  -- your-github-username
+  ~~~
+
+Leave two empty lines between notes.
+
+
+## Project Structure
+
+  * `src/` -- the CSS source code. This is bundled with esbuild.
+
+  * `www/` -- the project website, built with [Lume]
+      * `docs/` -- documentation. The prefixes on the names (e.g. `40-aria.md`)
+        determine the order of pages.
+      * `demos/` -- demo pages. These should have a `name` specified in the
+        frontmatter. They will be listed in the demo page (`../demos.md`).
+      * `releases/` -- release notes.
+
+  * `dist/` -- build results. This is also where the built website is.
+      * `missing.css` -- unminified dev build
+      * `missing.min.css` -- minified
+      * `missing-prism.css` (& `.min.css`) -- [Prism] theme
+
+[Lume]: https://lume.land
+[Prism]: https://prismjs.com