You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/portal/llms.txt
+27-3Lines changed: 27 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,34 @@
1
1
# Neo.mjs Platform
2
2
3
-
> Neo.mjs is not a library, but a comprehensive web platform and a new operating system for the web, with over 1000 files and 130,000 lines of code. It is architected for AI collaboration from the ground up, featuring three dedicated Model Context Protocol (MCP) servers. It reimagines web development from first principles, treating the browser as a distributed computing environment, not a single-threaded document renderer.
3
+
> Neo.mjs is not a library, but a comprehensive web platform and a new operating system for the web, with over 1000
4
+
> files and 130,000 lines of code. It is architected for AI collaboration from the ground up, featuring three dedicated
5
+
> Model Context Protocol (MCP) servers. It reimagines web development from first principles, treating the browser as a
6
+
> distributed computing environment, not a single-threaded document renderer.
4
7
>
5
-
> The core of Neo.mjs is its truly multi-threaded architecture which moves all application logic, state management, and data processing off the main thread. This ensures a "jank-free" user experience where the UI remains perfectly responsive, regardless of the workload. The platform provides a holistic, managed environment with operational guarantees, a unified class config system for declaratively describing entire component trees, and critical operational primitives like multi-window state. It includes an enterprise-grade component library.
8
+
> The core of Neo.mjs is its truly multi-threaded architecture which moves all application logic, state management, and
9
+
> data processing off the main thread. This ensures a "jank-free" user experience where the UI remains perfectly
10
+
> responsive, regardless of the workload. The platform provides a holistic, managed environment with operational
11
+
> guarantees, a unified class config system for declaratively describing entire component trees, and critical operational
12
+
> primitives like multi-window state. It includes an enterprise-grade component library.
6
13
>
7
-
> The developer experience is revolutionary and future-proof, featuring a zero-builds development mode that is 100% based on web standards. This eliminates the frustrating abstraction layer of bundlers and transpilers and ensures that applications evolve with the web platform itself.
14
+
> The developer experience is revolutionary and future-proof, featuring a zero-builds development mode that is 100% based
15
+
> on web standards. This eliminates the frustrating abstraction layer of bundlers and transpilers and ensures that
16
+
> applications evolve with the web platform itself.
17
+
18
+
Neo.mjs uniquely deploys each application and example in four equivalent environments, each serving identical
19
+
functionality through different code delivery methods: development mode (zero-builds), dist/development (bundled,
20
+
unminified), dist/esm (native ES modules, optimized), and dist/production (bundled, minified).
21
+
22
+
The URLs listed below use the development mode paths (e.g., /apps/ or /examples/), representing the zero-builds,
23
+
browser-native version that embodies Neo.mjs's core philosophy. To access any application in a different environment,
24
+
simply prefix the path with /dist/development/, /dist/esm/, or /dist/production/.
25
+
26
+
For example, the Portal app is available at all four environment URLs, plus a fifth version mapped to the domain root:
Copy file name to clipboardExpand all lines: buildScripts/generateSeoFiles.mjs
+27-3Lines changed: 27 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -329,11 +329,35 @@ export async function getLlmsTxt(options={}) {
329
329
330
330
letcontent=`# Neo.mjs Platform
331
331
332
-
> Neo.mjs is not a library, but a comprehensive web platform and a new operating system for the web, with over 1000 files and 130,000 lines of code. It is architected for AI collaboration from the ground up, featuring three dedicated Model Context Protocol (MCP) servers. It reimagines web development from first principles, treating the browser as a distributed computing environment, not a single-threaded document renderer.
332
+
> Neo.mjs is not a library, but a comprehensive web platform and a new operating system for the web, with over 1000
333
+
> files and 130,000 lines of code. It is architected for AI collaboration from the ground up, featuring three dedicated
334
+
> Model Context Protocol (MCP) servers. It reimagines web development from first principles, treating the browser as a
335
+
> distributed computing environment, not a single-threaded document renderer.
333
336
>
334
-
> The core of Neo.mjs is its truly multi-threaded architecture which moves all application logic, state management, and data processing off the main thread. This ensures a "jank-free" user experience where the UI remains perfectly responsive, regardless of the workload. The platform provides a holistic, managed environment with operational guarantees, a unified class config system for declaratively describing entire component trees, and critical operational primitives like multi-window state. It includes an enterprise-grade component library.
337
+
> The core of Neo.mjs is its truly multi-threaded architecture which moves all application logic, state management, and
338
+
> data processing off the main thread. This ensures a "jank-free" user experience where the UI remains perfectly
339
+
> responsive, regardless of the workload. The platform provides a holistic, managed environment with operational
340
+
> guarantees, a unified class config system for declaratively describing entire component trees, and critical operational
341
+
> primitives like multi-window state. It includes an enterprise-grade component library.
335
342
>
336
-
> The developer experience is revolutionary and future-proof, featuring a zero-builds development mode that is 100% based on web standards. This eliminates the frustrating abstraction layer of bundlers and transpilers and ensures that applications evolve with the web platform itself.
343
+
> The developer experience is revolutionary and future-proof, featuring a zero-builds development mode that is 100% based
344
+
> on web standards. This eliminates the frustrating abstraction layer of bundlers and transpilers and ensures that
345
+
> applications evolve with the web platform itself.
346
+
347
+
Neo.mjs uniquely deploys each application and example in four equivalent environments, each serving identical
348
+
functionality through different code delivery methods: development mode (zero-builds), dist/development (bundled,
349
+
unminified), dist/esm (native ES modules, optimized), and dist/production (bundled, minified).
350
+
351
+
The URLs listed below use the development mode paths (e.g., /apps/ or /examples/), representing the zero-builds,
352
+
browser-native version that embodies Neo.mjs's core philosophy. To access any application in a different environment,
353
+
simply prefix the path with /dist/development/, /dist/esm/, or /dist/production/.
354
+
355
+
For example, the Portal app is available at all four environment URLs, plus a fifth version mapped to the domain root:
0 commit comments