Skip to content

doc/guides: Add Getting Started guide #21436

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 29, 2025

Conversation

AnnsAnns
Copy link
Contributor

@AnnsAnns AnnsAnns commented Apr 24, 2025

Contribution description

This is the initial part of the three part tutorial introduction PR-chain. The goal of this very initial PR is to set the foundation and also adapt the great tutorial that was already hidden within the doc folder (The Windows WSL tutorial) to be more of a general getting started tutorial that can be used by everyone to get familiar with RIOT.

The subsequent PRs will then introduce #21434 C Tutorials and #21435 Rust Tutorials.

Testing procedure

This PR should only touch the guides site and modernize some parts of the already existing guides we had. There are no code changes outside of the guides site, nor testable code.

Issues/PRs references

Depends on #21404 Got merged!
Parent of #21434
Parent of #21435

@github-actions github-actions bot added Area: doc Area: Documentation Area: CI Area: Continuous Integration of RIOT components Area: tools Area: Supplementary tools labels Apr 24, 2025
@crasbe crasbe added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation State: waiting for other PR State: The PR requires another PR to be merged first and removed State: waiting for other PR State: The PR requires another PR to be merged first labels Apr 24, 2025
@github-actions github-actions bot removed Area: CI Area: Continuous Integration of RIOT components Area: tools Area: Supplementary tools labels Apr 25, 2025
@AnnsAnns
Copy link
Contributor Author

As #21404 has been merged this PR is now ready for review (and now actually readable 😄)

@Teufelchen1
Copy link
Contributor

@maribu can I get you to review the file doc/guides/getting-started/install-wsl.mdx in this PR?

@AnnsAnns
Copy link
Contributor Author

@maribu can I get you to review the file doc/guides/getting-started/install-wsl.mdx in this PR?

From all I can remember the install-wsl guide should actually be close to identical with the previous one. So a review will probably not be as annoying as it may seem 😄

@maribu
Copy link
Member

maribu commented Apr 26, 2025

I can confirm that the changes to the WSL guide are just impedance matching for different markdown flavors.

It would probably be good to check if the guide is actually still accurate. But the goal of this PR is not updating the WSL guide. So even if the guide would no longer be accurate, I think updating it would be a separate PR. (And we can update the guide after this PR just was well, so I see no reason of delaying this PR for checking the WSL guide.)

Copy link
Contributor

@Teufelchen1 Teufelchen1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 👍 Only minor comments.

@mguetschow
Copy link
Contributor

Thanks for working on this! Is it already previewed somewhere (automatically?) for a lazy reviewer like me?

@AnnsAnns
Copy link
Contributor Author

Thanks for working on this! Is it already previewed somewhere (automatically?) for a lazy reviewer like me?

Sadly not, the more I think about this the more this would probably be a really nice feature to have. I initially thought this could be solved using the doxygen preview CI script we have but this might not be the case as starlight is path sensitive and would break with the approach we are taking for the doxygen preview (Just drop all the files into a folder named after the commit) unless we change some config parameters within astro.config.ts within the CI each time.

TLDR: Really neat but possibly harder to integrate with the current preview system than I would have initially guessed. (I also quite frankly don't even properly understand Murdock, feels hard to understand from the outside 😅)

@Teufelchen1 Teufelchen1 changed the title doc/guides: Getting Started doc/guides: Add Getting Started guide Apr 29, 2025
@AnnsAnns AnnsAnns force-pushed the tutorials/getting_started branch from 0a50ad6 to 69e303d Compare April 29, 2025 16:25
@github-actions github-actions bot added Area: tests Area: tests and testing framework Area: build system Area: Build system Area: pkg Area: External package ports Area: sys Area: System labels Apr 29, 2025
@AnnsAnns AnnsAnns force-pushed the tutorials/getting_started branch from 69e303d to 8a0df4b Compare April 29, 2025 16:25
@github-actions github-actions bot removed Area: tests Area: tests and testing framework Area: build system Area: Build system Area: pkg Area: External package ports Area: sys Area: System labels Apr 29, 2025
doc/guides: remove original windows guide
@AnnsAnns AnnsAnns force-pushed the tutorials/getting_started branch from dd2873a to d511d60 Compare April 29, 2025 16:40
@Teufelchen1 Teufelchen1 added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Apr 29, 2025
@Teufelchen1 Teufelchen1 enabled auto-merge April 29, 2025 17:04
@riot-ci
Copy link

riot-ci commented Apr 29, 2025

Murdock results

✔️ PASSED

d511d60 doc/guides: Getting Started

Success Failures Total Runtime
1 0 1 01m:22s

Artifacts

@Teufelchen1 Teufelchen1 added this pull request to the merge queue Apr 29, 2025
Merged via the queue into RIOT-OS:master with commit a1816a7 Apr 29, 2025
26 checks passed
@Teufelchen1 Teufelchen1 added this to the Release 2025.07 milestone Jul 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: doc Area: Documentation CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants