-
Notifications
You must be signed in to change notification settings - Fork 724
Open
Description
The instructions for Deno Deploy in the README.md
file still seems to assume Fresh 1, they point to main.ts
.
In general the instructions differ with https://fresh.deno.dev/docs/deployment/deno-deploy and both lack clarification between the new project wizard (which will create a new repository, it seems) and linking an existing GitHub project (which has a different workflow).
This can be confusing for newcomers. Even more confusing when the "New Deploy" changes everything again (slightly), which is even harder to incorporate in current documentation.
Which leads to these questions:
- Should both Deploys get mentioned?
- Or only classic (as it is now)?
- Or should the New Deploy prominently get pushed?
Metadata
Metadata
Assignees
Labels
No labels