Merge marketing site into sites/www

.github/workflows/www.yml

@@ -0,0 +1,70 @@
+name: Marketing site
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - 'sites/www/**'
+      - 'tool/dash_site/**'
+      - 'tool/config/linkcheck-skip-list.txt'
+      - 'pubspec.yaml'
+      - 'pubspec.lock'
+      - 'analysis_options.yaml'
+      - '.github/workflows/www.yml'
+  pull_request:
+    branches:
+      - main
+    paths:
+      - 'sites/www/**'
+      - 'tool/dash_site/**'
+      - 'tool/config/linkcheck-skip-list.txt'
+      - 'pubspec.yaml'
+      - 'pubspec.lock'
+      - 'analysis_options.yaml'
+      - '.github/workflows/www.yml'
+  schedule:
+    - cron: '0 0 * * 0'
+
+permissions: read-all
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+
+jobs:
+  linkcheck:
+    name: Build and check links
+    runs-on: ubuntu-latest
+    if: github.repository == 'flutter/website'
+    timeout-minutes: 30
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
+      - uses: dart-lang/setup-dart@65eb853c7ba17dde3be364c3d2858773e7144260
+        with:
+          sdk: beta
+      - name: Fetch Dart dependencies
+        run: dart pub get
+      - name: Install firebase-tools
+        run: curl -sL https://firebase.tools | bash
+      - name: Build site
+        run: dart run dash_site --site=www build
+      - name: Check for broken Markdown link references
+        run: dart run dash_site --site=www check-link-references
+      - name: Check for broken internal links
+        run: dart run dash_site --site=www check-links
+
+  firebase-validate:
+    name: Validate Firebase configuration
+    runs-on: ubuntu-latest
+    if: github.repository == 'flutter/website'
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd
+      - uses: dart-lang/setup-dart@65eb853c7ba17dde3be364c3d2858773e7144260
+        with:
+          sdk: beta
+      - name: Fetch Dart dependencies
+        run: dart pub get
+      - name: Validate the firebase.json file
+        run: dart run dash_site --site=www verify-firebase-json

AGENTS.md

@@ -7,14 +7,20 @@ content and code in this repository.
 ## Project overview
 
 This repository contains the source code and content for
-the Flutter framework's documentation website.
-It is hosted at `docs.flutter.dev` and shouldn't be confused with
-the marketing site at `flutter.dev` or the API docs at `api.flutter.dev`.
+the Flutter framework's documentation and marketing websites:
 
