From aa6dd2a31ebe06a597d4e55ebcb3f443158e4105 Mon Sep 17 00:00:00 2001
From: Guillem Arias
Brisa mixes ideas from React's "Server Actions" and HTMX
concepts. With Brisa, you can handle all browser events on the
- server, such as forms, click events, etc. In addition, we offer
- some extra HTML attributes to manage debounces, optimistic
- updates, etc.
+ server, such as forms, click events and more. In addition, we
+ offer extra HTML attributes to manage debounces, optimistic
+ updates, among other things.
- The idea is that if you want you can create a SPA without Web
- Components, only with the weight of the Brisa RPC to make the
- connection with the server.
+ You can create a SPA without Web Components, with just the payload
+ of the Brisa RPC to make the connection with the server.
- Brisa has a built-in internationalization (i18n) support that
- allows you to translate your pages and routing,
- carrying only the translations you consume.
+ Brisa has built-in internationalization support that allows you to{' '}
+ translate your pages and routes, loading only the
+ translations you consume.
- Brisa allows you to build web applications that can be easily
- converted to native applications for Android, iOS,
- and desktop. It's full integrated with Tauri.
+ Brisa can also be used with Tauri, which allows you to build web
+ applications that can be easily converted to native applications
+ for Android, iOS, and desktop.
- Brisa's mission is to unify the both worlds (server and client)
- using the Web Platform. One key feature is the ease with which{' '}
- Web Components can be used, utilizing{' '}
+ Brisa's mission is to unify server and client using the Web
+ Platform. Web Components can easily be used, using{' '}
Declarative Shadow DOM and signals to enhance your
workflow in conjunction with Server Actions.
- We bring ideas from the Web to the server. You can{' '}
+ We bring concepts from the web to the server. You can{' '}
capture browser events on the server, such as forms, click
- events, Web Components events, etc. And you can propagate them
- through your server components.
+ events, Web Components events and others. They are progapated
+ through to your server components.
- It also streams Hypermedia over the wire during navigation
- and Server Actions, utilizing HTTP in the way it was originally
- intended. This is closely connected with Web Components because
- they are part of the DOM, their attributes are updated, and
- signals react to these changes.
+ Brisa also streams Hypermedia over the wire during
+ navigation and Server Actions, utilizing HTTP in the way it was
+ originally intended. This is closely connected with Web
+ Components, because they are part of the DOM, their attributes are
+ updated, and signals react to these changes.
- That said, it should be clarified that although we support Web
- Components, you can create a MPA like a{' '}
- SPA without using any Web Component, the grace is that you
+ With that said, it should be clarified that although we support
+ Web Components, you can create a MPA like a{' '}
+ SPA without using any Web Component, the trick is that you
only add a Web Component when you need to touch the Web Platform
or when a user interaction doesn't require the server.
π Full i18n support
π± Multi-platform
π€ Web Platform Framework?
- Brisa is an open-source project, and we welcome contributions from - the community. We have a T-shirt gift for the first - contributors who help us improve the framework. + Brisa is an open-source projec, and is backed by contributions + from the community. We will send a T-shirt gift to the + first contributors who help us improve the framework.
Brisa pages are dynamically server-rendered JSX components, so
there's zero JavaScript shipped to the browser{' '}
@@ -133,12 +133,12 @@ export default function Homepage() {
In Brisa everything by default runs only on the server, except the{' '}
-
Brisa mixes ideas from React's "Server Actions" and HTMX
concepts. With Brisa, you can handle all browser events on the
@@ -183,11 +183,11 @@ export default function Homepage() {
Brisa has built-in internationalization support that allows you to{' '}
- translate your pages and routes, loading only the
- translations you consume.
+ translate your pages and routes, while downloading
+ only the used translations.
Brisa can also be used with Tauri, which allows you to build web
applications that can be easily converted to native applications
@@ -231,7 +231,7 @@ export default function Homepage() {
Brisa's mission is to unify server and client using the Web
Platform. Web Components can easily be used, using{' '}
@@ -303,7 +303,7 @@ export default function Homepage() {
Brisa is an open-source projec, and is backed by contributions
from the community. We will send a T-shirt gift to the
@@ -335,7 +335,7 @@ export default function Homepage() {
Learn more about Brisa by reading the{' '}
@@ -345,7 +345,7 @@ export default function Homepage() {
Take a look at our{' '}
From 6dccc7a7f7af518f0ffcc5e678bc52fbf42f8769 Mon Sep 17 00:00:00 2001
From: Guillem Arias
- Build web applications with speed and{' '}
+ Build web applications with speed and{" "}
simplicity
- Brisa pages are dynamically server-rendered JSX components, so
- there's zero JavaScript shipped to the browser{' '}
+ Brisa pages are dynamically server-rendered JSX components, with zero JavaScript shipped to the browser{" "}
by default.
Simple to write; fast to run.
- In Brisa everything by default runs only on the server, except the{' '}
-
- Brisa has built-in internationalization support that allows you to{' '}
+ Brisa has built-in internationalization support that allows you to{" "}
translate your pages and routes, while downloading
only the used translations.
Brisa's mission is to unify server and client using the Web
- Platform. Web Components can easily be used, using{' '}
+ Platform. Web Components can easily be used, using{" "}
Declarative Shadow DOM and signals to enhance your
workflow in conjunction with Server Actions.
- We bring concepts from the web to the server. You can{' '}
+ We bring concepts from the web to the server. You can{" "}
capture browser events on the server, such as forms, click
events, Web Components events and others. They are progapated
through to your server components.
@@ -256,7 +255,7 @@ export default function Homepage() {
With that said, it should be clarified that although we support
- Web Components, you can create a MPA like a{' '}
+ Web Components, you can create a MPA like a{" "}
SPA without using any Web Component, the trick is that you
only add a Web Component when you need to touch the Web Platform
or when a user interaction doesn't require the server.
@@ -266,7 +265,7 @@ export default function Homepage() {
Brisa's vision is to become the standard for modern web
development, offering developers a unified platform that
simplifies the creation of high-performance applications from
- server to client. We focus on maximizing efficiency by{' '}
+ server to client. We focus on maximizing efficiency by{" "}
minimizing the client-side footprint and enabling
developers to build scalable, cross-platform applications that
fully leverage the web's native capabilities. We aim to empower
@@ -276,9 +275,9 @@ export default function Homepage() {
for future development.
- Learn more about Brisa by reading the{' '}
+ Learn more about Brisa by reading the{" "}
Documentation
.
- Take a look at our{' '}
+ Take a look at our{" "}
Open Collective
- {' '}
- that we have just opened.{' '}
+ {" "}
+ that we have just opened.{" "}
- Build web applications with speed and{" "}
- simplicity
+ Build web applications with speed and simplicity
- Brisa pages are dynamically server-rendered JSX components, with zero JavaScript shipped to the browser{" "}
- by default.
+ Brisa pages are dynamically server-rendered JSX components, with{' '}
+ zero JavaScript shipped to the browser by default.
Simple to write; fast to run.
- In Brisa everything runs only on the server by default, except
- the
Brisa mixes ideas from React's "Server Actions" and HTMX
concepts. With Brisa, you can handle all browser events on the
@@ -184,7 +183,7 @@ export default function Homepage() {
- Brisa has built-in internationalization support that allows you to{" "}
+ Brisa has built-in internationalization support that allows you to{' '}
translate your pages and routes, while downloading
only the used translations.
Brisa's mission is to unify server and client using the Web
- Platform. Web Components can easily be used, using{" "}
+ Platform. Web Components can easily be used, using{' '}
Declarative Shadow DOM and signals to enhance your
workflow in conjunction with Server Actions.
- We bring concepts from the web to the server. You can{" "}
+ We bring concepts from the web to the server. You can{' '}
capture browser events on the server, such as forms, click
events, Web Components events and others. They are progapated
through to your server components.
@@ -255,7 +254,7 @@ export default function Homepage() {
With that said, it should be clarified that although we support
- Web Components, you can create a MPA like a{" "}
+ Web Components, you can create a MPA like a{' '}
SPA without using any Web Component, the trick is that you
only add a Web Component when you need to touch the Web Platform
or when a user interaction doesn't require the server.
@@ -265,7 +264,7 @@ export default function Homepage() {
Brisa's vision is to become the standard for modern web
development, offering developers a unified platform that
simplifies the creation of high-performance applications from
- server to client. We focus on maximizing efficiency by{" "}
+ server to client. We focus on maximizing efficiency by{' '}
minimizing the client-side footprint and enabling
developers to build scalable, cross-platform applications that
fully leverage the web's native capabilities. We aim to empower
@@ -275,9 +274,9 @@ export default function Homepage() {
for future development.
- Learn more about Brisa by reading the{" "}
+ Learn more about Brisa by reading the{' '}
Documentation
.
- Take a look at our{" "}
+ Take a look at our{' '}
Open Collective
- {" "}
- that we have just opened.{" "}
+ {' '}
+ that we have just opened.{' '}
- Brisa pages are dynamically server-rendered JSX components, with{' '}
+ Brisa pages are dynamically server-rendered JSX components, with{" "}
zero JavaScript shipped to the browser by default.
Simple to write; fast to run.
- In Brisa everything runs only on the server by default, except the{' '}
+ In Brisa everything runs only on the server by default, except the{" "}
Brisa mixes ideas from React's "Server Actions" and HTMX
concepts. With Brisa, you can handle all browser events on the
@@ -181,11 +195,14 @@ export default function Homepage() {
- Brisa has built-in internationalization support that allows you to{' '}
- translate your pages and routes, while downloading
- only the used translations.
+ Brisa has built-in internationalization support that allows you to{" "}
+ translate your pages and routes, while downloading only the
+ used translations.
Brisa can also be used with Tauri, which allows you to build web
applications that can be easily converted to native applications
@@ -232,13 +252,13 @@ export default function Homepage() {
Brisa's mission is to unify server and client using the Web
- Platform. Web Components can easily be used, using{' '}
+ Platform. Web Components can easily be used, using{" "}
Declarative Shadow DOM and signals to enhance your
workflow in conjunction with Server Actions.
- We bring concepts from the web to the server. You can{' '}
+ We bring concepts from the web to the server. You can{" "}
capture browser events on the server, such as forms, click
events, Web Components events and others. They are progapated
through to your server components.
@@ -254,7 +274,7 @@ export default function Homepage() {
With that said, it should be clarified that although we support
- Web Components, you can create a MPA like a{' '}
+ Web Components, you can create a MPA like a{" "}
SPA without using any Web Component, the trick is that you
only add a Web Component when you need to touch the Web Platform
or when a user interaction doesn't require the server.
@@ -264,7 +284,7 @@ export default function Homepage() {
Brisa's vision is to become the standard for modern web
development, offering developers a unified platform that
simplifies the creation of high-performance applications from
- server to client. We focus on maximizing efficiency by{' '}
+ server to client. We focus on maximizing efficiency by{" "}
minimizing the client-side footprint and enabling
developers to build scalable, cross-platform applications that
fully leverage the web's native capabilities. We aim to empower
@@ -274,9 +294,9 @@ export default function Homepage() {
for future development.
- Learn more about Brisa by reading the{' '}
+ Learn more about Brisa by reading the{" "}
Documentation
.
- Take a look at our{' '}
+ Take a look at our{" "}
Open Collective
- {' '}
- that we have just opened.{' '}
+ {" "}
+ that we have just opened.{" "}
ποΈ Web Component island-based
+ Web Component island-based
src/web-components
folder that also runs on the
+ src/web-components
folder, which always run on the
client. Web components are rendered on the server (SSR) and
- hydrated on the client using native Web APIs, as they are
+ hydrated on the client using native Web APIs, where they are
transformed into Web Components with Signals.
π² Browser-events on Server
+ Browser-events on Server
π Full i18n support
+ Full i18n support
π± Multi-platform
+ Multi-platform
π€ Web Platform Framework?
+ What does Web Platform Framework mean?
π Gift to contributors
+ Gift to contributors
π Documentation
+ Documentation
π Sponsors
+ Sponsors
The Web Platform Framework
Build fast apps fast
Web Component island-based
src/web-components
folder, which always run on the
- client. Web components are rendered on the server (SSR) and
- hydrated on the client using native Web APIs, where they are
+ In Brisa everything runs only on the server by default, except
+ the src/web-components
folder, which always run on
+ the client. Web components are rendered on the server (SSR)
+ and hydrated on the client using native Web APIs, where they are
transformed into Web Components with Signals.
Full i18n support
What does Web Platform Framework mean?
Documentation
Sponsors
The Web Platform Framework
Build fast apps fast
Web Component island-based
src/web-components
folder, which always run on
- the client. Web components are rendered on the server (SSR)
- and hydrated on the client using native Web APIs, where they are
+ In Brisa everything runs only on the server by default, except the{' '}
+ src/web-components
folder, which always run on the
+ client. Web components are rendered on the server (SSR) and
+ hydrated on the client using native Web APIs, where they are
transformed into Web Components with Signals.
Browser-events on Server
+ Browser-events on the server
Full i18n support
What does Web Platform Framework mean?
Documentation
Sponsors
Build fast apps fast
+
+
Web Component island-based
+
+
src/web-components
folder, which always run on the
client. Web components are rendered on the server (SSR) and
hydrated on the client using native Web APIs, where they are
@@ -152,7 +163,10 @@ export default function Homepage() {
Browser-events on the server
+
+
Full i18n support
+
+
Multi-platform
+
+
What does Web Platform Framework mean?
Documentation
Sponsors