diff --git a/arctic_build/__pages/index.html b/arctic_build/__pages/index.html index dc4ee17..015c350 100644 --- a/arctic_build/__pages/index.html +++ b/arctic_build/__pages/index.html @@ -12,9 +12,11 @@

Arctic websites use content-to-HTML compilers that are easy to extend and can helpfully validate content. To get a sense of how this works, check out the quickstart! -

You could call it static, or you could call it frozen. +Arctic uses caching to avoid re-compiling content that hasn't changed, +which keeps build times extremely fast. +

You could call it static, or you could even call it frozen. However, Arctic sites integrate well with your high-performance Gleam backends, -or any others! It's just a way of organizing your client side code, +or any other backend! It's just a way of organizing your client side code, which happens to not always require a server side codebase at all. And if you use a Gleam backend, you can reuse Lustre components across the stack!

Ecosystem Integration diff --git a/arctic_build/index.html b/arctic_build/index.html index 89664d6..40d9a78 100644 --- a/arctic_build/index.html +++ b/arctic_build/index.html @@ -21,9 +21,11 @@

Arctic websites use content-to-HTML compilers that are easy to extend and can helpfully validate content. To get a sense of how this works, check out the quickstart! -

You could call it static, or you could call it frozen. +Arctic uses caching to avoid re-compiling content that hasn't changed, +which keeps build times extremely fast. +

You could call it static, or you could even call it frozen. However, Arctic sites integrate well with your high-performance Gleam backends, -or any others! It's just a way of organizing your client side code, +or any other backend! It's just a way of organizing your client side code, which happens to not always require a server side codebase at all. And if you use a Gleam backend, you can reuse Lustre components across the stack!

Ecosystem Integration diff --git a/content/home.md b/content/home.md index 1f0b56b..369ce55 100644 --- a/content/home.md +++ b/content/home.md @@ -19,10 +19,12 @@ All of this is handled automatically by the framework. Arctic websites use content-to-HTML compilers that are easy to extend and can helpfully validate content. To get a sense of how this works, check out the [quickstart](/guides/quickstart)! +Arctic uses caching to avoid re-compiling content that hasn't changed, +which keeps build times extremely fast. -You could call it static, or you could call it frozen. +You could call it static, or you could even call it frozen. However, Arctic sites integrate well with your high-performance Gleam [backends](https://github.com/Pevensie), -or any others! It's just a way of organizing your client side code, +or any other backend! It's just a way of organizing your client side code, which happens to not always require a server side codebase at all. And if you use a Gleam backend, you can reuse Lustre components across the stack! diff --git a/dist/__pages/index.html b/dist/__pages/index.html index dc4ee17..015c350 100644 --- a/dist/__pages/index.html +++ b/dist/__pages/index.html @@ -12,9 +12,11 @@

Arctic websites use content-to-HTML compilers that are easy to extend and can helpfully validate content. To get a sense of how this works, check out the quickstart! -

You could call it static, or you could call it frozen. +Arctic uses caching to avoid re-compiling content that hasn't changed, +which keeps build times extremely fast. +

You could call it static, or you could even call it frozen. However, Arctic sites integrate well with your high-performance Gleam backends, -or any others! It's just a way of organizing your client side code, +or any other backend! It's just a way of organizing your client side code, which happens to not always require a server side codebase at all. And if you use a Gleam backend, you can reuse Lustre components across the stack!

Ecosystem Integration diff --git a/dist/index.html b/dist/index.html index 89664d6..40d9a78 100644 --- a/dist/index.html +++ b/dist/index.html @@ -21,9 +21,11 @@

Arctic websites use content-to-HTML compilers that are easy to extend and can helpfully validate content. To get a sense of how this works, check out the quickstart! -

You could call it static, or you could call it frozen. +Arctic uses caching to avoid re-compiling content that hasn't changed, +which keeps build times extremely fast. +

You could call it static, or you could even call it frozen. However, Arctic sites integrate well with your high-performance Gleam backends, -or any others! It's just a way of organizing your client side code, +or any other backend! It's just a way of organizing your client side code, which happens to not always require a server side codebase at all. And if you use a Gleam backend, you can reuse Lustre components across the stack!

Ecosystem Integration