@bostonuniversity/buwp-local 0.7.0 → 0.7.1

package/docs/ARCHITECTURE.md

@@ -442,9 +442,9 @@ Docker's **volume mapping architecture** creates a clean separation:
 │    └── wp-content/              │
 │         └── plugins/            │
 │              └── my-plugin/ ──┐ │  (mapped from Mac)
-│                                │ │
-│  SEPARATED = No conflicts!     │ │
-└────────────────────────────────┴─┘
+│                               │ │
+│  SEPARATED = No conflicts!    │ │
+└───────────────────────────────┴─┘
 ```
 
 **Technical Benefits:**
@@ -459,47 +459,6 @@ Docker's **volume mapping architecture** creates a clean separation:
 
 5. **Safe Testing** - Test breaking changes in WordPress without risk. If something goes wrong, recreate the container—your code was never in danger.
 
-#### Workflow Comparison
-
-**VM Sandbox Workflow:**
-```
-Week 1-3: Develop in VM
-Week 4: Monthly rebuild
-  1. Backup your code manually
-  2. Coordinate with team
-  3. Wait for new VM image
-  4. Restore code manually
-  5. Re-test everything
-  6. Hope nothing broke
-Time lost: 2-4 hours + coordination overhead
-```
-
-**buwp-local Workflow:**
-```
-Anytime: New WordPress version available
-  1. docker pull ghcr.io/bu-ist/buwp:latest
-  2. npx buwp-local start
-  3. Test (your code unchanged)
-Time: 2 minutes
-```
-
-#### Real-World Example
-
-**Scenario:** 6-week plugin development project. WordPress update lands in week 3.
-
-**VM Approach:**
-- Wait for scheduled monthly rebuild (week 4)
-- Backup your work
-- Rebuild overwrites everything
-- Restore and re-test
-- **Impact:** 2-4 hours lost, risk of data loss
-
-**buwp-local Approach:**
-- Pull new image when convenient (any time in week 3-6)
-- Containers recreate with new WordPress version
-- Your code untouched on local filesystem
-- **Impact:** 2 minutes, zero risk
-
 ### Separation of Concerns
 
 This architecture provides clean boundaries:
@@ -516,18 +475,6 @@ This architecture provides clean boundaries:
 
 Updates to WordPress never touch your development code. Updates to your code never require rebuilding WordPress.
 
-### Additional Architectural Benefits
-
-1. **Live Reload** - File changes sync instantly via volume mappings. Save in your editor, refresh browser, see changes.
-
-2. **IDE Integration** - Use any editor (VS Code, PHPStorm, Sublime) with full IDE features (autocomplete, debugging, git integration).
-
-3. **Version Control** - Your code is already on the host filesystem where git lives. No special workflows to commit from inside VMs.
-
-4. **Multiple Projects** - Run multiple projects simultaneously, each with isolated environments. No VM resource conflicts.
-
-5. **Portable Configuration** - Commit `.buwp-local.json` to version control. Teammates get identical environments with one command.
-
 For detailed migration guidance, see [MIGRATION_FROM_VM.md](MIGRATION_FROM_VM.md).
 
 ## Security Model

package/docs/CHANGELOG.md

@@ -5,6 +5,10 @@ All notable changes to buwp-local will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.1]
+
+Documentation only release.
+
 ## [0.7.0]
 
 ### Added

package/docs/MIGRATION_FROM_VM.md

@@ -198,9 +198,6 @@ npx buwp-local start
 ```bash
 # Check Docker Desktop is running
 docker info
-
-# Check port conflicts
-npx buwp-local start --verbose
 ```
 
 ### Code changes not appearing

package/docs/ROADMAP.md

@@ -102,7 +102,7 @@ hostile.remove('127.0.0.1', config.hostname);
 ---
 
 ## Incremental Functional Improvements: v0.6.x
-**Status:** Currently Ongoing
+**Status:** Shipped
 **Focus:** Enhancements based on initial user experience
 
 ### Shipped in v0.6.1
@@ -115,7 +115,7 @@ hostile.remove('127.0.0.1', config.hostname);
 - **Fix issues with spaces in paths**
   - Fix issues with spaces in host paths causing Docker errors
 
-### Planned for v0.6.3
+### Shipped for v0.6.3
 
 - **Basic docs on existing Xdebug features**
   - Quickstart guide for enabling and using Xdebug in containers
@@ -123,10 +123,6 @@ hostile.remove('127.0.0.1', config.hostname);
 - **Volume Mapping pattern guide**
   - Documentation on different volume mapping strategies for various development workflows
 
-### Shipped in v0.6.3
-
-**Focus:** Documentation refinement based on real user patterns
-
 **Key Deliverables:**
 
 1. **Volume Mapping Patterns Guide** ✅
@@ -152,14 +148,12 @@ hostile.remove('127.0.0.1', config.hostname);
 
 **Result:** Documentation now accurately reflects real-world development workflows, making it easier for new users to adopt appropriate patterns.
 
-## Next Phase: v0.7.0 - Developer Experience
+## Next Phase: v0.7.x - Developer Experience
 
-**Status:** Planned  
-**Timeline:** After team onboarding feedback  
+**Status:** Ongoing 
 **Focus:** Ease of use and visibility
 
-### Potential Features
-
+### Shipped in v0.7.0
 - **Docker Image Update Command** 🎯 (Proposed for v0.7.0)
   - **Problem:** Stopping and restarting containers reuses existing images; newer images aren't pulled
   - **Solution:** Add `buwp-local update` command that:
@@ -169,6 +163,11 @@ hostile.remove('127.0.0.1', config.hostname);
   - **Benefit:** Safe, explicit way to apply WordPress/service updates without `destroy`
   - **Implementation:** Wrapper around `docker-compose pull && docker-compose up -d --force-recreate`
 
+### Shipped in v0.7.1
+- **Documentation Improvements**
+
+### Potential Features
+
 - **Database Security**
   - Check database access on db port (e.g. `localhost:3306`)
   - Consider more stringent default database passwords
@@ -226,7 +225,7 @@ Will be informed by feedback from initial small group of users and actual pain p
 
 - **Cross-Platform Support** - Windows WSL2 and Linux credential storage
 - **SSL Certificate Generation** - Local HTTPS with mkcert
-- **Real support for runnning on ports other than 443**
+- **Real support for running on ports other than 443**
 - **Potential GUI from Electron or SwiftUI**
 
 **Note:** Automatic `/etc/hosts` management deferred pending user feedback. See "Lessons Learned" section above for details on the `hostile` library approach.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bostonuniversity/buwp-local",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "description": "Local WordPress development environment for Boston University projects",
   "type": "module",
   "main": "lib/index.js",