Skip to content

docs: 🏗️ add that web app can be previewed locally#68

Open
lwjohnst86 wants to merge 3 commits into
mainfrom
docs/expand-on-local-preview-of-web-app
Open

docs: 🏗️ add that web app can be previewed locally#68
lwjohnst86 wants to merge 3 commits into
mainfrom
docs/expand-on-local-preview-of-web-app

Conversation

@lwjohnst86

Copy link
Copy Markdown
Member

Description

Related to the discussions in the other PR #53, this adds an explanation about previewing/serving the web app locally.

Needs a thorough review.

Checklist

  • Ran just run-all

@martonvago martonvago left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, just minor comments

Comment thread docs/design/interface/outputs.qmd Outdated
Comment thread docs/design/interface/outputs.qmd Outdated
Comment thread docs/design/interface/outputs.qmd Outdated
@github-project-automation github-project-automation Bot moved this from Todo to In Progress in Product development Jul 10, 2026

@joelostblom joelostblom left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for elaborating on the use of the web app locally! I think it is helpful to have this, although I think we should not make a decision about whether to include custom shortcuts or not until we understand which custom shortcuts are candidates for inclusion and evaluate how helpful they might be (as is also mentioned at the end of the article you linked). You might have some specific shortcuts in mind that are not fit for a web page but there might be others that are, so I think it would help understanding this more before committing to a decision.

For this PR, maybe you can add some of the potential positives of including custom keyboard shortcuts (many similar to what you have for the TUI already) and write that these will be evaluated against the potential drawbacks later when the design is further along and we also take advantage of testing the flow when using the website to inform our decision.

Comment thread docs/design/interface/outputs.qmd Outdated
Comment thread docs/design/interface/outputs.qmd Outdated
Comment thread docs/design/interface/outputs.qmd
Comment thread docs/design/interface/outputs.qmd Outdated
lwjohnst86 and others added 2 commits July 14, 2026 13:27
Co-authored-by: martonvago <57952344+martonvago@users.noreply.github.com>
Co-authored-by: Joel Ostblom <joelostblom@users.noreply.github.com>
@lwjohnst86 lwjohnst86 moved this from In Progress to In Review in Product development Jul 14, 2026
Comment thread docs/design/interface/outputs.qmd
@github-project-automation github-project-automation Bot moved this from In Review to In Progress in Product development Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants