Closed riverma closed 1 year ago
Something like this, where to top expandable area would link to resources described in more detail at the bottom:
We'd have to of course adjust the contents based on each "guide".
Thoughts @jpl-jengelke @jpl-btlunsfo @tariqksoliman @darth-pr?
I would be good to have a video at the top of the guide, so that new projects can get a quick overview in video form.
That's a great idea @galenatjpl - to have video introductions in general. In fact, you made me think that the front page of SLIM (https://nasa-ammos.github.io/slim/) currently explains more about SLIM than points people to the key best practice guides. Maybe a video or quick pointer sooner on the main page would help.
What about a faceted search approach where tags are utilized to label and organize specific process improvement solutions?
Pros:
Cons:
https://github.com/itemsapi/itemsjs (client-side only!)
I've performed some trade-analysis of key features desired and found the following:
Based on the above - I'd recommend we consider Docusaurus and propose a PR to draft a vision of the site for community review.
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
As mentioned by @tariqksoliman et al in https://github.com/NASA-AMMOS/slim/discussions/36 as well as other discussions with folks like @darth-pr a few months back, the SLIM best practice guides are a bit complex to sift through for new folks. They have quite a few pages to go through and that adds complexity.
Moreover, the prime interest in users of SLIM so far has tended to be Starter Kits, which are a bit buried in the documentation.
Describe the feature request
Let's try and simply the organization / structure of the SLIM best practice guides.
Right now, for example the "Documentation Guide" has the following structure:
Can we simplify the above to something more interactive and use case oriented? RETYPE has a feature called "stacked panels" which we could leverage as a set of initial questions for pointing people to specific resources we're offering.
Per @tariqksoliman's suggestion, I'm thinking we simplify the whole best practice guide structure to the following only:
Open to other ideas!