Update ESO docs

[ashleythomasbarnes]

Hey!

I plan to make some updates to the astroquery.eso docs (tagging @juanmcloaiza).

Is it a preference to have the docs in a flat structure page (as is now), or with heierarchy like with MAST? I can see the benefits of having either, particularly for the latter when we add more functionality.

-- Ash

[keflavich]

I'm happy with either approach. As it gets longer, hierarchical makes sense to me. @bsipocz , opinions?

[bsipocz]

Same opinion here, if it's gets longer a bit of hierarchy could make sense, but I would also say that one big page has the potential benefit of easier searchability.

(Just a bit of background: the mast module is very much an odd one; they don't follow the common API and has a lot of custom and non VO things. So using it for any generic template and guidance is not encouraged.)

[ashleythomasbarnes]

Would you like me to draft a PR for the docs in a hierarchy format and see what you think?

[ashleythomasbarnes]

I made a little example of what this could look like in a fork here - https://github.com/ashleythomasbarnes/astroquery/tree/develop-docs/docs/eso

[keflavich]

Could you link to a rendered version?

One comment: The WDB (Web DataBase) API is being deprecated and replaced by TAP (Table Access Protocol), should be edited to show dates. The present-tense will probably never be correct.

[bsipocz]

The WDB (Web DataBase) API is being deprecated and replaced by TAP (Table Access Protocol),

That reminds me to make a dev release -- not sure if it help or not, but it's certainly easier to install that way.

[ashleythomasbarnes]

I think I can do that... can you unzip and open this? This should contain the changes to the eso docs from the branch above.

astroquery-docs-html.zip

[keflavich]

This seems a little more granular than I would expect, but I don't have any objection; probably several other modules could do with this level of added structure.