Skip to content
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

docs(blog): add "Documenting Rust code with Markdown" blog post #8

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

klenkovic
Copy link

Adds a new blog post on the GASERI Blog. The post describes usage of Markdown language while documenting Rust code and usage of rustdoc tool to generate a HTML code documentation. It contains a simple guide for the reader to easily try the rustdoc tool on his own machine by spinning up a simple Rust web service powered by the axum web application framework.

@klenkovic klenkovic force-pushed the blogpost/documenting-rust-code-with-markdown branch 5 times, most recently from d1f91e7 to 9f1b349 Compare June 1, 2024 12:17
@klenkovic
Copy link
Author

As requested, the gaseri-rustdoc-demo screenshot has been removed from the patch. Please, let me know if there is something else requiring alteration.

@klenkovic klenkovic force-pushed the blogpost/documenting-rust-code-with-markdown branch 3 times, most recently from bc5f4db to f1cb14c Compare June 1, 2024 14:09
@klenkovic
Copy link
Author

As requested, a \n was added in the docs/en/blog/.authors.yml file, along with the URL.

@klenkovic klenkovic force-pushed the blogpost/documenting-rust-code-with-markdown branch 3 times, most recently from 8dae903 to 516fb74 Compare June 2, 2024 16:59
Adds a new blog post on the `GASERI Blog`. The post describes
usage of Markdown language while documenting Rust code and usage
of `rustdoc` tool to generate a HTML code documentation. It
contains a simple guide for the reader to easily try the
`rustdoc` tool on his own machine by spinning up a simple Rust
web service powered by the `axum` web application framework.
@klenkovic klenkovic force-pushed the blogpost/documenting-rust-code-with-markdown branch from 516fb74 to 540391c Compare June 2, 2024 16:59
Copy link
Contributor

Choose a reason for hiding this comment

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

description: GASERI alumni would be stronger and correct: https://group.miletic.net/en/people/#former-students

- rust
- markdown
- documentation
- rustdoc
Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest removing rustdoc and axum since these tags are unlikely to be repeated in future posts, but rust should be kept

authors:
- klenkovic
date: 2024-06-01
readtime: 15
Copy link
Contributor

Choose a reason for hiding this comment

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

We can also let Material automatically generate this

## Project Setup

Once you have installed Rust on your system, let's create a new project and install some dependencies that we will need for this to work.

Copy link
Contributor

Choose a reason for hiding this comment

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

Would be nice to have a paragraph here giving a bit of context, i.e. Axum is ... Tokio is ... We'll install them right away.

@@ -9,3 +9,8 @@ authors:
description: PhD student
avatar: https://github.com/mateaturalija.png
url: https://mateaturalija.github.io/
klenkovic:
Copy link
Contributor

Choose a reason for hiding this comment

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

I would prefer kristijanlenkovic for consistency

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants