More clearly separate changes corresponding to unreleased invest changes

[emlys]

More clearly separate changes corresponding to unreleased invest changes

[dcdenu4]

It doesn't make sense for most users to see the corresponding UG updates until those invest changes are released.

Yep, definitely agree.

We could also use separate main and release branches like we do with invest, but that might be more work than needed to solve the problem.

This is what I thought our current approach was. My understanding is that the benefit of how things are currently set up is that we can fix things in the Users Guide to better reflect the latest released InVEST version or help clarify something for the latest released InVEST version. I think that has proved useful with forum feedback where someone might point out a confusing pain point that we can quickly update.

the python docs do this better IMO. A dropdown menu at the top defaults to the most recent released version, but you can switch to the dev version or older versions.

That is a nice feature. I think the difference we have is updating the UG for the current version of InVEST. I'm not sure what the Python project does if it finds a significant mistake in it's documentation for a current release... Maybe they let it be as is and punt the fix to the next release (dev (X.Y)).

[emlys]

This is what I thought our current approach was.

I think we have done it in the past and I recently made a release/3.10.2 branch. Happy to keep using that strategy. Just want to make sure we're all in agreement about it, since before I think we let some things get merged into main and published early.