Rename pages to routes now that Api Routes are a thing

[ashconnell]

Feature request

Is your feature request related to a problem? Please describe.

Two overarching related issues:

1. The directory pages no longer makes sense now that it contains Api Routes. These aren't pages.
2. The name pages is a convention generally used in other frameworks to denote a place where top level UI components and accompanying files such as styles, tests, stores or state live.

Describe the solution you'd like

With the addition of Api Routes, it makes much more sense to consider renaming this from pages to routes. This has been requested multiple times before but mostly this was before Api Routes were introduced.

Consequently, this also allows developers to continue using the pages convention to contain top level UI components and related files all in one place.

• src/routes/api/**/*.js: api routes
• src/routes/**/*.js: exports the relevent page component from src/pages
• src/pages: contains one folder per page component along with it's store/state and styles
• src/components: re-usable components

Describe alternatives you've considered

• src/pages/api/**/*.js: api routes
• src/pages/**/*.js: exports the relevent screen component from src/screens
• src/screens: contains one folder per screen component with state and style files
• src/components: re-usable components

This structure trips me and other developers up every single time:

• When you want to edit an Api Route is this in pages or screens? None seem relevent to "Api Routes".
• When you want to edit the UI for a page is this in pages or screens? Pages seems most relevent but this is wrong.