rename to “Framework”; new Getting started tutorial

README.md

@@ -1,4 +1,4 @@
-# Observable CLI
+# Observable Framework
 
 - [Documentation](https://cli.observablehq.com/)
 - [Issues](https://github.com/observablehq/cli/issues)

docs/components.md

@@ -2,7 +2,7 @@
 
 You don’t have to start from scratch: components are reusable pieces of code (functions, themes, snippets, etc.) that make it quicker to update page layout and appearance, and add common page content.
 
-The Observable CLI offers three flavors of components: [layout helpers](#layout-helpers), [Observable Plot snippets](#observable-plot-snippets), and [Observable Inputs](#observable-inputs).
+Observable Framework offers three flavors of components: [layout helpers](#layout-helpers), [Observable Plot snippets](#observable-plot-snippets), and [Observable Inputs](#observable-inputs).
 
 ## Layout helpers
 
@@ -140,4 +140,4 @@ The [radio input](./inputs/radio) prompts a user to select a penguin species:
 const pickSpecies = view(Inputs.radio(["Adelie", "Chinstrap", "Gentoo"], {value: "Gentoo", label: "Penguin species:"}))
 ```
 
-The value of `pickSpecies` (<tt>="${pickSpecies}"</tt>) can then be accessed elsewhere in the page, as a parameter in other computations, and to create interactive charts, tables or text with [inline expressions](./javascript#inline-expressions).
+The value of `pickSpecies` (<code>="${pickSpecies}"</code>) can then be accessed elsewhere in the page, as a parameter in other computations, and to create interactive charts, tables or text with [inline expressions](./javascript#inline-expressions).

docs/contributing.md

@@ -1,6 +1,6 @@
 # Contributing
 
-If you’d like to contribute to the Observable CLI, here’s how. First clone the [git repo](https://github.com/observablehq/cli) and run [Yarn (1.x)](https://classic.yarnpkg.com/lang/en/docs/install/) to install dependencies:
+If you’d like to contribute to Observable Framework, here’s how. First clone the [git repo](https://github.com/observablehq/cli) and run [Yarn (1.x)](https://classic.yarnpkg.com/lang/en/docs/install/) to install dependencies:
 
 ```sh
 git clone [email protected]:observablehq/cli.git
@@ -30,7 +30,7 @@ This creates the `dist` folder. View the site using your preferred web server, s
 http-server dist
 ```
 
-This documentation site is built on GitHub using the Observable CLI; see the [deploy workflow](https://github.com/observablehq/cli/blob/main/.github/workflows/deploy.yml). Please open a pull request if you’d like to contribute to the documentation or to CLI features. Contributors are expected to follow our [code of conduct](https://github.com/observablehq/.github/blob/master/CODE_OF_CONDUCT.md). 🙏
+This documentation site is built on GitHub using Observable Framework; see the [deploy workflow](https://github.com/observablehq/cli/blob/main/.github/workflows/deploy.yml). Please open a pull request if you’d like to contribute. Contributors are expected to follow our [code of conduct](https://github.com/observablehq/.github/blob/master/CODE_OF_CONDUCT.md). 🙏
 
 A test coverage report can be generated with [c8](https://github.com/bcoe/c8), in text and lcov formats, to help you identify which lines of code are not (yet!) covered by tests. Just run:
 
@@ -42,7 +42,7 @@ yarn test:coverage
 
 <div class="note">These instructions are intended for Observable staff.</div>
 
-To release a new version of the CLI, first update the [package.json](https://github.com/observablehq/cli/blob/main/package.json) file by following the standard process for committing code changes:
+To release a new version, first update the [package.json](https://github.com/observablehq/cli/blob/main/package.json) file by following the standard process for committing code changes:
 
 1. Create a new branch.
 2. Edit the `version` field in the [package.json](https://github.com/observablehq/cli/blob/main/package.json) file as desired.

docs/data/forecast.json.js

@@ -0,0 +1,13 @@
+const longitude = -122.47;
+const latitude = 37.80;
+
+async function json(url) {
+  const response = await fetch(url);
+  if (!response.ok) throw new Error(`fetch failed: ${response.status}`);
+  return await response.json();
+}
+
+const station = await json(`https://api.weather.gov/points/${latitude},${longitude}`);
+const forecast = await json(station.properties.forecastHourly);
+
+process.stdout.write(JSON.stringify(forecast));

docs/data/forecast.json.py

@@ -0,0 +1,11 @@
+import json
+import requests
+import sys
+
+longitude = -122.47
+latitude = 37.80
+
+station = requests.get(f"https://api.weather.gov/points/{latitude},{longitude}").json()
+forecast = requests.get(station["properties"]["forecastHourly"]).json()
+
+json.dump(forecast, sys.stdout)