Turn Wiki for Repo into User Guide

[egrace479]

Andromeda needs a User Guide!

We should describe the project:

• What Andromeda is compared to the data fetching.
• Data limitations (starts getting crowded as data point numbers increase, especially with images).
• What is QUEST?
• Different versions/releases of Andromeda (eg., QUEST 2023, latlonCover, Quest 2024) with descriptions and links to that particular version.
• Why some columns might be dropped and what to do about it (eg., Inform users why columns are excluded #68)
• Fetch data information:
  • latlonCover info (including eg., Improve land cover big and small column documentation #71)
  • SatRGB and general extra info (upcoming).

[egrace479]

As discussed here, this will also serve as our general documentation, so for admin use as well. To this point, it will also allow us to record our prior configurations for others setting up their own instance or ourselves in case we wish to return to them for some reason.

[egrace479]

Once this is properly set up, we'll want to add links to the documentation from the README in the repo and in the HF repo:

• Link to Docs in GH README
• Link to Docs in HF README

[johnbradley]

Let's add a link from the App to the documentation too.

[egrace479]

Let's add a link from the App to the documentation too.

As in this note on the GH README?

For instructions on building and running the Docker container see Developing with Docker.

[johnbradley]

No. Right now this is the main Andromeda screen running on huggingface:

My thought is users might visit the page and not realize we have a user guide. So my suggestion is to add a link to this page that opens the User Guide section related to user interaction.

[egrace479]

Ah, like with the data dashboard link to documentation. That seems like a good idea, though we still need to write most of the user guide.

[egrace479]

Thoughts on organization of our user/admin guide:

• Home page can give overview of Andromeda
• QUEST page to discuss what QUEST is (sections for 2023, 2024, and on to the future). This could focus on descriptions, then point to appropriate Prior Configurations for more information on the technical details.
• GUI-type page? Something to cover the limitations of space and similar.
• Page with more details on Andromeda and the implementation:
  • Cover things like why some columns might be dropped, general column requirements.
• Fetch data page:
  • Options for getting data
  • Tools that can be/are applied (latlonCover & SatRGB)

[egrace479]

@johnbradley, think we should establish MkDocs documentation instead of keeping it in the wiki?