search

observablehq / framework

A static site generator for data apps, dashboards, reports, and more. Observable Framework combines JavaScript on the front-end for interactive graphics with any language on the back-end for data analysis.
https://observablehq.com/framework/
ISC License
2.57k stars 123 forks source link

Add settings URL to deploy outro #1646

Closed tophtucker closed 2 months ago

tophtucker commented 2 months ago
9FCFBC53-B505-429D-AFBF-C96FE1CDA8A6-676-000A6670FA1700E0
Fil commented 2 months ago

I find this both useful and disturbing (like every time you have two CTAs).

Maybe we could clarify what these settings are about, and put the link a bit above rather than below the app URL.

To review cloud settings: <https://observablehq.com/projects/@observablehq/observable-framework/settings>

[bold]The deployed app is now visible at <https://observablehq-observablecloud.test:5000/observable-framework/>[/bold]
mbostock commented 2 months ago

Agree, not sure we want a dual CTA here. And I don’t think the settings page has the same urgency because you don’t need to change your settings every time you deploy, but you do often want to verify that the deployed app contains what you expect.

Should we have a command you can run that automatically opens either the live app, or the app’s setting page, in the browser?

tophtucker commented 2 months ago

Separate command sounds good! Hm… some relevant tasks (reasons you’d want web settings from CLI) might be:

  1. Opening the page the first time you deploy and the app is created on Observable so you can continue initial configuration
  2. Kicking off a cloud build and viewing logs
  3. Link the app to the repo you’re in (if possible??)

I think we can definitely improve the connection somehow but those all feel different enough that I’ll close this PR. 🙏