How ernesthdj/pid works
The tree contains dated PHP course examples and a separate photography-site planning area, but no README. The PHP files appear to demonstrate nested pages and application entry points; their source was not sampled, so relationships between pages or include files cannot be confirmed. The only sampled source is a partial generated DC runtime bundle, which is not enough to establish how it connects to the planning files or PHP examples.
Main entry points: _htdocs/index.php Course root · dir.0/index.php dir.0 page · dir1/index.php dir1 page · dir2/index.php dir2 page
Components 16
PHP course examples
- Course root
Suivit_Cours/pid.20260919/_htdocs/index.php - Root content
Suivit_Cours/pid.20260919/_htdocs/index.content.php - dir.0 page
Suivit_Cours/pid.20260919/_htdocs/dir.0/index.php - dir1 page
Suivit_Cours/pid.20260919/_htdocs/dir1/index.php - dir1 content
Suivit_Cours/pid.20260919/_htdocs/dir1/index.content.php - dir2 page
Suivit_Cours/pid.20260919/_htdocs/dir1/dir2/index.php - page12
Suivit_Cours/pid.20260919/_htdocs/dir1/dir2/page12.php - personne
Suivit_Cours/pid.20260919/_htdocs/dir1/dir2/personne.php - Include example
Suivit_Cours/pid.20260919/_htdocs/dir1/dir2/a_inclure.php - monapp
- application
Suivit_Cours/pid.20260912/application.php - page
Suivit_Cours/pid.20260912/page.php
Site planning
- Image slot
Design/Ernest H. Photography site planning/image-slot.js - iOS frame
Design/Ernest H. Photography site planning/ios-frame.jsx - DC runtime bundle
Design/Ernest H. Photography site planning/support.js
Other components
- Browser
Connections 9
- Browser → Course root: requests
- Browser → dir.0 page: requests
- Browser → dir1 page: requests
- Browser → dir2 page: requests
- Browser → page12: requests
- Browser → personne: requests
- Browser → monapp: requests
- Browser → application: requests
- Browser → page: requests