Skip to content

Commit 47132cd

Browse files
authored
chore: adds more requirements and v0 resource (#669)
Signed-off-by: Anthony D. Mays <[email protected]>
1 parent 3ec4746 commit 47132cd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

capstone/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,8 @@ Your project submission must include the following elements:
1010
* Each team member must contribute *at least one* submitted pull request containing working code and tests. See [Lesson 15][lesson-15] for a refresh.
1111
* Write unit tests achieving 70% code coverage (using JaCoCo for Java or Jest for Typescript).
1212
* Must have a working front-end that interacts with a back-end web service to retrieve and persist data.
13-
* Your app must be publicly accessible.
13+
* Your app must be publicly accessible. It is recommended that you use [Vercel](https://vercel.com) or [Fly.io](https://fly.io) to deploy your apps.
1414
* The system must incorporate one third-party API.
15-
* All code must be kept in a public GitHub repository.
1615
* Your repo must include a README with the following elements:
1716
* The team
1817
* Screenshot
@@ -76,6 +75,7 @@ To ensure the timely completion of your project, you will need to complete the f
7675

7776
Here are some links to tools and templates that can help you work together effectively.
7877

78+
* [v0 (chatbot for generating UI and web applications)](https://v0.dev)
7979
* [A Short Guide to Effective Daily Standups (Nave)](https://getnave.com/blog/short-guide-daily-standups/)
8080
* [Team Meeting Notes template (Google Docs)](https://docs.google.com/document/d/1rL-Zm2w0hABuGkIMSPzmXcJHDQxmIeA-mlipt8kDA9E/edit)
8181
* [Crafting Effective User Stories: A Guide to Good and Bad Versions (Visual Paradigm)](https://guides.visual-paradigm.com/crafting-effective-user-stories-a-guide-to-good-and-bad-versions/)

0 commit comments

Comments
 (0)