Seeking Recommendations for Optimizing Site Structure (Image-heavy Hugo Site)

support
1

I’m reviewing my camera club’s Hugo site, which was originally built several years ago, and I’m concerned the organizational structure may be suboptimal.

The site includes standard club information (events, workshops, news, contact details) but also prominently features member photography. Currently:

  • Each competition gets a new subdirectory under content/competitions
  • Competition pages display images + results tables
  • Image filenames encode metadata (title, author, score, level)
  • These images are reused in two key ways:
    1. Frontpage carousel (displays latest competition images)
    2. Member profile pages (images grouped by member)

My concerns:

  1. The competitions directory stores all images, yet they’re used site-wide
  2. Growing repository size due to image storage (not critical but notable)

Potential solutions I’ve considered:

  • Moving images to assets instead of content
  • External image storage with a structured data approach (e.g., CSVs in data)

I’m open to a complete rebuild if needed. Given Hugo’s current capabilities, what would be the most maintainable approach? Particularly interested in:

  • Optimal directory structure for mixed content/assets
  • Best practices for cross-referencing images
  • Scalability considerations

Thanks in advance for your expertise!