First draft of landing page #135


-Let's see what it looks like to bring Flox to one of your existing projects.
+  :material-arrow-right-thick: Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.  


Suggested change

:material-arrow-right-thick: Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.

* Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.

I like how the right arrows look, but they don't indent properly on their second lines. Standard bullets will indent properly - perhaps @brendaneamon knows a way to accomplish this?

Agree, I'll change to standard bullets!

rossturk · 2025-05-01T18:52:13Z

docs/index.md


-Let's see what it looks like to bring Flox to one of your existing projects.
+  :material-arrow-right-thick: Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.  


I like how the right arrows look, but they don't indent properly on their second lines. Standard bullets will indent properly - perhaps @brendaneamon knows a way to accomplish this?

rossturk · 2025-05-01T18:53:34Z

docs/index.md


-=== "Python"
+    Install `flox` with `brew` and get your dev 


Suggested change

Install `flox` with `brew` and get your dev

Install `flox` and get your dev

How about

Install flox with apt, yum, or brew and ...

I still don't understand why we need to include a specific install mechanism here.

And I worry that it will confuse users: "do I need to install brew or be on Linux to use this?"

Ah, sorry I didn't explain. The reason for calling out brew specifically is because we saw in several research sessions that (1) people looked for brew as an install method but didn't see it on the website so they chose the download instead and (2) when someone did find or use brew, they were delighted to use that method.

My hypothesis is that if you just put the word brew front and center when you mention install, they won't have to click to the Install docs, and can just get started even more quickly. Adding apt and yum would do the same for those users.

How about this:

That is a fine compromise.

I understand that we have that research result, but I don't agree that putting brew front and center is the best decision. I weigh those research experiences in my mind lower than the desire not to confuse people about the role Flox plays in their stack.

rossturk · 2025-05-01T18:55:49Z

docs/index.md

-    ...select yes...
-    ✨ Created environment 'my_project' (aarch64-darwin)
-    ✅ 'python3' installed to environment 'my_project'
+    Flox makes the power of Nix more accessible for your team, and maybe for you too.


Suggested change

Flox makes the power of Nix more accessible for your team, and maybe for you too.

Flox brings the power of Nix to your team, and can simplify your workflows too.

rossturk · 2025-05-01T18:56:35Z

docs/index.md

