sdsc-ordes / sdsc-ordes/technical-presentation

Shorten the list make it fit more for beginner?

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
2
Forks
3
PR merge metrics
No merged PRs in 30d

Description

https://github.com/sdsc-ordes/technical-presentation/blob/2347ae8eaf8df7e82e2446beb1fa9abcc88faad4/src/presentations/part-1/includes/links.md?plain=1#L17-L38

I feel it can be a bit overwhelming for audiences with too many learning resources.
I believe this is the slide people what to take a picture (if it is a in person presentation).

I'd recommend to have three block in this slide

  1. get started: The official learning reference as the first one is super nice! I like it. Rust Book/rust by example/rustling are all linked from this link maybe put them in this block.
  2. then show the path on how potentially can become fluent in rust. The path I found worth to check is https://corrode.dev/blog/rust-learning-resources-2025/
  3. A link that link to the collection of extra materials that we can keep on adding and updating other learning materials.

Maybe remove std library link, it is important but it will become natural when get more into rust. (could mention that rust has a very nice std lib with a lot of explanation, that any modern IDE can easily access it)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with src/presentations/part-1/includes/links.md, especially lines 17-38, and review how this resource list appears in the presentation. Organize the links into getting started, a Rust learning path, and extra materials, while deciding whether the standard-library link belongs on the slide. Done means the slide is shorter, clearer for beginners, and still points audiences to the broader resources.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
content, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.