WordPress headless CMS for Calaveras Big Trees State Park trail guide data.
bigtrees/
├── data/ # Data files and source materials
│ ├── bigtrees_data.json # Main data file (imported to WordPress)
│ ├── north_grove_trails.json
│ ├── North Grove Guide.pdf
│ └── pdf_full_text.txt
│
├── docs/ # Documentation
│ ├── architecture-plan.md
│ ├── wordpress-setup-guide.md
│ ├── react-setup-guide.md
│ ├── post-meta-vs-acf-plan.md
│ ├── admin-editing-experience.md
│ └── ... (other docs)
│
├── scripts/ # Python extraction scripts
│ ├── explore_pdf.py
│ ├── extract_trails.py
│ ├── find_trail_markers.py
│ └── check_stops_api.py
│
├── wordpress/ # WordPress plugin files
│ ├── bigtrees-cms-plugin.php
│ ├── bigtrees-acf-debug.php
│ └── wordpress-import.php
│
├── frontend/ # Frontend code (future React app)
│ └── types.ts # TypeScript type definitions
│
├── venv/ # Python virtual environment
├── requirements.txt # Python dependencies
└── README.md # This file
- Copy
wordpress/folder contents towp-content/plugins/bigtrees-cms/ - Copy
data/bigtrees_data.jsonto the plugin directory - Activate the plugin in WordPress admin
- Go to Big Trees Import → Import Data
# Activate virtual environment
source venv/bin/activate
# Run extraction scripts
python scripts/extract_trails.py
python scripts/check_stops_api.py- Plugin files are in
wordpress/ - The plugin will automatically find
bigtrees_data.jsonin:- Plugin directory (for deployment)
../data/folder (for development)- Theme directory (fallback)
- Setup Guide:
docs/wordpress-setup-guide.md - Architecture:
docs/architecture-plan.md - Quick Reference:
docs/QUICK-START.md - API Review:
docs/api-review-summary.md
When deploying to WordPress:
- All files in
wordpress/should be in the plugin directory bigtrees_data.jsonshould be in the plugin directory- The plugin will work with files in the plugin directory
For development:
- Files are organized in folders
- Plugin automatically finds files in parent
data/folder