Merge pull request 'theme: don't plainify post summaries' (#31) from fix-smart-quotes into main

Reviewed-on: lix-project/lix-website#31
Reviewed-by: jade <jade@noreply.git.lix.systems>

config.yaml

@@ -46,16 +46,20 @@ menus:
       url: "/faq"
       weight: 2
 
-        #- name: "Docs"
-        #  url: "/#"
-        #  weight: 4
-
     - name: "Resources"
       url: "/resources"
-      weight: 5
+      weight: 3
 
     - name: "Community"
       url: "/community"
+      weight: 4
+
+    - name: News
+      url: "/blog"
+      weight: 5
+
+    - name: "Docs"
+      url: "https://docs.lix.systems/manual/lix/stable"
       weight: 6
 
     - name: "Code"
@@ -67,7 +71,7 @@ menus:
       weight: 8
 
   buttons:
-    - name: "Install Lix (beta)"
+    - name: "Install Lix"
       url: "/install"
       weight: 5
       pre: "btn btn-primary text-light"

content/about.md

@@ -11,11 +11,11 @@ packages that can be used for anything from **putting configuration files into p
 **declaratively managing an entire system**. 
 
 That means that, with a few well-written Nix expressions, one 
-can easily configure a system into a known state --- and the packages that are created this
+can easily configure a system into a known state -- and the packages that are created this
 way are guaranteed to run _exactly the same way_ on any system of the same architecture.
 
 As a fork of CppNix, Lix is designed to be fully compatible with the original CppNix 
-implementation --- but also designed to allow evolution of the language and tooling, so
+implementation -- but also designed to allow evolution of the language and tooling, so
 its developers can improve usability and ergonomics without sacrificing correctness.
 
 ### Why use Nix?
@@ -31,21 +31,21 @@ to clusters of critical infrastructure. With this in mind, the Lix team has been
 provide a collection of necessary improvements over CppNix:
 
 - **Built for a community, not for a corporation.**  
-  Lix is built by a team of open-source volunteers --- and exists to provide a alternative to the
+  Lix is built by a team of open-source volunteers -- and exists to provide an alternative to the
   commercial interests that have long plagued both upstream CppNix and corporate-authored forks.
   We're proud to stand by our open [conflict of interest statements](/team#conflict-of-interest-statements),
   and proud to listen to community voices on issues of sponsorship, direction, and moderation.
 
 - **A safe community for developers of all backgrounds.**  
-  Lix is developed by a diverse group of users --- and accordingly is committed to providing a
+  Lix is developed by a diverse group of users -- and accordingly is committed to providing a
   space that's safe for users and developers typically underrepresented in technical projects.
   We take moderation seriously, and are committed to preventing bad actors from driving out 
   marginalized groups.
 
 - **A correct implementation of the Nix language.**  