-      $ flox activate            <- Enter the environment
-      $ flox edit                <- Add environment variables and shell hooks
-    ```
+The same challenges, no matter the stack: inconsistent environments, dependency drift, and brittle build processes that don’t scale well across machines, teams, or deployment targets. Current solutions often add complexity and fragmentation.


Suggested change

The same challenges, no matter the stack: inconsistent environments, dependency drift, and brittle build processes that don’t scale well across machines, teams, or deployment targets. Current solutions often add complexity and fragmentation.

We encounter the same challenges, no matter the stack: inconsistent environments, dependency drift, and brittle build processes that don’t scale well across machines, teams, or deployment targets. Current solutions often add complexity and fragmentation.

github-actions · 2025-05-02T18:52:56Z

🚀 Deployed on https://aef55b577b22673acb9b15e38caf3e0eed228a2d--floxdocs.netlify.app

zmitchell · 2025-05-02T18:54:56Z

docs/index.md

-Let's see what it looks like to bring Flox to one of your existing projects.
+- Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.  
+- Switch between environments easily, share them with your team, and keep everything in version control.   
+- Use the same setup across macOS and Linux, on both x86 and ARM.     


Suggested change

- Use the same setup across macOS and Linux, on both x86 and ARM.

- Use the same setup across macOS and Linux, on both x86 and Arm.

zmitchell · 2025-05-02T18:56:38Z

docs/index.md


-`cd` into your project and initialize the environment with [`flox init`][init].
+    Install `flox` with `apt`, `yum`, `brew`, or a system installer to get your dev 


system install sounds a little off to me, maybe standalone installer instead?

zmitchell · 2025-05-02T18:57:09Z

docs/index.md


-    * latest python (requirements.txt)
+    Flox brings the power of Nix to your team, and can simplify your workflows too.


Suggested change

Flox brings the power of Nix to your team, and can simplify your workflows too.

Flox brings the power of Nix to your team, and can simplify your workflows.

zmitchell · 2025-05-02T19:01:48Z

docs/index.md


-    If you accept, it will also create a virtual environment that's activated
-    automatically when you activate your Flox environment.
+Guides for getting started in just a few of the many languages Flox supports:


My nitpick about the word "guides" here is that is sounds like the linked blog posts are the suggested way of getting started, when in actuality they're examples of projects (I haven't read all of the blog posts, but that's at least how my Rust post was). Maybe "Examples" instead?

zmitchell · 2025-05-02T19:06:36Z

docs/index.md

-    If you accept, it will also add a hook that calls either `npm install` or
-    `yarn` when activating the environment so that your dependencies are up to
-    date.
+Set up a [local developer environment](https://flox.dev/docs/tutorials/creating-environments/) that will work the same across multiple system types and architectures. Seamlessly switch between development environments across multiple language ecosystems using a consistent, unified workflow.


Suggested change

Set up a [local developer environment](https://flox.dev/docs/tutorials/creating-environments/) that will work the same across multiple system types and architectures. Seamlessly switch between development environments across multiple language ecosystems using a consistent, unified workflow.

Set up a [local developer environment](https://flox.dev/docs/tutorials/creating-environments/) that will work the same across multiple operating systems and architectures. Seamlessly switch between development environments across multiple language ecosystems using a consistent, unified workflow.

system types would include both operating system and architectures in my mind, so if we've split out architectures, it makes sense to split out operating systems as well.

zmitchell · 2025-05-02T19:07:36Z

docs/index.md


---
+Set up your [default environment](https://flox.dev/docs/tutorials/default-environment/) with a set of 
+packages that you always want available, whether you're on macOS or Linux—x86 or ARM.


Suggested change

packages that you always want available, whether you're on macOS or Linux—x86 or ARM.

packages that you always want available, whether you're on macOS or Linux—x86 or Arm.

zmitchell · 2025-05-02T19:09:12Z

docs/index.md

+
+### __Consistent builds from local to CI to production__
+
+Flox lets you define what an environment _is_ in a way that can be reused across local dev, CI, and production. 


I think you could drop this sentence.

Let's leave it in. Unless @barstoolbluz would you cut it or rewrite?

zmitchell · 2025-05-02T19:09:21Z

docs/index.md

+### __Consistent builds from local to CI to production__
+
+Flox lets you define what an environment _is_ in a way that can be reused across local dev, CI, and production. 
+Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in prod. 


Suggested change

Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in prod.

Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in production.

zmitchell · 2025-05-02T19:10:58Z

docs/index.md

+Flox lets you define what an environment _is_ in a way that can be reused across local dev, CI, and production. 
+Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in prod. 
+
+Or use Flox [containerize](https://flox.dev/docs/reference/command-reference/flox-containerize/?h=containerize) to package your environments as OCI images—fully pinned and runnable anywhere. 


I'm not really sure what "fully pinned" means here. You could mention that the images only contain exactly what your software needs to run (most images build on top of an OS, and ours don't).

@barstoolbluz thoughts or revisions here?

zmitchell · 2025-05-02T19:11:36Z

docs/index.md

+
+### __And more...__
+
+- Create a reusable toolchain or templates to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).


Suggested change

- Create a reusable toolchain or templates to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).

- Create templates or reusable toolchains to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).

github-actions · 2025-05-05T15:22:02Z

🚀 Deployed on https://78bb7cfcd8f59176c9d45c354cbdd158c66f87b0--floxdocs.netlify.app

github-actions · 2025-05-05T19:40:07Z

🚀 Deployed on https://ceafbdee138641c92ccca2d5e7894dcdab9b9944--floxdocs.netlify.app

Jenny Mahmoudi and others added 4 commits February 6, 2025 17:17

Rename index.md to flox-5-minutes.md

710eee1

New index.md as landing page

5ef53fc

Add structure to the new landing page

035cbcb

Add description placeholders and video embed

21d14bb

jennymahmoudi requested review from rossturk, zmitchell, brendaneamon and barstoolbluz February 7, 2025 17:34

floxbot added the documentation Improvements or additions to documentation label Feb 7, 2025

zmitchell added 2 commits February 11, 2025 17:06

Disable inline html check

d82bdc2

Disable more linter stuff

9e20774

stahnma approved these changes Feb 19, 2025

View reviewed changes

Remove link to nvm guide in Examples section

afc9215

Update reproducible package manager use case (#146)

0a84b5f

barstoolbluz added 2 commits April 16, 2025 23:14

Update index.md

e6cca5a

added paragraph that waxes fantastically / rhapsodically about flox and ci and reproducibility uber alles.

Update index.md

45ce4f7

barstoolbluz added 2 commits April 16, 2025 23:16

Update index.md

ca97f48

Update index.md

ad63d18

Merge branch 'preview' into jennymahmoudi-landing-page

2f4f932

Move CI content, update Nix getting started

aa87c64

Add Reproducible dev environment use case

61cd950

Update Why Flox and Reproducible dev envs

9893201

Merge branch 'preview' into jennymahmoudi-landing-page

67adc2c

Jenny Mahmoudi added 2 commits April 30, 2025 18:06

Update "What is Flox?" section, Add "More" section

a9150ab

Minor changes throughout - all content here is ready for review

Linting fixes

de69157

brendaneamon reviewed May 1, 2025

View reviewed changes

docs/index.md Outdated Show resolved Hide resolved

brendaneamon reviewed May 1, 2025

View reviewed changes

docs/index.md Outdated Show resolved Hide resolved

Apply suggestions from code review

f03015e

Co-authored-by: Brendan Magee <[email protected]>

brendaneamon reviewed May 1, 2025

View reviewed changes

docs/index.md Outdated Show resolved Hide resolved

feedback from team review

ba946e3

rossturk reviewed May 1, 2025

View reviewed changes

rossturk approved these changes May 1, 2025

View reviewed changes

Jenny Mahmoudi added 2 commits May 2, 2025 14:48

changes from review feedback

9bf4069

fix indenation

aef55b5

zmitchell reviewed May 2, 2025

View reviewed changes

Changes from review feedback

78bb7cf

jennymahmoudi marked this pull request as ready for review May 5, 2025 19:37

zmitchell approved these changes May 5, 2025

View reviewed changes

Merge branch 'preview' into jennymahmoudi-landing-page

ceafbde

jennymahmoudi merged commit 3fe2050 into preview May 5, 2025
3 checks passed

jennymahmoudi deleted the jennymahmoudi-landing-page branch May 5, 2025 19:42


		Let's see what it looks like to bring Flox to one of your existing projects.
		:material-arrow-right-thick: Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.

	:material-arrow-right-thick: Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.
	* Define everything your environment needs—packages, tools, environment variables, and services—in one manifest.

	Install `flox` with `brew` and get your dev
	Install `flox` and get your dev

	Flox makes the power of Nix more accessible for your team, and maybe for you too.
	Flox brings the power of Nix to your team, and can simplify your workflows too.

	The same challenges, no matter the stack: inconsistent environments, dependency drift, and brittle build processes that don’t scale well across machines, teams, or deployment targets. Current solutions often add complexity and fragmentation.
	We encounter the same challenges, no matter the stack: inconsistent environments, dependency drift, and brittle build processes that don’t scale well across machines, teams, or deployment targets. Current solutions often add complexity and fragmentation.

	- Use the same setup across macOS and Linux, on both x86 and ARM.
	- Use the same setup across macOS and Linux, on both x86 and Arm.


		`cd` into your project and initialize the environment with [`flox init`][init].
		Install `flox` with `apt`, `yum`, `brew`, or a system installer to get your dev


		* latest python (requirements.txt)
		Flox brings the power of Nix to your team, and can simplify your workflows too.

	Set up a [local developer environment](https://flox.dev/docs/tutorials/creating-environments/) that will work the same across multiple system types and architectures. Seamlessly switch between development environments across multiple language ecosystems using a consistent, unified workflow.
	Set up a [local developer environment](https://flox.dev/docs/tutorials/creating-environments/) that will work the same across multiple operating systems and architectures. Seamlessly switch between development environments across multiple language ecosystems using a consistent, unified workflow.

	packages that you always want available, whether you're on macOS or Linux—x86 or ARM.
	packages that you always want available, whether you're on macOS or Linux—x86 or Arm.


		### __Consistent builds from local to CI to production__

		Flox lets you define what an environment _is_ in a way that can be reused across local dev, CI, and production.

	Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in prod.
	Leverage [pre-built integrations](https://flox.dev/docs/tutorials/ci-cd/?h=ci) for GitHub Actions, CircleCI, and GitLab to pull and activate the same environments locally, in CI and in production.


		### __And more...__

		- Create a reusable toolchain or templates to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).

	- Create a reusable toolchain or templates to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).
	- Create templates or reusable toolchains to bootstrap new projects by [reusing and combining dev environments](https://flox.dev/docs/tutorials/composition/).

First draft of landing page #135

First draft of landing page #135

Uh oh!

Conversation

jennymahmoudi commented Feb 7, 2025

Uh oh!

github-actions bot commented Feb 12, 2025

Uh oh!

github-actions bot commented Feb 20, 2025

Uh oh!

github-actions bot commented Mar 30, 2025

Uh oh!

github-actions bot commented Apr 17, 2025

Uh oh!

github-actions bot commented Apr 17, 2025

Uh oh!

github-actions bot commented Apr 17, 2025

Uh oh!

github-actions bot commented Apr 17, 2025

Uh oh!

github-actions bot commented Apr 29, 2025

Uh oh!

github-actions bot commented Apr 29, 2025

Uh oh!

github-actions bot commented Apr 29, 2025

Uh oh!

github-actions bot commented Apr 30, 2025

Uh oh!

github-actions bot commented Apr 30, 2025

Uh oh!

github-actions bot commented Apr 30, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented May 1, 2025

Uh oh!

github-actions bot commented May 1, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented May 2, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment