Phase 1: Mobile Image Workflow (Pixel & Google Photos)
BLUF
Objective: Secure a high-velocity visual pipeline by ensuring all assets are “web-ready” before reaching the server. This protocol prevents upload errors and layout fragmentation by standardizing cropping and file sizes at the source.
Fast Facts
- Primary Tool: Google Pixel Camera (Source).
- Editor: Google Photos (Optimization).
- Hero Ratio: 16:9 (Horizontal headers).
- Body Ratio: 4:3 or 1:1 (Standard content).
- File Limit: Must be < 5MB to ensure rapid server ingestion.
The Deep Dive
1. Capture Protocol
Initiate the workflow using the Pixel Camera. Shoot in default modes to capture maximum data, but keep the final framing in mind.
- Orientation: Shoot horizontal for landscapes, vertical for portraits (but be ready to crop).
- Lighting: Trust the Pixel’s computational photography, but aim for even natural light where possible.
2. The Google Photos Edit
Never upload raw. All images must pass through the Google Photos Editor “sanitation” station.
- Crop: This is the most critical step for Blocksy compatibility.
- Heroes: Lock crop to 16:9.
- Gallery: Lock crop to 4:3.
- Adjust: Use Auto-enhance to balance shadows and highlights instantly.
- Resize: Verify file size is reasonable. High-res allows for zooming, but web-ready means optimized.
3. Ingestion (Upload)
Transfer assets to the WordPress Dashboard immediately.
- Batch: Navigate to
Media > Add Newto bulk upload edited sets. - Direct: Insert strictly relevant images directly into the post using the Image Block.
By The Numbers
| Metric | Raw Capture | Web-Ready Asset |
|---|---|---|
| Aspect Ratio | Variable / Unconstrained | 16:9 (Hero) / 4:3 (Body) |
| File Size | 10MB – 15MB+ | < 5MB |
| Lighting | Variable | Auto-Enhanced |
| Destination | Cloud Backup | WordPress Media Library |
Context/Backstory
- The Problem: Raw uploads frequently cause HTTP errors or “crunching” timeouts on mobile networks.
- The Risk: Inconsistent aspect ratios break the grid layout in Blocksy, creating jagged gallery lines.
- The Fix: Pre-processing in Google Photos ensures that WordPress only receives standardized, optimized data.
What’s Next
- [ ] Capture: Shoot a test batch of 5 images using the Pixel.
- [ ] Crop: Open Google Photos and apply 16:9 crop to the best “Hero” candidate.
- [ ] Optimize: Apply Auto-enhance to the batch.
- [ ] Upload: Log into WP Admin on mobile and test the
Add Newmedia function.