Skip to content

Commit 2f41b49

Browse files
committed
Update homepage
1 parent 18fcb4e commit 2f41b49

File tree

2 files changed

+7
-9
lines changed

2 files changed

+7
-9
lines changed

data/index.md

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,13 @@
11
---
2-
title: The simple web framework and site generator you could have built yourself.
2+
title: The simplest web framework and site generator yet.
33
metaTitle: 'Mastro: the simplest web framework and site generator'
44
description: 'No bloat, no magic, no config. Mastro gets out of the way, so that you can focus on building awesome websites.'
55
layout: hero
66
---
77

8-
But since you didn't, take Mastro as a starting point. It fills in the few missing pieces that aren't built into modern browsers and JavaScript runtimes:
9-
a file-based [router](/guide/server-side-components-and-routing/#routing-and-page-handlers), and a handful of [composable functions](https://jsr.io/@mastrojs/mastro/doc) to return standard [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response/Response) objects. Static site generation and on-demand rendering of HTML or JSON – it all works exactly the same in Mastro.
10-
Not compromising on developer experience, Mastro feels like a framework – but actually it's just a tiny library.
11-
12-
- **No bloat**: written in just [~700 lines](https://github.com/mastrojs/mastro/tree/main/src#readme) of TypeScript, Mastro is distilled to the essence.
8+
- **Minimal yet powerful**: Mastro fills in the few missing pieces that aren't yet built into the platform: a file-based [router](/docs/routing/) and a handful of [composable functions](/docs/html-components/) to return standard [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response/Response) objects.
9+
- **Static site generation and on-demand server rendering** of HTML or JSON [works all the same](/docs/routing/#route-handlers).
10+
- **No bloat**: written in just [~700 lines](https://github.com/mastrojs/mastro/tree/main/src#readme) of TypeScript, Mastro feels like a framework but is just a library.
1311
- **No client-side JavaScript** (until you [add some](/guide/interactivity-with-javascript-in-the-browser/)): create [MPA](/guide/client-side-vs-server-side-javascript-static-vs-ondemand-spa-vs-mpa/) websites that load blazingly [fast](#fast-for-everyone).
1412
- **No bundler** (until you [add one](/guide/bundling-assets-caching/)): your code arrives in the browser exactly how you wrote it.
1513
- **No magic**: use normal `<img>` and `<a>` tags referencing HTTP-first [assets](/guide/bundling-assets-caching/#transforming-images).
@@ -18,7 +16,7 @@ Not compromising on developer experience, Mastro feels like a framework – but
1816
- **No lock-in**: swap out calls to the Mastro library later on. Or fork it – it's only [~700 lines](https://github.com/mastrojs/mastro/tree/main/src#readme) after all.
1917

2018
<a class="button" data-goatcounter-click="home.try" data-goatcounter-title="top" href="https://github.dev/mastrojs/template-basic">Try online with GitHub</a>
21-
<a class="button -secondary" href="#experienced-developers-–-do-you-want-off-the-frontend-treadmill%3F">Install with Deno, Node.js or Bun</a>
19+
<a class="button -secondary" href="#powerful-for-experienced-developers">Install with Deno, Node.js or Bun</a>
2220

2321
<p>
2422
<picture>
@@ -116,7 +114,7 @@ Start with HTML and CSS. Then build a blog, and a to-do list app with JavaScript
116114
</div>
117115

118116

119-
## Experienced developers – do you want off the frontend treadmill?
117+
## Powerful for experienced developers
120118

121119
I've seen things you people wouldn't believe. Megabytes of JavaScript on fire in the browser. I watched towers of complex abstractions collapse upon themselves. All those codebases will be lost in time, like tears in rain. Time to let them die.
122120

routes/styles/styles.css

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ html {
3434
overflow-wrap: break-word;
3535
text-rendering: optimizeLegibility;
3636
font-kerning: normal;
37-
scroll-padding-top: 3em;
37+
scroll-padding-top: 1em;
3838
scroll-behavior: smooth;
3939
@media screen and (prefers-reduced-motion: reduce) {
4040
scroll-behavior: auto;

0 commit comments

Comments
 (0)