43 copy revisions

[tylers-username]

Tasks

Beta Give feedback

1. Keep step content as concise as possible - the demo guide is to lead users to experience cool features, not train them on feature usage, to excite them to want to learn more about the product
2. Ensure copy aligns with the purpose of the demo: enable users to experience key features of Upsun - the demo guide is to lead users to experience cool features, not train them on feature usage, to excite them to want to learn more about the product
3. Implement
4. Remove Quick Commands - these are only useful when the CLI demo:start and demo:reset commands are available; let's keep the user focused on the next steps we want them to complete
5. Remove environment status - we are already confirming what has been done in the steps. let's not distract the users.
6. Remove sidebar tests as the content no longer exists
7. Update header test to consider new copy
8. update app.tests.tsx to consider removed sidebar content
9. resources:set should use the minimum values possible

[tylers-username]

@gilzow @GuGuss I cannot assign myself as the reviewer. This branch includes the content that we intend to take to production.

[gilzow]

in all deployed environments, the following correction should be made in the top box:

Welcome to your Upsun Demo Guide project, a Python and Node.js multiapp designed to run on Upsun and teach you about it’s its unique features.

Fixed in commit 40b5174

[gilzow]

in the initial production environment:

This app is the React frontend of your demo project’s production environment, which is associated with the default branch of the repository: main. With it now deployed, we can add features, services, and runtimes from in preview environments - which are actually byte-for-byte copies of production.

Fixed in commit de2f895

[gilzow]

In the deployed staging environment:

This app uses the Upsun-provided environment variable $UPSUNPLATFORM_ENVIRONMENT="staging" to modify the content of this page.

Fixed in commit d9b3050

[gilzow]

FYI: python backend fails to build due to issue with incorrect constraints on the Werkzeug dependency in the upstream Flask repository. The Werkzeug is incorrectly being updated to version 3.0.0 which is incompatible with Flask <3.0.0 where ours is constrained to v2.0.1. We need to pin Werkzeug to v2.2.2 by adding a constraint to backend/requirements.txt:

Werkzeug==2.2.2

[gilzow]

The changes look ok, and I can most intuitively tell which step i'm at in the process as I progress but there are a couple of pieces that are still "broken"

[tylers-username]

Current state of MR.

2.Screen.Recording.2023-10-02.at.6.15.40.PM.mov

[tylers-username]

@gilzow - is there anything left that is critical on your side? would love to get this merged and then we can iterate over post-mvp launch changes in a new MR.

[gilzow]

we need to change git merge to upsun merge since we never actually instruct the user to perform a git merge

[tylers-username]

Think we're all good here.

[Kazanir]

🌞