update about and themeing

This commit is contained in:
Kate Temkin 2024-04-27 19:20:05 -06:00
parent 214fc6fa18
commit 8c524f2112
7 changed files with 34 additions and 24 deletions

View file

@ -14,7 +14,6 @@ TODO List
- Create the `/install` page. - Create the `/install` page.
- Create a subsection for using Lix on existing NixOS, and link it to the box. - Create a subsection for using Lix on existing NixOS, and link it to the box.
- Create the `/about` page.
- Create a "Why Lix" section on `/about` and link to it. - Create a "Why Lix" section on `/about` and link to it.
- Create the /team page and include CoI declarations. - Create the /team page and include CoI declarations.
- Figure out where to link the "Docs" link to. - Figure out where to link the "Docs" link to.
@ -28,6 +27,7 @@ TODO List
- Replace the primary "hero" graphic with a Lix one. - Replace the primary "hero" graphic with a Lix one.
- Replace the "lix-managed systems" graphic with an image of our logo on a screen. - Replace the "lix-managed systems" graphic with an image of our logo on a screen.
- Replace the placeholders for each of the three main page "why lix" points. - Replace the placeholders for each of the three main page "why lix" points.
- Add nice images to the "/about" page.
# Wishlist # Wishlist

View file

@ -46,9 +46,9 @@ menus:
url: "https://git.lix.systems/lix-project/lix" url: "https://git.lix.systems/lix-project/lix"
weight: 3 weight: 3
- name: "Docs" #- name: "Docs"
url: "/#" # url: "/#"
weight: 4 # weight: 4
- name: "Community" - name: "Community"
url: "/community" url: "/community"

View file

@ -6,7 +6,7 @@ author: "Lix Team"
--- ---
**Lix** is an implementation of the Nix _functional package management_ language. Originally **Lix** is an implementation of the Nix _functional package management_ language. Originally
codified by [cppnix](https://github.com/NixOS/nix/), the Nix language allows you to create codified by [CppNix](https://github.com/NixOS/nix/), the Nix language allows you to create
packages that can be used for anything from **putting configuration files into place** to packages that can be used for anything from **putting configuration files into place** to
**declaratively managing an entire system**. **declaratively managing an entire system**.
@ -14,7 +14,7 @@ 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. 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 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. its developers can improve usability and ergonomics without sacrificing correctness.
@ -28,11 +28,11 @@ If you're not familiar with the Nix approach, we recommend checking out some of
The **Nix language** is used for a variety of applications ranging from individual computers The **Nix language** is used for a variety of applications ranging from individual computers
to clusters of critical infrastructure. With this in mind, the Lix team has been working to to clusters of critical infrastructure. With this in mind, the Lix team has been working to
provide a collection of necessary improvements over _cppnix_: provide a collection of necessary improvements over CppNix:
- **Built for a community, not for a corporation.** - **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 a alternative to the
commercial interests that have long plagued both upstream _cppnix_ and corporate-authored forks. commercial interests that have long plagued both upstream CppNix and corporate-authored forks.
We're proud to stand by our open [conflict of interest statement](/team#conflicts-of-interest), We're proud to stand by our open [conflict of interest statement](/team#conflicts-of-interest),
and proud to listen to community voices on issues of sponsorship, direction, and moderation. and proud to listen to community voices on issues of sponsorship, direction, and moderation.
@ -43,9 +43,9 @@ provide a collection of necessary improvements over _cppnix_:
marginalized groups. marginalized groups.
- **A correct implementation of the Nix language.** - **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 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 introduced new features and backported a number of features from newer versions without
sacrificing correctness. sacrificing correctness.
@ -70,15 +70,6 @@ using Lix in any existing Nix or NixOS configuration.
Check out the [install page](/install) to see how to use Lix with your existing configurations. Check out the [install page](/install) to see how to use Lix with your existing configurations.
#### 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
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
that Lix already has feature-parity with -- and correctness exceeding -- the original _cppnix_.
#### Q: What are your plans for flakes? #### Q: What are your plans for flakes?
One of our primary goals is compatibility. While flakes are an experimental technology, their use is One of our primary goals is compatibility. While flakes are an experimental technology, their use is
@ -92,19 +83,29 @@ extensions -- to seamlessly act with the Lix core without needing to reside long
#### Q: What relation does Lix have to the Nix Foundation, and to related projects? #### 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 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. 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 permissive open-source absolutely allows any developer to integrate our code into any and our open-source implementation absolutely allows any developer to integrate our code into any
license-compatible project. license-compatible project.
However, ___Lix does not fall under the NixOS Foundation umbrella___, is funded independently of the foundation, 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. Unfortunately, at the moment, this is currently vital for and is not in any way controlled by its leadership. Unfortunately, at the moment, this is vital for
us to deliver on our promise of a safe and inclusive community. us to deliver on our promise of a safe and inclusive community.
#### 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
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
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? #### Q: What does the name Lix stand for? How is it pronounced?
Like Nix, Lix isn't really short for anything. The name originally derives from the term _Layered Nix_, Like Nix, Lix isn't really short for anything. The name originally derives from the term _Layered Nix_,

View file

@ -24,4 +24,4 @@ content:
text: "Lix can also be used as the core Nix implementation for Nix-based operating systems and system managers, including the full NixOS distribution, as well as system management software like Home Manager or nix-darwin." text: "Lix can also be used as the core Nix implementation for Nix-based operating systems and system managers, including the full NixOS distribution, as well as system management software like Home Manager or nix-darwin."
button: button:
label: "use lix with NixOS" label: "use lix with NixOS"
url: "/install" url: "/install#on-nixos"

View file

@ -14,6 +14,11 @@
color: $primary; color: $primary;
} }
h3 {
margin-top: 2rem;
}
h4 { h4 {
font-size: inherit; font-size: inherit;
font-weight: bold; font-weight: bold;

View file

@ -0,0 +1,3 @@
.btn-primary.text-light {
font-weight: 600;
}

View file

@ -5,6 +5,7 @@
@import "header"; @import "header";
@import "footer"; @import "footer";
@import "buttons";
@import "../sections/hero"; @import "../sections/hero";
@import "../sections/brands"; @import "../sections/brands";