[Bug] Missing `public/` folder in new site

[aswnss-m]

Describe the bug
In the application, when creating a new site using the dedicated "Create New Site" button, the public/ folder is not generated by default. This folder is usually where static assets (images, files, etc.) are stored.

To Reproduce
Steps to reproduce the behavior:

1. Open the application and click on the "Create New Site" button to generate a new site.
2. Navigate to the root directory of the newly created site.
3. Observe that the public/ folder is not generated as part of the initial structure.

Expected behavior
The public/ folder should be automatically generated within the project structure when creating a new site using the "Create New Site" button, allowing users to add static assets without needing to create the folder manually.

Screenshots
Created using the app

Created using create-next-app@rc

Environment:

• OS: [e.g., Windows, macOS, Linux]
• Node.js version [e.g., 18.0.0]
• Framework and version: Next.js 13.x
• DevKit version [e.g., 1.0.0]

Additional context
This issue may cause confusion for developers expecting the public/ folder to be pre-included in newly created sites, as it was in earlier versions of Next.js. A fix or a clarification in the documentation would be helpful.

[AnirudhDaya]

First of all great spotting!

create-next-app@latest

was used to create new project in the case of the app, which does not have public folder.

but

create-next-app@rc

does have a public folder

[AnirudhDaya]

I'm marking this as a feature request as , we can allow users to choose specific versions of flags they want to add when creating projects