I wanted to provide some context around what is happening on this page and why it was created, as well as clarify the proposed shift in approach.

Current State & Challenges

At present, much of the league-related functionality is being handled directly through Google Sheets, including both pulling data from Sheets into the site and pushing data back into Sheets via embedded forms. While this approach works, it introduces a few challenges:

• Load performance is impacted by iframed Google Sheets.
• Forms both pull from and push to Google Sheets, which adds complexity and points of failure.
• Google Sheets is currently being used not just for analytics, but also for core league management, which is outside its ideal use case.

It’s also worth noting that, in this setup, WRH is effectively being used as a WordPress installation rather than as a sports management platform, which limits its value.

Proposed Direction

The proposal is to shift core league management into WRH, and reserve Google Sheets primarily for what it does best: internal analytics and reporting.

Under this model:

• Leagues are managed in WRH, including teams, schedules, and score reporting.
• Below, you’ll see two sample leagues in my sandbox installation; the league buttons and pages are being dynamically generated from the WRH Leagues system, not from Google Sheets.
• WRH would handle most of the functionality that is currently being managed in Sheets, with the exception of advanced or custom analytics.

Data Flow Change (Key Improvement)

Instead of:

• pulling league and score data from Google Sheets,

We move to:

• pushing score data from WRH to Google Sheets via a simple reporting form or automation.

This change has several benefits:

• Score reporting becomes more reliable and faster.
• Google Sheets continues to receive the data it needs for analytics.
• The website no longer depends on Google Sheets for real-time operational data.

Practical Outcome

• League pages in WRH would be lightweight and fast.
• The only remaining embedded Google Sheet on league pages would be something like a Playoff Schedule, where it makes sense.
• Score reporting would not rely on a live “pull” from Google Sheets—only a controlled “push.”

Assumptions & Next Steps

Based on my conversation with Ross, we believe that if score data can be pushed directly into Google Sheets, the analytics requirements should be satisfied. That said, this is an assumption, and it’s possible there are analytics needs we haven’t fully accounted for yet.

The intent here is not to remove Google Sheets from the workflow, but to use it more intentionally, while allowing WRH to do what it was designed to do: manage leagues efficiently and reliably.

I’m happy to walk through a concrete example if that would be helpful.