-The website is statically built and implemented with
+- `docs.flutter.dev`:
+  The Flutter framework's documentation website.
+- `flutter.dev`:
+  Flutter's homepage and marketing website.
+
+The API docs at `api.flutter.dev` are embedded in the Flutter SDK source
+and are maintained in the <https://github.com/flutter/flutter> repository.
+
+The websites are statically built and implemented with
 Dart and the [Jaspr](https://jaspr.site) web framework.
-For loading content, data, and some of its assets,
-it uses [Jaspr Content](https://docs.jaspr.site/content).
+For loading content, data, and some assets,
+they use [Jaspr Content](https://docs.jaspr.site/content).
 
 ### Directory structure
 
@@ -30,29 +36,40 @@ it uses [Jaspr Content](https://docs.jaspr.site/content).
       for the sidenav, glossary, and various indices.
     - `sites/docs/src/_includes/`:
       Liquid partial files written in Markdown.
+  - `sites/www/`:
+    The implementation of flutter.dev,
+    written in Dart using Jaspr and Jaspr Content.
+    - `sites/www/content/`:
+      Markdown-based marketing pages and structured content.
+    - `sites/www/lib/`:
+      Dart source code for the site.
+    - `sites/www/firebase.json`:
+      Firebase Hosting configuration for flutter.dev.
 - `examples/`:
   A pub workspace containing Dart and Flutter code examples,
-  referenced by code excerpts in the Markdown files.
+  referenced by code excerpts in the docs Markdown files.
 - `tool/dash_site/`:
   CLI tool for site development and maintenance.
 
 ## Common commands
 
-While working on the site,
+While working on these sites,
 you might need to run these commands:
 
 ```bash
 # Install or update Dart dependencies:
 dart pub get
 
 # Serve a dev server of the site locally:
-dart run dash_site serve
+dart run dash_site --site=docs serve
+dart run dash_site --site=www serve
 
 # Build a production version of the site:
-dart run dash_site build
+dart run dash_site --site=docs build
+dart run dash_site --site=www build
 
-# Sync code excerpts to Markdown files:
-dart run dash_site refresh-excerpts
+# Sync docs code excerpts to Markdown files:
+dart run dash_site --site=docs refresh-excerpts
 
 # Learn what other commands are available:
 dart run dash_site --help

README.md

@@ -148,9 +148,8 @@ following the instructions in [Get the prerequisites](#get-the-prerequisites).
    This command generates and serves the site on a
    local port that's printed to your terminal.
 
-5. View your changes in the browser by navigating to <http://localhost:8080>.
-
-   Note the port might be different if `8080` is taken.
+5. View your changes in the browser by navigating to
+   the local URL printed to your terminal.
 
 6. Make your changes to the local repo.
 

pubspec.yaml

@@ -10,4 +10,5 @@ workspace:
   - packages/analysis_defaults
   - packages/excerpter
   - sites/docs
+  - sites/www
   - tool/dash_site

sites/www/.agents/rules/jaspr.md

@@ -0,0 +1,117 @@
+---
+trigger: always_on
+---
+
+# Jaspr Project Rules
+
+## Core Principles
+- **Framework**: Use [Jaspr](https://github.com/schultek/jaspr) for all web UI components. Do not use standard Flutter widgets (Container, Column, Row, etc.). 
+- **Elements**: Use HTML-like components provided by Jaspr (`div`, `section`, `h1`, `p`, `img`, `a`, `button`, `span`, etc.).
+
+## Components
+- **Stateless vs Stateful**:
+  - Use `StatelessComponent` for purely presentational components that do not manage local state.
+  - Use `StatefulComponent` only when internal state management (e.g., animations, form input handling) is required.
+- **Client-Side Rendering**: Annotate components with `@client` if they require browser-specific APIs or interactivity that cannot be server-side rendered (SSR).
+
+## Project Structure
+- **Components**: Place reusable UI components in `lib/components/`.
+- **Pages**: Place route-level components in `lib/pages/`.
+
+## Common Patterns
+- **Lists**: Prefer Dart collection-for and collection-if elements over`.map().toList()` to render lists of children.
+- **Conditionals**: Prefer Dart `if` inside the children list over ternary operators for conditional rendering.
+
+## Best Practices
+
+When writing Jaspr components, adhere to these modern syntax rules:
+
+### Component Signature
+Always use the `Component build(BuildContext context)` signature (not `Iterable<Component>` with `yield`).
+
+```dart
+// ✅ Correct
+@override
+Component build(BuildContext context) {
+  return div([...]);
+}
+
+// ❌ Avoid
+@override
+Iterable<Component> build(BuildContext context) sync* {
+  yield div([...]);
+}
+```
+
+### Text Components
+Use the dot-shorthand `.text()` for adding text nodes, which is cleaner than wrapping strings in `text()`.
+
+```dart
+// ✅ Correct
+div([
+  .text('Hello World'),
+])
+
+// ❌ Avoid, Deprecated
+div([
+  text('Hello World'),
+])
+```
+
+### Links and Navigation
+
+Prefer standard `a` tags over `Link` components when you need full control over attributes or are migrating strict HTML.
+
+```dart
+// ✅ Correct
+a(
+  href: '/path',
+  classes: 'my-link',
+  events: {'click': (e) => ...}, // Easy to attach events
+  [.text('Go')]
+)
+```
+
+### Positional Arguments for Children
+
+`div`, `span`, and other container components typically take children as a positional `List<Component>`.
+
+```dart
+// ✅ Correct
+div(classes: 'wrapper', [
+  child1,
+  child2
+])
+
+// ❌ Avoid
+div(classes: 'wrapper', children: [ ... ])
+```
+
+- Use `main_([...])` for rendering a `<main>` element.
+- Use `Component.element(tag: 'xx', children: [...])` for an element that does not have a direct component.
+
+### Using Browser APIs and handling Global/Window Events
+
+Use `import 'package:universal_web/web.dart' as web;` for accessing standard browser APIs (e.g. `window` or `window.document`) when implementing browser-specific logic (location checking, scroll locking).
+
+Use `web.EventStreamProviders` to listen to window-level events in `initState` and cancel stream subscriptions in `dispose`.
+
+```dart
+StreamSubscription? _resizeSubscription;
+
+@override
+void initState() {
+  super.initState();
+  if (kIsWeb) {
+    _resizeSubscription = web.EventStreamProviders.resizeEvent
+        .forTarget(web.window)
+        .listen((_) => setState(() {}));
+  }
+}
+
+@override
+void dispose() {
+  _resizeSubscription?.cancel();
+  super.dispose();
+}
+```