Tell me the directory structure for the php js css html application?

1. Do you use any design pattern? If yes, then the structure of such a project can be found on the Internet (I advise MVC).
2. I usually create in this form.

--- | Public - everything that is available in essence to the user.

------ | Assets - js, css, fonts.

--------- | js

--------- | css

--------- | fonts

------ | views - views from where I attach files. html pages can be connected right there.

--- | Core - the software part. Classes, models and the like.

----- | Classes

--- | Configs - configuration files.

index.php - at the root. All requests here.

It is possible to do simple routing through $ _GET parameters without knowledge of .htaccess and complex design patterns. If you need a simple and fast project, then I am writing it that way. I can throw off the repository with an example, if you're interested.

I wrote once a framework and made such a structure

As for the organization of security, then your application code should be outside the input file so that a умелый человек cannot directly link to the source
Input file public/index.php , code src/
src and public at the same level

More symfony way but can get something for yourself

 ├── app │  ├── config │  └── logs ├── Framework │  ├── Config │  ├── Controller │  ├── Database │  ├── DI │  ├── Event │  ├── Exception │  ├── Helper │  ├── Logger │  ├── Model │  ├── Patterns │  ├── Renderer │  ├── Request │  ├── Response │  ├── Router │  ├── Security │  ├── Services │  ├── Session │  └── Validation │  └── Filter ├── src │  ├── CMS │  │  ├── config │  │  ├── Controller │  │  ├── Migrations │  │  ├── Model │  │  └── views │  └── Shop │  ├── config │  ├── Controller │  ├── Model │  ├── Services │  └── views ├── storage │  └── session └── web ├── css ├── fonts ├── images │  └── uploads ├── js └── uploads