trusat / trusat-learn Goto Github PK

We need to codify and document the framework the project shall adopt and follow for making decisions such as merging major code changes, adding new project owners, etc.

When copying the TruSat white paper to the formatting in these docs, a number of words were inadvertently concatenated.

For example, at the top of the Roadmap, the characters "alimitedprototype" should instead read as "a limited prototype."

If someone could scan through and fix these instances, that would be helpful.

-Write instructions for how to add new pages
-Add to bottom of "Updating this documentation page
-Should include screenshots as visual aids for each step

The web has a number of existing resources to help advance the practice of satellite tracking. TruSat would benefit from pointing people towards the best of these resources.

We can provide a list of links, ideally with some mindful curation of th most helpful of the resources, rather than providing an overwhelming list of anything we find on the topic.

The Roadmap page was written before we launched the Catalog in October 2019.

Since then, we have refined perspectives on what initiatives to prioritize in the near-term and medium-term to achieve the high-level outcomes in the roadmap.

It'd be nice to have this updated thinking reflected in the roadmap. References to specific features and sets of features can link to respective issues on github.

We've gotten feedback that the CalSky process times out for people, shutting them out of the site for a period. This isn't ideal for an introductory experience, so let's swap the screenshots and instructions to feature Heavens-Above instead.

We can still include CalSky as an alternate option in the tutorial.

The TruSat docs will be more globally accessible once they've been translated to more languages.

The Docusaurus framework the Learning Hub uses includes extra configuration options for translation and localization of content.

Enabling these options in the UI may help facilitate the localization of TruSat content.

Create a list of ways with the exact steps required (either in the same page or as separate pages.

e.g.:

• updating docs
• submitting bugs
• suggesting features and editing requirements
• spreading the word
• etc

Creating an IOD from an observation would be a cool assignment for a high school science class.

And there are many websites that collect and distribute lesson plans for teachers.

It'd be nice to have a section that addresses the use case of an instructor looking for a lesson plan. If we can translate existing tutorial information into the form of an assignment or lesson plan, that becomes a more practical and shareable artifact for this use case. The same content can also be submitted to popular lesson plan hosting sites, as a way to bring in more student observers to the community.

Create a list of ways to contribute with the exact steps required (with details, eithr on the same page or as separate linked pages).

e.g.:

• updating docs
• submitting bugs
• suggesting features and editing requirements
• promoting the project
• etc