Main Project Brief

Project Vision

Create a comprehensive, community-driven WordPress platform for sharing knowledge about propagating New Zealand native plants, with structured data that can support future mobile applications.

Current Site: https://feaa.info/wordpress/grownative/ Target Audience: Native plant enthusiasts, conservation groups, educators, home gardeners

Project Scope

Phase 1: WordPress Enhancement (Current Project)

Transform the existing placeholder website into a fully functional, community-driven platform with:

  • Structured plant species database
  • User-contributed propagation knowledge
  • Advanced search and filtering
  • Community features for knowledge sharing
  • Content management workflows

Future Consideration: API Development

Design the database structure to support future mobile applications via REST API integration.

Current Site Analysis

What Works Well (Retain):

  • Clear site structure with species-specific URLs using botanical names
  • Standardized page sections (Description, Seed Collection, Germination, Growing On, Planting)
  • External references approach
  • Comment-based community interaction
  • Basic plant listing: https://feaa.info/wordpress/grownative/the-plants/

Areas for Enhancement:

  • Structured data entry instead of free-form content
  • Advanced search and filtering capabilities
  • User registration and contribution workflows
  • Systematic approach to plant information collection
  • Enhanced photo management and galleries

Key Success Factors

  1. Community-Driven Content: Platform must make it easy for experienced growers to share knowledge
  2. Authoritative Information: Balance between community contributions and verified botanical data
  3. Practical Focus: Emphasis on propagation techniques rather than general botanical information
  4. Accessibility: Easy to find specific plant information and growing advice
  5. Future-Proof: Database structure supports expansion to mobile applications

DECISION REQUIRED: Project Priorities

Please rank these priorities (1-5, 1 being highest):

  • [ ] Enhanced plant database with structured fields
  • [ ] User registration and contribution system
  • [ ] Advanced search and filtering
  • [ ] Community features (ratings, success stories)
  • [ ] Automated content population from web research

DECISION REQUIRED: Technical Approach

WordPress Enhancement vs. Custom Development:

Option A: Enhanced WordPress (Recommended)

  • ✅ Build on existing foundation
  • ✅ Faster time to launch
  • ✅ Familiar content management
  • ❌ Some limitations on complex features

Option B: Custom Web Application

  • ✅ Complete control over features
  • ✅ Better mobile app integration
  • ❌ Longer development time
  • ❌ More complex maintenance

Your preference: ________________

DECISION REQUIRED: Content Strategy

Automated Content Population:

  • Should Claude pre-populate basic plant information from web research?
  • Which authoritative sources should be prioritized?
  • How much manual review is acceptable?

Community Content:

  • Moderated vs. immediate publication of user contributions?
  • User reputation/expertise system needed?
  • Anonymous contributions allowed?

DECISION REQUIRED: Timeline and Resources

Development Timeline Preference:

  • [ ] 4-6 weeks (basic functionality)
  • [ ] 8-12 weeks (comprehensive features)
  • [ ] Phased approach with incremental releases

Content Population:

  • [ ] Launch with automated research for [X] species
  • [ ] Launch with current placeholder content only
  • [ ] Hybrid approach: automated basic info + community propagation knowledge

Implementation Documents

This brief is supported by detailed implementation documents:

  1. technical-requirements.md – WordPress plugins, hosting, development environment
  2. database-schema.md – Plant data structure and relationships
  3. user-stories.md – Detailed user scenarios and workflows
  4. content-strategy.md – Approach to populating and managing plant information
  5. development-workflow.md – Step-by-step implementation process

Success Metrics

Community Growth:

  • Number of registered users contributing content
  • Number of plant species with complete propagation information
  • Geographic distribution of contributors

Content Quality:

  • Percentage of plants with complete propagation guides
  • User ratings of information usefulness
  • External citations and references

Platform Usage:

  • Return visitor percentage
  • Time spent on plant species pages
  • Search success rates

Risk Mitigation

Technical Risks:

  • WordPress limitations → Modular approach allows migration to custom platform
  • Performance issues → Caching and optimization strategies
  • Security concerns → Regular updates and monitoring

Content Risks:

  • Insufficient community participation → Seed with researched content
  • Information accuracy → Expert review process
  • Copyright violations → Clear attribution and fair use guidelines

Next Steps

  1. Review and refine this brief with stakeholder input
  2. Make key decisions marked above
  3. Review supporting documentation (technical-requirements.md, etc.)
  4. Finalize project scope and timeline
  5. Begin development environment setup

Document Status: Draft for Review Last Updated: [Current Date] Review Required By: [Your Decision]