-  Recent versions of the CppNix project have introduced significant regressions --- so much so
+  Recent versions of the CppNix project have introduced significant regressions -- so much so
   that the upstream [Nixpkgs](https://github.com/nixos/nixpkgs) team has opted to remain several
-  versions behind. Lix is forked from the last truly-stable version of CppNix --- but has both
+  versions behind. Lix is forked from the last truly-stable version of CppNix -- but has both
   introduced new features and backported a number of features from newer versions without
   sacrificing correctness.
 
@@ -53,12 +53,12 @@ provide a collection of necessary improvements over CppNix:
   Lix is designed for evolution of its codebase. Lix already uses the more modern 
   [meson build system](https://mesonbuild.com/), which improves developer usability and decreases build times. 
   Plans include a gradual, piecewise introduction of the memory-safe [Rust](https://www.rust-lang.org/)
-  programming language --- to both supplement and replace sections of the current C++ codebase. 
+  programming language -- to both supplement and replace sections of the current C++ codebase. 
 
 - **A language with room to grow.**  
-  Unlike upstream Nix, Lix intends to be an evolving language --- a robust language versioning
+  Unlike upstream Nix, Lix intends to be an evolving language -- a robust language versioning
   system will allow the language to grow and evolve without sacrificing backwards-compatibility or correctness.
-  And room to grow means room for **usability and ergonomics improvements** --- both in the langauge and in
+  And room to grow means room for **usability and ergonomics improvements** -- both in the language and in
   tooling.
   
 

content/add-to-config.md

@@ -1,13 +1,58 @@
 ---
 title:  "Switching To Lix"
-description: "or: how to make your existing configruation Delicious"
+description: "or: how to make your existing configuration Delicious"
 date: "2024-04-27"
 author: "Lix Team"
 ---
 
-If you have an existing configuration on **NixOS** or **nix-darwin**, the easiest way
+If you have an existing configuration on **NixOS** or **nix-darwin**, there are
-to switch to Lix is currently by using our provided _NixOS module_. Fortunately, this
+a couple of ways to switch to Lix, all of which are relatively easy.
-usually means adding only a couple of lines to your configuration.
+
+- Using Lix from nixpkgs:
+  - Potentially slightly older version of Lix
+  - Working binary caching
+  - Programs like nix-eval-jobs and colmena still use the default version of
+    Nix (may be unacceptable depending on your use case)
+- Using the Lix NixOS module:
+  - Fresh version of Lix right out of the freezer
+  - You will be compiling Lix yourself, for now at least
+  - Programs like nix-eval-jobs and colmena have the version of Nix they use
+    overridden by an overlay such that most of the system uses Lix.
+
+# Using Lix from nixpkgs
+
+This approach has some caveats: since it is not using an overlay, it does not
+set the version of Nix depended on by other tools like colmena or
+nix-eval-jobs. Consequently, those tools will be using whichever version of
+CppNix is default in nixpkgs, likely leading to an inconsistent experience. It
+is, however, easy, and it does not take the few minutes to compile Lix from
+source.
+
+Add the following code to your NixOS configuration:
+
+```nix
+{ pkgs, ... }:
+{
+  nix.package = pkgs.lix;
+}
+```
+
+That's it, you're done.
+
+You can verify that it works by running the following command:
+
+```sh
+$ nix --version
+nix (Lix, like Nix) 2.90.0
+```
+
+# Using the Lix NixOS module
+
+The Lix NixOS module is the way to get the most consistent experience using
+Lix, and to have a system that has Lix as the default Nix implementation
+wherever possible by using an overlay to replace `pkgs.nix`. It will result in
+building Lix from source, which takes a few minutes on every update, which is a
+perfect time to get up, get some water, and stretch for a bit.
 
 ## Flake-based Configurations
 
@@ -22,13 +67,8 @@ Adding Lix to a flake-based configuration is relatively simple. First, add the L
     # Note that this assumes you have a flake-input called nixpkgs,
     # which is often the case. If you've named it something else,
     # you'll need to change the `nixpkgs` below.
-    lix = {
-      url = "git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.1";
-      flake = false;
-    };
     lix-module = {
-      url = "git+https://git.lix.systems/lix-project/nixos-module";
+      url = "https://git.lix.systems/lix-project/nixos-module/archive/2.90.0.tar.gz";
-      inputs.lix.follows = "lix";
       inputs.nixpkgs.follows = "nixpkgs";
     };
 
@@ -78,12 +118,17 @@ Add the Lix _NixOS Module_ to your configuration:
 }
 ```
 
+<!--
+FIXME: the binary cache doesn't do much good given that everyone is running a
+different nixpkgs than Lix is actually cached with during the release process.
+We need a hydra to be able to fix that.
+
 Finally, if you'd prefer not to build Lix yourself, you can add our binary cache.
 Add the following to any NixOS module in your configuration (e.g. `configuration.nix`):
 
 ```nix
 {
-  nix.settings.extra-substituters = [
+  nix.settings.substituters = [
     "https://cache.lix.systems"
   ];
 
@@ -93,12 +138,14 @@ Add the following to any NixOS module in your configuration (e.g. `configuration
 }
 ```
 
+-->
+
 Rebuild and switch into your new system (either using `nixos-rebuild` or `darwin-rebuild`).
 You should now be using Lix! You can verify this by asking the `nix` command to report its version:
 
 ```sh
 $ nix --version
-nix (Lix, like Nix) 2.90.0-beta.0
+nix (Lix, like Nix) 2.90.0
 ```
 
 As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
@@ -113,12 +160,6 @@ Lix release tarball, and then add it to your `configuration.nix`.
 Open your `/etc/nixos/configuration.nix` in the editor of your choice. Find the `imports`
 section, and add the line provided in the configuration
 
-<mark>
-<b>This section is currently pending on a quick update.</b>
-</mark>
-<br/>
-<br/>
-
 ```nix
 { config, lib, pkgs, ... }:
 {
@@ -126,20 +167,30 @@ section, and add the line provided in the configuration
     [ # Include the results of the hardware scan.
       ./hardware-configuration.nix
 
-      # This is the core line -- it pulls down the Lix module and
+      # This includes the Lix NixOS module in your configuration along with the
-      # includes it in your configuration. It looks much nicer with a let
+      # matching version of Lix itself.
-      # binding -- but for clarity, we'll leave that as an exercise for the 
-      # reader. :)
       #
-      # Note that the tag (e.g. v2.90) in the URL here is what determines
+      # The sha256 hashes were obtained with the following command in Lix (n.b.
+      # this relies on --unpack, which is only in Lix and CppNix > 2.18):
+      # nix store prefetch-file --name source --unpack https://git.lix.systems/lix-project/lix/archive/2.90.0.tar.gz
+      #
+      # Note that the tag (e.g. 2.90.0) in the URL here is what determines
       # which version of Lix you'll wind up with.
-      (import 
+      (let
-        (
+        module = fetchTarball {
-          (fetchTarball { url = "https://git.lix.systems/lix-project/nixos-module/archive/main.tar.gz"; }) + "/module.nix"
+          name = "source";
-        ) 
+          url = "https://git.lix.systems/lix-project/nixos-module/archive/2.90.0.tar.gz";
-        { 
+          sha256 = "sha256-yEO2cGNgzm9x/XxiDQI+WckSWnZX63R8aJLBRSXtYNE=";
-          lix = fetchTarball { url = "https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz"; }; 
+        };
-        }
+        lixSrc = fetchTarball {
+          name = "source";
+          url = "https://git.lix.systems/lix-project/lix/archive/2.90.0.tar.gz";
+          sha256 = "sha256-f8k+BezKdJfmE+k7zgBJiohtS3VkkriycdXYsKOm3sc=";
+        };
+        # This is the core of the code you need; it is an exercise to the
+        # reader to write the sources in a nicer way, or by using npins or
+        # similar pinning tools.
+        in import "${module}/module.nix" { lix = lixSrc; }
       )
     ];
 
@@ -147,12 +198,15 @@ section, and add the line provided in the configuration
 }
 ```
 
+<!--
+FIXME: as above, doesn't work, we should not recommend it.
+
 Finally, if you'd prefer not to build Lix yourself, you can add our binary cache.
 Add the following to any NixOS module in your configuration (e.g. `configuration.nix`):
 
 ```nix
 {
-  nix.settings.extra-substituters = [
+  nix.settings.substituters = [
     "https://cache.lix.systems"
   ];
 
@@ -161,13 +215,14 @@ Add the following to any NixOS module in your configuration (e.g. `configuration
   ];
 }
 ```
+-->
 
 Rebuild and switch into your new system (either using `nixos-rebuild` or `darwin-rebuild`).
 You should now be using Lix! You can verify this by asking the `nix` command to report its version:
 
 ```sh
 $ nix --version
-nix (Lix, like Nix) 2.90.0-beta.0
+nix (Lix, like Nix) 2.90.0
 ```
 
 As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
@@ -176,7 +231,7 @@ great time to check out some of the [community's resources on Nix](/resources).
 ## Having Trouble?
 
 **One quick thing to check:** have you set `nix.package` anywhere in your configuration?
-If so, your configuration option will override the Lix module. You'll want to remove it, first --- 
+If so, your configuration option will override the Lix module. You'll want to remove it, first --
 or, if you're feeling savvy, point it to the provided Lix package.
 
 **Otherwise:** If you're having difficulty installing Lix, don't panic! Hop on over to our

content/blog/2024-07-10-lix-2.90-release.md

@@ -0,0 +1,228 @@
++++
+title = "Announcing Lix 2.90 \"Vanilla Ice Cream\""
+author = "Lix Team"
++++
+
+We at the Lix team are proud to announce our first release, version 2.90
+"Vanilla Ice Cream". This release focuses on foundations and reliability, but
+nevertheless contains several small but exciting user-facing features that are
+exclusive to Lix.
+
+Lix is a Nix implementation focused on reliability, predictability,
+friendliness, developed by a community of people from
+around the world. We have long term plans to incrementally evolve Nix to work
+in more places, to make it more reliable and secure, and to update
+the language and semantics to correct past mistakes and reduce
+errors, all the while providing an amazing tooling experience.
+
+Lix forks from CppNix version 2.18, which is the default version of Nix in
+NixOS 23.11 and 24.05. It includes backports for most bug fixes in later versions of
+CppNix, as well as various reliability improvements, and many improvements to user
+experience. Our goal with Lix 2.90 is to create a better Nix 2.18: faster, more
+user friendly, with fewer bugs, and fully compatible with previously-valid
+Nix code including flakes.
+
+Some highlights of this release include:
+
+- `:doc` in `nix repl` now works on lambdas, in addition to built-in functions
+  as before, thanks to [Lunaphied] and [jade]:
+
+  ```
+  dev/nixpkgs » nix repl -f .
+  Lix 2.90.0-lixpre20240520-992c63f
+  Type :? for help.
+  Loading installable ''...
+  Added 21430 variables.
+  nix-repl> :doc lib.forEach
+  Synopsis: func = xs: f: ...
+
+        |    Apply the function to each element in the list.
+        |    Same as `map`, but arguments flipped.
+        |
+        | Inputs
+        |
+        |    `xs`
+        |
+        |    : 1\. Function argument
+        |
+        |    `f`
+        |
+        |    : 2\. Function argument
+        |
+        | Type
+        |
+        |    ``
+        |    forEach :: [a] -> (a -> b) -> [b]
+        |    ``
+        |
+        | Examples
+        |    :::{.example}
+
+      # lib.lists.forEach usage example
+
+        |    ``nix
+        |    forEach [ 1 2 ] (x:
+        |      toString x
+        |    )
+        |    => [ "1" "2" ]
+        |    ``
+        |
+        |    :::
+
+  /home/jade/dev/nixpkgs/lib/lists.nix:77
+
+  ```
+- `nix repl` supports creating shortcuts using the [`repl-overlays`][repl-overlays]
+  setting, thanks to [wiggles]. For example, one can create a shortcut to
+  `legacyPackages.${currentSystem}` with the following repl overlay, configured
+  as a file in the `repl-overlays` setting in `~/.config/nix/nix.conf`:
+
+  ```nix
+  { currentSystem, ...}: final: prev: let
+    optionalAttrs = predicate: attrs:
+      if predicate
+      then attrs
+      else {};
+  in
+    optionalAttrs (prev ? legacyPackages && prev.legacyPackages ? ${currentSystem})
+    {
+      pkgs = prev.legacyPackages.${currentSystem};
+    }
+  ```
+
+  Then:
+
+  ```
+  ~ » nix repl nixpkgs
+  Lix 2.90.0-lixpre20240520-992c63f
+  Type :? for help.
+  Loading installable 'flake:nixpkgs#'...
+  Added 5 variables.
+  Loading 'repl-overlays'...
+  Added 6 variables.
+  nix-repl> pkgs.hello
+  «derivation /nix/store/w0hjp1fnvyf1z30s29fj4im8c7bxqrql-hello-2.12.1.drv»
+  ```
+- Evaluation is 5-20% faster than 2.18, depending on which benchmark is in use,
+  thanks to [eldritch horrors].
+- Various user experience issues have been fixed. For example:
+  - Error reporting has been fixed to be more accurate in several cases thanks
+    to [wiggles], and errors give more details to diagnose them.
+
+    For instance, type errors now give the actual value that caused the error.
+  - `nix flake lock --update-input nixpkgs` is now the much more reasonable
+    `nix flake update nixpkgs`.
+  - `nix build -E` is now an alias for `nix build --expr`, mirroring `nix-build
+    -E`.
+  - Several very silly `--debugger` bugs that one runs into in normal usage
+    have been fixed thanks to [wiggles], so the debugger actually works properly
+    without a mental index of all the bugs in it.
+  - The Lix evaluation cache no longer caches failures, so "cached failure" is an
+    error of the past.
+  - The REPL value printer now intelligently chooses whether to print on one
+    line or multiple lines, rather than putting everything on one very long
+    line.
+  - Various failures that were silent in the past are no longer silent:
+    - The Lix daemon warns when it rejects a setting from a client that requires
+      being a trusted user, instead of silently ignoring it.
+    - Remote builds failing to connect to a builder now print the error.
+    - Crashing the daemon now indicates that is what probably happened.
+    - Lix now generally crashes much harder in the case of bugs, such that bugs
+      are easier to find and fix.
+  - Various errors have been made more specific, like "path is invalid".
+- Several hauntings have been exorcised from the codebase:
+  - Flake input overrides like `foo.inputs.bar.inputs.nixpkgs` now work as
+    documented rather than being ignored.
+  - Store path names starting with `.` are now permitted, fixing some home-manager
+    issues.
+  - A crash when running patched kernels with non-default schedulers has been
+    fixed.
+  - Breakage inside the sandbox when running on systems with unprivileged user
+    namespaces disabled has been fixed.
+  - Various format string crashes have been fixed.
+  - `nix doctor` now has correct output of client trustedness.
+
+[wiggles]: https://github.com/9999years
+[eldritch horrors]: https://git.lix.systems/pennae
+[Lunaphied]: https://github.com/lunaphied
+[jade]: https://jade.fyi
+
+[repl-overlays]: https://docs.lix.systems/manual/lix/2.90/command-ref/conf-file.html#conf-repl-overlays
+
+A lot of internal stability work and development process work has gone into
+this release. For instance:
+- Lix builds exclusively with the Meson build system. The historical CppNix
+  Make-based build system has been removed altogether. This improves
+  compile times as well as various aspects of the developer experience: the `clangd`
+  language server just works with no configuration now, for instance.
+- Lix has the beginnings of the infrastructure to do linting of its C++ code and work on
+  modernization with automated tools.
+- Lix enforces various aspects of [its
+  styleguide][styleguide] with `pre-commit` hooks.
+- A lot of onboarding and project planning information has been written down in
+  the [Wiki]. In general we strive to be transparent with our plans and
+  priorities, and to communicate them clearly.
+- We have completed a release automation project, which should let us release more
+  frequently given that our `main` is more or less releaseable on any given day.
+- We have built out a lot of infrastructure which we own end-to-end, allowing
+  us to quickly improve on pain points in the project ourselves.
+  - We have [Single Sign-On](https://identity.lix.systems) permitting us to
+    easily deploy more services that cleanly integrate together.
+  - We use [Gerrit](https://gerrit.lix.systems) for reviews, which allows us to
+    focus on providing prompt and high quality patch reviews by making it easy
+    to review changes piece by piece, with CI testing of every commit.
+
+    Gerrit is one of our secret superpowers in shipping correct code, since it,
+    by its structure, enforces good commit history, reviewable code, and
+    incremental changes.
+  - We use [Forgejo](https://git.lix.systems) for code hosting and issue
+    tracking, which we have customised to integrate natively with Gerrit and
+    to work natively with Nix flakes for locking tarballs.
+  - We have a [Wiki] with design documents, styleguide, and other project
+    organisational information.
+
+[Wiki]: https://wiki.lix.systems
+
+[styleguide]: https://wiki.lix.systems/books/lix-contributors/chapter/style-guide
+
+For a more comprehensive list of the changes in this release, see
+[the release notes][release-notes].
+
+[release-notes]: https://docs.lix.systems/manual/lix/2.90/release-notes/rl-2.90.html
+
+The Lix team as well as several dozen beta testers have been running a
+development release of Lix 2.90 in production every day for a couple of months,
+and we do not expect any significant regressions compared to Nix 2.18. However,
+if you find a bug or suspicious behaviour in Lix, feel free to mention it on
+Matrix or [file a bug on Forgejo][bugs]. If you would like to participate in
+beta testing of future Lix versions, we have a [guide on the wiki][beta-guide]
+and a [Matrix channel][beta-channel] for running `main`.
+
+[bugs]: https://git.lix.systems/lix-project/lix/issues
+[beta-guide]: https://wiki.lix.systems/books/lix-contributors/page/lix-beta-guide
+[beta-channel]: https://matrix.to/#/#open-beta:lix.systems
+
+We would especially like to thank all the following groups for their hard work
+and trust in contributing to this release:
+- The several dozen Lix beta testers who have been running Lix `main` in
+  production for over a month, and who have helped us fix the various
+  longstanding CppNix bugs they have had stuck in their craw as well as put up
+  with our work-in-progress infrastructure as we built it out.
+- All the first time contributors who made their first contributions to a Nix
+  implementation in Lix. We are eternally grateful to everyone who helped us out
+  on the numerous important but tedious issues.
+- All the people new to Nix who have trusted us by running experimental
+  versions of Lix and given us feedback.
+- The long time CppNix contributors who came to Lix and helped out with fixing
+  many issues.
+- The CppNix contributors and CppNix team, without whom we would not have this
+  software, and who wrote many of the bug fixes we backported to Lix from CppNix
+  versions > 2.18.
+- Everyone else who has worked with us on starting to make this dream a
+  reality.
+
+We are very proud of what everyone has achieved with this release since we
+begun in late February 2024, and we are just getting started. We are looking
+forward to continue working together with everyone to build a better foundation
+for the future evolution of Nix.
+

content/blog/_index.md

@@ -0,0 +1,6 @@
++++
+aliases = ["posts", "articles", "blog", "news"]
+title = "News"
+author = "Lix Team"
+tags = ["index"]
++++

content/community-standards.md

@@ -1,7 +1,7 @@
 ---
 title:  "Community Standards"
 description: "making Lix a safe and productive environment <3"
-date: "2024-04-27"
+date: "2024-05-14"
 author: "Lix Team"
 ---
 
@@ -15,7 +15,7 @@ The following are *principles* and do not in any way limit the authority of the
     - We want to avoid creating unnecessary social hierarchy and avoid unaccountable positions in the project.
     - These expectations apply to everyone in the project including the core team and the interim community team.
 - The Lix community is significantly comprised of people of various marginalised backgrounds. We are committed to protecting these people and providing a safe environment for them.
-    - If you are of a less-marginalised background, keep in mind that you are a guest in our spaces and although you are welcome, you are nonetheless a guest.
+    - If you are of a less-marginalised background, keep in mind that you are a guest in our spaces but are nonetheless welcome. Think of it like staying at a friend's place where they might have different cultural customs; you may have to do things a little bit differently.
 - We want to build leadership in community members and help them grow.
 - Technology is neither neutral nor apolitical. We consider how decisions affect different groups of people, and how they may create power dynamics or other consequences.
 - Impact is more important than intent.
@@ -44,8 +44,9 @@ We encourage working through conflicts privately with involved parties, but we a
 
 If you wish to contact a member of the interim community team about a concern, consider contacting one of the following people:
 
-- ktemkin (@ktemkin:katesiria.org)
-- jade (@jade_:matrix.org)
 - qyriad (@qyriad:katesiria.org)
+- piegames (@piegames:flausch.social)
+- ktemkin (@ktemkin:katesiria.org)
 - hexchen (@hexchen:colon.at)
 - lunaphied (@lunaphied:lunaphied.me)
+- jade (@jade_:matrix.org)

content/community.md

@@ -5,8 +5,8 @@ date: "2024-04-27"
 author: "Lix Team"
 ---
 
-Lix exists **first and foremost for its community** --- and we very much hope that will include you!
+Lix exists **first and foremost for its community** -- and we very much hope that will include you!
-If you're looking for help, have any questions, want to pitch in --- or just want to talk --- join us
+If you're looking for help, have any questions, want to pitch in -- or just want to talk -- join us
 using [one of the venues below](#engaging-with-the-community) .
 
 ## Community Standards
@@ -24,22 +24,22 @@ nor a small foundation board that governs the community. Instead, **we rely on t
 and users to carry the burdens of maintenance and governance**.
 
 We're currently in the process of establishing a more full-fledged governance model, which we believe must
-be built on engagement with --- and feedback from --- our community. In the interim, decisions are made by
+be built on engagement with -- and feedback from -- our community. In the interim, decisions are made by
 simple voting, with one vote held by each member of the "[core team](/team)", who are acting as interim
 governance.
 
 ## Engaging with the Community
 
-The best way to engage with the community currently is to **join our Matrix space** --- a decentralized 
+The best way to engage with the community currently is to **join our Matrix space** -- a decentralized 
 chat platform commonly used among open-source projects.
 
 ### Lix Matrix
 
-Joining is relatively straightforward --- you can find us on the `lix.systems` Matrix server.
+Joining is relatively straightforward -- you can find us on the `lix.systems` Matrix server.
 The easiest way to connect with us is to join our [Matrix space](https://matrix.to/#/#space:lix.systems),
 which will allow you to see previews of and join the most relevant community rooms.
 
-Note that all community venues --- including our Matrix rooms --- are subject to our [community standards](/community-standards).
+Note that all community venues -- including our Matrix rooms -- are subject to our [community standards](/community-standards).
 
 ### Community Resources
 

content/faq.md

@@ -5,7 +5,7 @@ date: "2024-05-01"
 author: "Lix Team"
 ---
 
-These are the most common questions we get --- or anticipate getting. If you can't find the answer
+These are the most common questions we get -- or anticipate getting. If you can't find the answer
 you're looking for, please feel free to ask over in the [community](/community).
 
 <br/>
@@ -20,31 +20,31 @@ Check out the [install page](/install) to see how to use Lix with your existing
 #### Q: What are your plans for flakes?
 
 One of our primary goals is compatibility. While flakes are an experimental technology, their use is
-widespread enough that they've become a de-facto part of the Nix ecosystem --- and thus we consider them
+widespread enough that they've become a de-facto part of the Nix ecosystem -- and thus we consider them
 to be part of our compatibility guarantee.
 
 That said, we're not tied to any particular flake implementation. As Lix develops, we plan on adding an
-extension system for the tooling --- which will allow technologies like flakes, as well as new and different
+extension system for the tooling -- which will allow technologies like flakes, as well as new and different
-extensions --- to seamlessly act with the Lix core without needing to reside long-term in the Lix tree.
+extensions -- to seamlessly act with the Lix core without needing to reside long-term in the Lix tree.
 
 _Flakes are not the only way to write Nix language code in Lix, and we intend to provide a good experience
-to those using flakes --- while also improving the experience for those not using them --- 
+to those using flakes -- while also improving the experience for those not using them -- 
 by evolving a compatible but more flexible flake-like abstraction in the periphery of the Lix system._
 
 
 #### Q: What relation does Lix have to the Nix Foundation, and to related projects?
 
 Besides being a fork of CppNix and an implementation of the Nix language, Lix is the
-effort of a number of long-time Nix, Nixpkgs, NixOS, and Tvix contributors and maintainers --- and has
+effort of a number of long-time Nix, Nixpkgs, NixOS, and Tvix contributors and maintainers -- and has
 been developed in partnership with a number of prolific Nix-documenters, bloggers, and users.
 
-We welcome anyone who wants to develop for both Lix and another implementation --- including CppNix and Tvix,
+We welcome anyone who wants to develop for both Lix and another implementation -- including CppNix and Tvix,
 and our open-source implementation absolutely allows any developer to integrate our code into any
 license-compatible project.
 
 However, ___Lix does not fall under the NixOS Foundation umbrella___, is funded independently of the foundation,
 and is not in any way controlled by its leadership. With the recent reboot of the foundation's governance,
-we are in communication with --- and open to collaboration with --- the foundation.
+we are in communication with -- and open to collaboration with -- the foundation.
 
 #### Q: How does Lix work? How can I contribute or help out?
 
@@ -55,7 +55,7 @@ compiling lists of resources, web design, bug tracker triage, and more. If you'r
 to get started on, we have triaged some tasks
 [that we believe should be straightforward](https://git.lix.systems/lix-project/lix/issues?q=&type=all&sort=&state=open&labels=157&milestone=0&project=0&assignee=0&poster=0). To read more
 about which tasks we recommend taking on, see
-[Freezes and recommended contributions](https://git.lix.systems/lix-project/lix/src/branch/main/CONTRIBUTING.md).
+[Freezes and recommended contributions](https://wiki.lix.systems/link/9).
 
 Feel free to ask for help in the Lix development channel. Especially feel free to ask for us to write down 
 more work that we would like help with, or to write contribution information that is missing; 
@@ -88,11 +88,11 @@ will gladly make you one manually.
 #### Q: If Lix plans to adopt Rust, what makes it different from Tvix?
 
 Unlike Lix, [Tvix](https://tvix.dev/) is a ground-up re-implementation of the Nix language in Rust,
-which shares many of the same modernization goals as Lix --- but also has a long way to go before it can
+which shares many of the same modernization goals as Lix -- but also has a long way to go before it can
 reach feature parity (and parity in correctness) with the CppNix and Lix implementations.
 
-Lix instead plans a _top-down_, _piecewise_ approach to our Rust extensions and replacements --- which means
+Lix instead plans a _top-down_, _piecewise_ approach to our Rust extensions and replacements -- which means
-that Lix already has feature-parity with --- and correctness exceeding --- the original CppNix.
+that Lix already has feature-parity with -- and correctness exceeding -- the original CppNix.
 
 
 #### Q: What does the name Lix stand for? How is it pronounced?
@@ -100,5 +100,5 @@ that Lix already has feature-parity with --- and correctness exceeding --- the o
 Like Nix, Lix isn't really short for anything. The name originally derives from the term _Layered Nix_,
 based on the premise of layering new language and tooling features atop a fully-compatible, rock-solid base.
 
-Lix is pronounced like _licks_ --- i.e. what you might do if someone handed you a delicious ice cream cone;
+Lix is pronounced like _licks_ -- i.e. what you might do if someone handed you a delicious ice cream cone;
 which may or may not be stacked up with lambdas.

content/install.md

@@ -9,7 +9,7 @@ Whether you're a new or returning user, **we're thrilled you've decided to pick
 
 Lix works out-of-the-box on most Linux and MacOS systems, including with system management tools
 such as [home-manager](https://github.com/nix-community/home-manager) and
-[nix-darwin](https://github.com/LnL7/nix-darwin) --- but, like any Nix-based system, some Nix background
+[nix-darwin](https://github.com/LnL7/nix-darwin) -- but, like any Nix-based system, some Nix background
 knowledge is recommended before installation.
 
 If you're new to the Nix ecosystem, you may want to check out some [community resources](/resources)
@@ -20,13 +20,11 @@ first, to get familiar with how Nix works.
 
 If you haven't already installed NixOS, do so using any upstream
 [install image](https://nixos.org/download/#NixOS) and the instructions in the
-[NixOS Manual](https://nixos.org/manual/nixos/stable/#sec-installation). Then, follow 
+[NixOS Manual](https://nixos.org/manual/nixos/stable/#sec-installation).
-the instructions for either:
 
-- [flake-based configurations](/add-to-config#flake-based-configurations); or
+Then, follow the [instructions to add Lix to your
-- [non-flake configurations](/add-to-config#non-flake-configurations)
+configuration](/add-to-config). Both flake-based and non-flake-based
-
+configurations are fully supported.
-depending on how you prefer to configure your system.
 
 
 ## On an Existing `nix-darwin` Install
@@ -55,7 +53,7 @@ Open a terminal, and run the following command:
 curl -sSf -L https://install.lix.systems/lix | sh -s -- install
 ```
 
-The installer will guide you through installing Lix --- and once it's finished, 
+The installer will guide you through installing Lix -- and once it's finished,
 you'll have a full, working installation. If you're not sure what to do, now is a
 great time to check out some of the [community's resources on Nix](/resources).
 
@@ -69,12 +67,12 @@ of the `upgrade-nix` command.
 Thanks to Nix, we can actually ask Lix to upgrade your system directly. Run the following command:
 
 ```sh
-sudo nix run \
+sudo --preserve-env=PATH nix run \
      --experimental-features "nix-command flakes" \
-     --extra-substituters https://cache.lix.systems \
+     --extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o=" \
-     --trusted-public-keys "cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o=" \
+     'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90.0-rc1' -- \
-     'git+https://git@git.lix.systems/lix-project/lix?ref=refs/tags/2.90-beta.0' -- \
+     upgrade-nix \
-     upgrade-nix
+     --extra-substituters https://cache.lix.systems --extra-trusted-public-keys "cache.lix.systems:aBnZUw8zA7H35Cz2RyKFVs3H4PlGTLawyY5KRbvJR8o="
 ```
 
 You should now have upgraded to Lix! You can verify this by asking the `nix` command
@@ -82,7 +80,7 @@ to report its version:
 
 ```sh
 $ nix --version
-nix (Lix, like Nix) 2.90.0-beta.1
+nix (Lix, like Nix) 2.90.0
 ```
 
 As long as you see `Lix` in the output, you're good! If you're not sure what to do now, it's a
@@ -96,4 +94,4 @@ If you're having difficulty installing Lix, don't panic! Hop on over to our
 ## Feedback?
 
 If you have thoughts on these instructions, feel free to drop by our [community](/community),
-or to [make a pull request to our website](git@git.lix.systems:lix-project/lix-website.git)!
+or to [make a pull request to our website](https://git.lix.systems/lix-project/lix-website/pulls)!

content/post/_index.md

@@ -1,6 +0,0 @@
-+++
-aliases = ["posts", "articles", "blog", "showcase", "docs"]
-title = "Posts"
-author = "Hugo Authors"
-tags = ["index"]
-+++

content/post/emoji-support.md

@@ -1,46 +0,0 @@
-+++
-author = "Hugo Authors"
-title = "Emoji Support"
-date = "2019-03-05"
-description = "Guide to emoji usage in Hugo"
-tags = [
-    "emoji",
-]
-+++
-
-Emoji can be enabled in a Hugo project in a number of ways. 
-<!--more-->
-The [`emojify`](https://gohugo.io/functions/emojify/) function can be called directly in templates or [Inline Shortcodes](https://gohugo.io/templates/shortcode-templates/#inline-shortcodes). 
-
-To enable emoji globally, set `enableEmoji` to `true` in your site's [configuration](https://gohugo.io/getting-started/configuration/) and then you can type emoji shorthand codes directly in content files; e.g.
-
-<p><span class="nowrap"><span class="emojify">🙈</span> <code>:see_no_evil:</code></span>  <span class="nowrap"><span class="emojify">🙉</span> <code>:hear_no_evil:</code></span>  <span class="nowrap"><span class="emojify">🙊</span> <code>:speak_no_evil:</code></span></p>
-<br>
-
-The [Emoji cheat sheet](http://www.emoji-cheat-sheet.com/) is a useful reference for emoji shorthand codes.
-
-***
-
-**N.B.** The above steps enable Unicode Standard emoji characters and sequences in Hugo, however the rendering of these glyphs depends on the browser and the platform. To style the emoji you can either use a third party emoji font or a font stack; e.g.
-
-{{< highlight html >}}
-.emoji {
-  font-family: Apple Color Emoji, Segoe UI Emoji, NotoColorEmoji, Segoe UI Symbol, Android Emoji, EmojiSymbols;
-}
-{{< /highlight >}}
-
-{{< css.inline >}}
-<style>
-.emojify {
-	font-family: Apple Color Emoji, Segoe UI Emoji, NotoColorEmoji, Segoe UI Symbol, Android Emoji, EmojiSymbols;
-	font-size: 2rem;
-	vertical-align: middle;
-}
-@media screen and (max-width:650px) {
-  .nowrap {
-    display: block;
-    margin: 25px 0;
-  }
-}
-</style>
-{{< /css.inline >}}

content/post/markdown-syntax.md

@@ -1,148 +0,0 @@
-+++
-author = "Hugo Authors"
-title = "Markdown Syntax Guide"
-date = "2019-03-11"
-description = "Sample article showcasing basic Markdown syntax and formatting for HTML elements."
-tags = [
-    "markdown",
-    "css",
-    "html",
-]
-categories = [
-    "themes",
-    "syntax",
-]
-series = ["Themes Guide"]
-aliases = ["migrate-from-jekyl"]
-+++
-
-This article offers a sample of basic Markdown syntax that can be used in Hugo content files, also it shows whether basic HTML elements are decorated with CSS in a Hugo theme.
-<!--more-->
-
-## Headings
-
-The following HTML `<h1>`—`<h6>` elements represent six levels of section headings. `<h1>` is the highest section level while `<h6>` is the lowest.
-
-# H1
-## H2
-### H3
-#### H4
-##### H5
-###### H6
-
-## Paragraph
-
-Xerum, quo qui aut unt expliquam qui dolut labo. Aque venitatiusda cum, voluptionse latur sitiae dolessi aut parist aut dollo enim qui voluptate ma dolestendit peritin re plis aut quas inctum laceat est volestemque commosa as cus endigna tectur, offic to cor sequas etum rerum idem sintibus eiur? Quianimin porecus evelectur, cum que nis nust voloribus ratem aut omnimi, sitatur? Quiatem. Nam, omnis sum am facea corem alique molestrunt et eos evelece arcillit ut aut eos eos nus, sin conecerem erum fuga. Ri oditatquam, ad quibus unda veliamenimin cusam et facea ipsamus es exerum sitate dolores editium rerore eost, temped molorro ratiae volorro te reribus dolorer sperchicium faceata tiustia prat.
-
-Itatur? Quiatae cullecum rem ent aut odis in re eossequodi nonsequ idebis ne sapicia is sinveli squiatum, core et que aut hariosam ex eat.
-
-## Blockquotes
-
-The blockquote element represents content that is quoted from another source, optionally with a citation which must be within a `footer` or `cite` element, and optionally with in-line changes such as annotations and abbreviations.
-
-#### Blockquote without attribution
-
-> Tiam, ad mint andaepu dandae nostion secatur sequo quae.
-> **Note** that you can use *Markdown syntax* within a blockquote.
-
-#### Blockquote with attribution
-
-> Don't communicate by sharing memory, share memory by communicating.<br>
-> — <cite>Rob Pike[^1]</cite>
-
-[^1]: The above quote is excerpted from Rob Pike's [talk](https://www.youtube.com/watch?v=PAAkCSZUG1c) during Gopherfest, November 18, 2015.
-
-## Tables
-
-Tables aren't part of the core Markdown spec, but Hugo supports supports them out-of-the-box.
-
-   Name | Age
---------|------
-    Bob | 27
-  Alice | 23
-
-#### Inline Markdown within tables
-
-| Italics   | Bold     | Code   |
-| --------  | -------- | ------ |
-| *italics* | **bold** | `code` |
-
-## Code Blocks
-
-#### Code block with backticks
-
-```html
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8">
-  <title>Example HTML5 Document</title>
-</head>
-<body>
-  <p>Test</p>
-</body>
-</html>
-```
-
-#### Code block indented with four spaces
-
-    <!doctype html>
-    <html lang="en">
-    <head>
-      <meta charset="utf-8">
-      <title>Example HTML5 Document</title>
-    </head>
-    <body>
-      <p>Test</p>
-    </body>
-    </html>
-
-#### Code block with Hugo's internal highlight shortcode
-{{< highlight html >}}
-<!doctype html>
-<html lang="en">
-<head>
-  <meta charset="utf-8">
-  <title>Example HTML5 Document</title>
-</head>
-<body>
-  <p>Test</p>
-</body>
-</html>
-{{< /highlight >}}
-
-## List Types
-
-#### Ordered List
-
-1. First item
-2. Second item
-3. Third item
-
-#### Unordered List
-
-* List item
-* Another item
-* And another item
-
-#### Nested list
-
-* Fruit
-  * Apple
-  * Orange
-  * Banana
-* Dairy
-  * Milk
-  * Cheese
-
-## Other Elements — abbr, sub, sup, kbd, mark
-
-<abbr title="Graphics Interchange Format">GIF</abbr> is a bitmap image format.
-
-H<sub>2</sub>O
-
-X<sup>n</sup> + Y<sup>n</sup> = Z<sup>n</sup>
-
-Press <kbd><kbd>CTRL</kbd>+<kbd>ALT</kbd>+<kbd>Delete</kbd></kbd> to end the session.
-
-Most <mark>salamanders</mark> are nocturnal, and hunt for insects, worms, and other small creatures.

content/post/math-typesetting.md

@@ -1,49 +0,0 @@
----
-author: Hugo Authors
-title: Math Typesetting
-date: 2019-03-08
-description: A brief guide to setup KaTeX
-math: true
----
-
-Mathematical notation in a Hugo project can be enabled by using third party JavaScript libraries.
-<!--more-->
-
-In this example we will be using [KaTeX](https://katex.org/)
-
-- Create a partial under `/layouts/partials/math.html`
-- Within this partial reference the [Auto-render Extension](https://katex.org/docs/autorender.html) or host these scripts locally.
-- Include the partial in your templates like so:  
-
-```bash
-{{ if or .Params.math .Site.Params.math }}
-{{ partial "math.html" . }}
-{{ end }}
-```
-
-- To enable KaTex globally set the parameter `math` to `true` in a project's configuration
-- To enable KaTex on a per page basis include the parameter `math: true` in content files
-
-**Note:** Use the online reference of [Supported TeX Functions](https://katex.org/docs/supported.html)
-
-{{< math.inline >}}
-{{ if or .Page.Params.math .Site.Params.math }}
-<!-- KaTeX -->
-<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/katex@0.11.1/dist/katex.min.css" integrity="sha384-zB1R0rpPzHqg7Kpt0Aljp8JPLqbXI3bhnPWROx27a9N0Ll6ZP/+DiW/UqRcLbRjq" crossorigin="anonymous">
-<script defer src="https://cdn.jsdelivr.net/npm/katex@0.11.1/dist/katex.min.js" integrity="sha384-y23I5Q6l+B6vatafAwxRu/0oK/79VlbSz7Q9aiSZUvyWYIYsd+qj+o24G5ZU2zJz" crossorigin="anonymous"></script>
-<script defer src="https://cdn.jsdelivr.net/npm/katex@0.11.1/dist/contrib/auto-render.min.js" integrity="sha384-kWPLUVMOks5AQFrykwIup5lo0m3iMkkHrD0uJ4H5cjeGihAutqP0yW0J6dpFiVkI" crossorigin="anonymous" onload="renderMathInElement(document.body);"></script>
-{{ end }}
-{{</ math.inline >}}
-
-### Examples
-
-{{< math.inline >}}
-<p>
-Inline math: \(\varphi = \dfrac{1+\sqrt5}{2}= 1.6180339887…\)
-</p>
-{{</ math.inline >}}
-
-Block math:
-$$
- \varphi = 1+\frac{1} {1+\frac{1} {1+\frac{1} {1+\cdots} } } 
-$$

content/post/placeholder-text.md

@@ -1,45 +0,0 @@
-+++
-author = "Hugo Authors"
-title = "Placeholder Text"
-date = "2019-03-09"
-description = "Lorem Ipsum Dolor Si Amet"
-tags = [
-    "markdown",
-    "text",
-]
-+++
-
-Lorem est tota propiore conpellat pectoribus de pectora summo. <!--more-->Redit teque digerit hominumque toris verebor lumina non cervice subde tollit usus habet Arctonque, furores quas nec ferunt. Quoque montibus nunc caluere tempus inhospita parcite confusaque translucet patri vestro qui optatis lumine cognoscere flos nubis! Fronde ipsamque patulos Dryopen deorum.
-
-1. Exierant elisi ambit vivere dedere
-2. Duce pollice
-3. Eris modo
-4. Spargitque ferrea quos palude
-
-Rursus nulli murmur; hastile inridet ut ab gravi sententia! Nomine potitus silentia flumen, sustinet placuit petis in dilapsa erat sunt. Atria tractus malis.
-
-1. Comas hunc haec pietate fetum procerum dixit
-2. Post torum vates letum Tiresia
-3. Flumen querellas
-4. Arcanaque montibus omnes
-5. Quidem et
-
-# Vagus elidunt
-
-<svg class="canon" xmlns="http://www.w3.org/2000/svg" overflow="visible" viewBox="0 0 496 373" height="373" width="496"><g fill="none"><path stroke="#000" stroke-width=".75" d="M.599 372.348L495.263 1.206M.312.633l494.95 370.853M.312 372.633L247.643.92M248.502.92l246.76 370.566M330.828 123.869V1.134M330.396 1.134L165.104 124.515"></path><path stroke="#ED1C24" stroke-width=".75" d="M275.73 41.616h166.224v249.05H275.73zM54.478 41.616h166.225v249.052H54.478z"></path><path stroke="#000" stroke-width=".75" d="M.479.375h495v372h-495zM247.979.875v372"></path><ellipse cx="498.729" cy="177.625" rx=".75" ry="1.25"></ellipse><ellipse cx="247.229" cy="377.375" rx=".75" ry="1.25"></ellipse></g></svg>
-
-[The Van de Graaf Canon](https://en.wikipedia.org/wiki/Canons_of_page_construction#Van_de_Graaf_canon)
-
-## Mane refeci capiebant unda mulcebat
-
-Victa caducifer, malo vulnere contra dicere aurato, ludit regale, voca! Retorsit colit est profanae esse virescere furit nec; iaculi matertera et visa est, viribus. Divesque creatis, tecta novat collumque vulnus est, parvas. **Faces illo pepulere** tempus adest. Tendit flamma, ab opes virum sustinet, sidus sequendo urbis.
-
-Iubar proles corpore raptos vero auctor imperium; sed et huic: manus caeli Lelegas tu lux. Verbis obstitit intus oblectamina fixis linguisque ausus sperare Echionides cornuaque tenent clausit possit. Omnia putatur. Praeteritae refert ausus; ferebant e primus lora nutat, vici quae mea ipse. Et iter nil spectatae vulnus haerentia iuste et exercebat, sui et.
-
-Eurytus Hector, materna ipsumque ut Politen, nec, nate, ignari, vernum cohaesit sequitur. Vel **mitis temploque** vocatus, inque alis, *oculos nomen* non silvis corpore coniunx ne displicet illa. Crescunt non unus, vidit visa quantum inmiti flumina mortis facto sic: undique a alios vincula sunt iactata abdita! Suspenderat ego fuit tendit: luna, ante urbem Propoetides **parte**.
-
-{{< css.inline >}}
-<style>
-.canon { background: white; width: 100%; height: auto; }
-</style>
-{{< /css.inline >}}

content/resources.md

@@ -5,13 +5,22 @@ date: "2024-04-27"
 author: "Lix Team"
 ---
 
-Lix doesn't exist in a vacuum --- but instead builds atop the incredible work of dozens of
+Lix doesn't exist in a vacuum -- but instead builds atop the incredible work of dozens of
 NixOS community members. This page collects resources that have been recommended by members
 of the community.
 
 We're also currently in the process of writing brand new documentation, which will be listed here
 once available.
 
+## A note of caution
+
+Nix has a long history. Some things that seemed like good ideas once are no longer common practice. In particular:
+
+- It's probably a good idea to ignore `nix-env` and mutable environments in favor of declarative configuration
+- If you don't already use channels, it's probably a good idea to learn about flakes or some other pinning mechanism instead
+
+If you're learning about those topics because you want to understand the ideas that are currently in favor in the historical contexts they are responses to, or because you think you see a benefit to them that others don't, that's totally fine; this warning is only here to help beginners have a fruitful experience.
+
 ## Understanding Nix
 
 - [The official Nix ecosystem documentation](https://nix.dev), maintained by the **NixOS Foundation**.

content/team.md

@@ -13,7 +13,7 @@ and users to carry the burdens of maintenance and governance.
 
 The **core team** are the developers most directly responsible for the Lix project. While the project
 is in its "soft-release" period, these folks are responsible for project governance. One of their main
-tasks is to establish a lasting governance model --- and other teams to handle things!
+tasks is to establish a lasting governance model -- and other teams to handle things!
 
 Members (in alphabetical order):
 
@@ -44,23 +44,24 @@ Members (in alphabetical order):
 - **puck ([@puckipedia](https://github.com/puckipedia), she/her [singular] or they/them [plural])**
 
 - **Qyriad ([@Qyriad](https://github.com/Qyriad), she/her [singular] or they/them [plural])**  
-  Build system experts who delve way, way too deep into tooling --- so you don't have to. 
+  Build system experts who delve way, way too deep into tooling -- so you don't have to. 
 
 - **raito ([@RaitoBezarius](https://github.com/RaitoBezarius), he/him)**  
   Raito is working on nixpkgs packaging, infrastructure, and review in Lix. 
   They are a Tvix developer focusing on the store and the evaluator.
 
 - **Rebecca Turner ([@9999years](https://github.com/9999years), she/her)**  
+  Rebecca is working on the evaluator and error messages.
 
 <br/>
 
 We all hang around in [community spaces](/community), including on Matrix. Feel free to pop into
-the Lix channels and say hello --- we'd love to hear what you think of Lix!
+the Lix channels and say hello -- we'd love to hear what you think of Lix!
 
 ## Conflict of Interest Statements
 
 As a community project, it's important that project decisions are made **exclusively for the
-benefit of the community**, and don't serve any other interests --- including personal or corporate gain.
+benefit of the community**, and don't serve any other interests -- including personal or corporate gain.
 
 If a team member is unable to do so in any context, they are **required** to disclose the _conflict of interest_
 and to recuse themselves from any leadership decisions affected.
@@ -117,7 +118,12 @@ conflicts of interest.
   aiming to promote the parisian Ecole Normale Superieure (45 rue d'Ulm, 75005 Paris) excellence on computer 
   science using heavily Nix/NixOS based technologies.
 
-- **Rebecca Turner** works for mercury.com, a company that uses nix to build software. **Should a governance decision involving these or any other financial ties arise, wiggles will recuse herself from the relevant decision-making.**
+- **Rebecca Turner** works for [Mercury](https://mercury.com/), a financial
+  services startup that [uses
+  Nix](https://serokell.io/blog/haskell-in-production-mercury) to build
+  software. **Should a governance decision involving these or any other
+  financial ties arise, Rebecca will recuse herself from the relevant
+  decision-making.**
 
 <br />
 

flake.lock

@@ -20,16 +20,16 @@
     },
     "nixpkgs": {
       "locked": {
-        "lastModified": 1713995372,
+        "lastModified": 1720553833,
-        "narHash": "sha256-fFE3M0vCoiSwCX02z8VF58jXFRj9enYUSTqjyHAjrds=",
+        "narHash": "sha256-IXMiHQMtdShDXcBW95ctA+m5Oq2kLxnBt7WlMxvDQXA=",
         "owner": "NixOS",
         "repo": "nixpkgs",
-        "rev": "dd37924974b9202f8226ed5d74a252a9785aedf8",
+        "rev": "249fbde2a178a2ea2638b65b9ecebd531b338cf9",
         "type": "github"
       },
       "original": {
         "owner": "NixOS",
-        "ref": "nixos-23.11",
+        "ref": "nixos-24.05",
         "repo": "nixpkgs",
         "type": "github"
       }

flake.nix

@@ -8,7 +8,7 @@
   # The sources we depend on.
   #
   inputs = {
-    nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11";
+    nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.05";
     flake-utils.url = "github:numtide/flake-utils";
   };
 

themes/lix/layouts/_default/list.html

@@ -22,7 +22,7 @@
             </div>
             <div class="card-body">
               <h5 class="card-title fw-semibold">{{ .Title }}</h5>
-              <p class="card-text text-black-61">{{ .Summary | plainify }}</p>
+              <p class="card-text text-black-61">{{ .Summary }}</p>
             </div>
           </a>
         </div>

themes/lix/layouts/partials/icons/git.html

@@ -1 +1 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="92pt" height="92pt" viewBox="0 0 92 92"><defs><clipPath id="a"><path d="M0 .113h91.887V92H0Zm0 0"/></clipPath></defs><g clip-path="url(#a)"><path style="stroke:none;fill-rule:nonzero;fill:#f03c2e;fill-opacity:1" d="M90.156 41.965 50.036 1.848a5.918 5.918 0 0 0-8.372 0l-8.328 8.332 10.566 10.566a7.03 7.03 0 0 1 7.23 1.684 7.034 7.034 0 0 1 1.669 7.277l10.187 10.184a7.028 7.028 0 0 1 7.278 1.672 7.04 7.04 0 0 1 0 9.957 7.05 7.05 0 0 1-9.965 0 7.044 7.044 0 0 1-1.528-7.66l-9.5-9.497V59.36a7.04 7.04 0 0 1 1.86 11.29 7.04 7.04 0 0 1-9.957 0 7.04 7.04 0 0 1 0-9.958 7.06 7.06 0 0 1 2.304-1.539V33.926a7.049 7.049 0 0 1-3.82-9.234L29.242 14.272 1.73 41.777a5.925 5.925 0 0 0 0 8.371L41.852 90.27a5.925 5.925 0 0 0 8.37 0l39.934-39.934a5.925 5.925 0 0 0 0-8.371"/></g></svg>
+<svg xmlns="http://www.w3.org/2000/svg" width="16px" height="16px" viewBox="0 0 92 92"><defs><clipPath id="a"><path d="M0 .113h91.887V92H0Zm0 0"/></clipPath></defs><g clip-path="url(#a)"><path style="stroke:none;fill-rule:nonzero;fill:#f03c2e;fill-opacity:1" d="M90.156 41.965 50.036 1.848a5.918 5.918 0 0 0-8.372 0l-8.328 8.332 10.566 10.566a7.03 7.03 0 0 1 7.23 1.684 7.034 7.034 0 0 1 1.669 7.277l10.187 10.184a7.028 7.028 0 0 1 7.278 1.672 7.04 7.04 0 0 1 0 9.957 7.05 7.05 0 0 1-9.965 0 7.044 7.044 0 0 1-1.528-7.66l-9.5-9.497V59.36a7.04 7.04 0 0 1 1.86 11.29 7.04 7.04 0 0 1-9.957 0 7.04 7.04 0 0 1 0-9.958 7.06 7.06 0 0 1 2.304-1.539V33.926a7.049 7.049 0 0 1-3.82-9.234L29.242 14.272 1.73 41.777a5.925 5.925 0 0 0 0 8.371L41.852 90.27a5.925 5.925 0 0 0 8.37 0l39.934-39.934a5.925 5.925 0 0 0 0-8.371"/></g></svg>

themes/lix/layouts/partials/icons/mastodon.html

@@ -1,4 +1,4 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="61.076954mm" height="65.47831mm" viewBox="0 0 216.4144 232.00976">
+<svg xmlns="http://www.w3.org/2000/svg" width="16px" height="17.15px" viewBox="0 0 216.4144 232.00976">
   <path fill="#2b90d9" d="M211.80734 139.0875c-3.18125 16.36625-28.4925 34.2775-57.5625 37.74875-15.15875 1.80875-30.08375 3.47125-45.99875 2.74125-26.0275-1.1925-46.565-6.2125-46.565-6.2125 0 2.53375.15625 4.94625.46875 7.2025 3.38375 25.68625 25.47 27.225 46.39125 27.9425 21.11625.7225 39.91875-5.20625 39.91875-5.20625l.8675 19.09s-14.77 7.93125-41.08125 9.39c-14.50875.7975-32.52375-.365-53.50625-5.91875C9.23234 213.82 1.40609 165.31125.20859 116.09125c-.365-14.61375-.14-28.39375-.14-39.91875 0-50.33 32.97625-65.0825 32.97625-65.0825C49.67234 3.45375 78.20359.2425 107.86484 0h.72875c29.66125.2425 58.21125 3.45375 74.8375 11.09 0 0 32.975 14.7525 32.975 65.0825 0 0 .41375 37.13375-4.59875 62.915"/>
   <path fill="#fff" d="M177.50984 80.077v60.94125h-24.14375v-59.15c0-12.46875-5.24625-18.7975-15.74-18.7975-11.6025 0-17.4175 7.5075-17.4175 22.3525v32.37625H96.20734V85.42325c0-14.845-5.81625-22.3525-17.41875-22.3525-10.49375 0-15.74 6.32875-15.74 18.7975v59.15H38.90484V80.077c0-12.455 3.17125-22.3525 9.54125-29.675 6.56875-7.3225 15.17125-11.07625 25.85-11.07625 12.355 0 21.71125 4.74875 27.8975 14.2475l6.01375 10.08125 6.015-10.08125c6.185-9.49875 15.54125-14.2475 27.8975-14.2475 10.6775 0 19.28 3.75375 25.85 11.07625 6.36875 7.3225 9.54 17.22 9.54 29.675"/>
 </svg>

themes/lix/layouts/partials/icons/matrix.html

@@ -1,4 +1,4 @@
-<svg version="1.1" viewBox="0 0 27.9 32" xmlns="http://www.w3.org/2000/svg" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+<svg version="1.1" viewBox="0 0 27.9 32" width="16px" height="18px" xmlns="http://www.w3.org/2000/svg" xmlns:cc="http://creativecommons.org/ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <title>Matrix (protocol) logo</title>
  <g transform="translate(-.095 .005)" fill="#040404">
   <path d="m27.1 31.2v-30.5h-2.19v-0.732h3.04v32h-3.04v-0.732z"/>

themes/lix/layouts/partials/sections/ecosystem.html

@@ -10,7 +10,7 @@
         {{ end }}
       </div>
     </div>
-    <div class="row g-5">
+    <div class="row g-4 g-md-5">
       {{ range .content.cards }}
         <div class="col-12 col-xl-4">
           <div class="card bg-blue-16 border-0 border-radius-34 p-4">

themes/lix/layouts/partials/shared/footer.html

@@ -6,7 +6,7 @@
         <p class="small text-black-61">{{ .Site.Params.description }}</p>
         {{ with .Site.Params.social }}
         <ul class="d-flex justify-content-center justify-content-xl-start list-unstyled">
-          {{ with .mastodon }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/mastodon.html" }}</a></li>{{ end }}
+          {{ with .mastodon }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a rel="me" class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/mastodon.html" }}</a></li>{{ end }}
           {{ with .matrix }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/matrix.html" }}</a></li>{{ end }}
           {{ with .github }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/github.html" }}</a></li>{{ end }}
           {{ with .git }}<li class="rounded-circle bg-blue-63 me-2 p-2"><a class="d-flex align-items-center justify-content-center size-16 svglogo" href="{{ . }}">{{ partial "icons/git.html" }}</a></li>{{ end }}