dumindunuwan

A masterpiece!

Use https://dumindu.github.io/E25DX/ kind minimal theme or build a simple GoHugo theme and cut your tech-stack to 1 executable.

If you're reimplementing the wheel, at least do it in latest tech + minimal tech.

Location: Seeking On site Roles with Visa Sponsorship (Currently in Sri Lanka)

Remote: No

Willing to relocate: Yes, prefer Singapore

Technologies: Rust / Go

GitHub: https://github.com/dumindu

Résumé/CV: https://github.com/dumindu/dumindu/blob/master/Dumindu%20Mad...

Email: dumindu [dot] madunuwan [at] gmail

Use right tools! don't be a die hard fan of any language.

However, I used many tech stacks including Hexo navy theme, Docusaurus, Docsy but ended up creating my own setup with Hugo. If you can see, in the project it's more or html/css that can be used with any builder.

First time announced 2018: https://news.ycombinator.com/item?id=16594547

Now with Human written new design and lot of rewrites to match Rust 2024

The project started in 2016 as a Medium publication and GitBook but later moved to https://github.com/learning-rust/learning-rust.github.io

I was updating section by section from time to time. No lies! keeping a Rust tutorial up to date is very tough. Plus, you end up repeating what you already know. It is even tougher, when you have to write code in another language for work.

https://learning-rust.github.io updated to 2026 with lot of rewrites. Human-Authored and target human readers.

What's next?

https://github.com/dumindu/axum and some real world project ideas as a separate section parallel to the docs.

A modern thread per core concurrency focused concurrency docs section, maybe.

More details at https://learning-rust.github.io/journal/ and https://github.com/dumindu

Thanks

Already support:

- https://learningrust.org

- https://learningtypescript.org

- https://learningjavascript.org

- https://learningphp.org

- https://learningzig.org

- https://learningsql.org

More to come :D

No need Hundreds of NPM Packages & Thousands of CSS Classes For a Blog & Documentation Setup

Platform/ Lead/ Staff Go Engineer and Rust Enthusiast

Creator of

- learning-rust.github.io (1500+ GitHub Stars)

- learning-cloud-native-go.github.io (1000+ GitHub stars for codebase/ myapp and documentation)

https://github.com/dumindu

---

Location: Currently stuck in Sri Lanka

Remote: No

Willing to relocate: Singapore, US, Poland, and any good stable location

Technologies: Go, Rust, Kubernetes, Istio,

Résumé/CV: https://github.com/dumindu

Email: Buzz me via https://www.linkedin.com/in/dumindunuwan

This can be just a Hugo theme with much lesser code https://themes.gohugo.io/tags/gallery/

Ex. Content can be in Git repo. Site can be build via static site generators + automated via CI update site when add new content to Git repo. We only need good blog theme, photo albums theme and profile theme to replace FB, Linkedin even TikTok. Publishers have full control on their own data.

I understand these points. As someone who truly love open source, we can see open source projects are becoming just a free training materials for AI. After training LLMs using open-source projects AI can build far superior software one day and that software may be not free, not able to replace by any non-AI software project. We all know that day is not far and that period of time all open-source software might consider legacy as no individual contributor able to implement stuff the speed of AI. What you are protecting is not only a legacy system we build decade old requirements and also the death of the purpose of why people build free software.

What we have to focus is why we created free software, not word by word terms that not fulfill the requirement at this and future time period.

Article 4(3) of the Digital Single Market (DSM) Directive establishes a legal bridge between AI governance and copyright law.

https://www.ddg.fr/actualite/the-european-unions-code-of-pra...

I meant I asked Gemini before and it told the same

The AI Act will be fully applicable from 2 August 2026.

Providers of GPAI models must respect Text and Data Mining (TDM) opt-outs.

2.1 Legal Basis: Article 53(1)(c) AI Act and Directive (EU) 2019/790 The Copyright Chapter of the Code directly addresses one of the most contentious legal questions in AI governance: the use of copyrighted material in training GPAI models and the risk of infringing outputs. Article 53(1)(c) AI Act requires GPAI providers to “identify and respect copyright protection and rights reservations” within their datasets. + This obligation complements the framework of Directive (EU) 2019/790 on copyright and related rights in the Digital Single Market (DSM Directive). Notably, Article 4(3) DSM Directive allows rightsholders to exclude their works from text and data mining (TDM) operations via machine-readable opt-outs.

https://www.ddg.fr/actualite/the-european-unions-code-of-pra...

This is what any AI agent tells

This should be about get permission from open-source developers before feeding their years of work into AI. I think we should not believe what Anthropic, OpenAI, Meta, Google tells.

We should move to local LLMs.

  I'm thrilled to share an open-source project I've been passionately working on end of last year and the beginning of this year, a modern Hugo theme for tech documentations https://github.com/dumindu/E25DX 

 Design: https://dribbble.com/shots/23025050-Tech-Docs-Hugo-Theme

 Demo: https://learning-rust.github.io/ , https://learning-cloud-native-go.github.io/

 Performance: Lightning-fast load times ensure you get what you need, when you need it.

 Vanilla CSS/JS: Crafted from scratch without relying on third-party frameworks or clutter.

 Light Mode & Dark Mode: Seamlessly switch between modes for a personalized experience.

 Code Blocks: Enjoy a smooth reading experience even with code blocks, scoring 100 or 90+!

 Accessibility: Prioritizing inclusivity to make information available to all.

 SEO Practices: Elevating your content to new heights in search engine rankings.

 Best Practices: Adhering to industry standards for a robust and reliable documentation experience.

 PWA Support: Embrace the future with Progressive Web App capabilities.

Happy Coding!

# Repository

https://github.com/docura/docura

# Example

https://github.com/docura/site

# Features

- Responsive and adaptive layouts.

- Built-in dark, light and night themes.

- Customizable menu with Hugo configs.

- Customizable sidebars using Hugo data templates.

- Support for multiple documentation sets.

- Minimal reliance on external frameworks (No CSS, JS/npm, icon, font frameworks).

- SCSS/Vanilla JS based UI components and Hugo pipes based building process.

This repository shows how to build a Dockerized RESTful API application in Go for a simple bookshelf.

Batteries included,

- The idiomatic structure based on the resource-oriented design.

- The usage of Docker, Docker compose, Alpine images, and linters on development.

- Healthcheck and CRUD API implementations with OpenAPI specifications.

- The usage of Goose for the database migrations and GORM as the database ORM.

- The usage of Zerolog as the centralized Syslog logger.

- The usage of Validator.v10 as the form validator.

Hi,

This is the very beginning of this series. As the first step, we are going to discuss about “How to build a Dockerized RESTful API application using Go”.

In this post, we are discussing,

1. Creating a new Go project.

2. Adding initial HTTP server.

3. Adding initial Docker files.

4. Adding initial configurations.

5. Adding Chi router.

6. Adding Zerolog logger.

7. Adding DB docker file.

8. Adding initial database migrations.

9. Adding GORM.

10. Adding initial books API routes.

11. Implementing RESTful handlers.

12. Adding Validator.v9.

The completed project can be found in https://github.com/learning-cloud-native-go/myapp repository. And I’ll upload the same content to https://learning-cloud-native-go.github.io/ which uses Docusaurus in the upcoming days. Hope it will be more structured and easy to see the big picture.

Also, I am not a native English speaker. So, if you found any mistake or something I need to be changed, even a spelling or a grammar mistake, please let me know.

⭐ Contribute! : https://github.com/learning-cloud-native-go/website and https://github.com/learning-cloud-native-go/myapp

⭐ Buy me a coffee! : https://www.buymeacoffee.com/dumindu

⭐ Hire me! : https://github.com/dumindu/hire-me/

Thanks

Hi Guys,

This is the fifth post I wrote about Learning Rust on Medium, https://medium.com/learning-rust. Now you can read the same content via https://learning-rust.github.io as well. In this post, I tried to summarize about,

  - Smart Compiler
    - Why Compiler?
    - Explain Error Codes

  - Panicking
    - panic!()
    - unimplemented!()
    - unreachable!()
    - assert!(), assert_eq!(), assert_ne!()
    - debug_assert!(), debug_assert_eq!(), debug_assert_ne!()

  - Option and Result
    - Why Option and Result?
    - Basic usages of Option
    - Basic usages of Result
    - is_some(), is_none(), is_ok(), is_err()
    - ok(), err() for Result types

  - Unwrap and Expect
    - unwrap()
    - expect()
    - unwrap_err() and expect_err() for Result types
    - unwrap_or(), unwrap_or_default() and unwrap_or_else()

  - Error and None Propagation
    - ? Operator
    - try!()
    - Error propagation from main()

  - Combinators
    - What is a combinator?
    - or() and and()
    - or_else()
    - and_then()
    - filter()
    - map() and map_err()
    - map_or() and map_or_else()
    - ok_or() and ok_or_else()
    - as_ref() and as_mut()

  - Custom Error Types
    - Error trait
    - From trait

> I am a Sri Lankan🇱🇰 Web Developer who works in Vietnam🇻🇳. I am not a native English speaker and I am just practicing Rust in my very little leisure time, while learning more about Golang, Devops and so much in the workplace. So, if you found any mistake or something I need to be changed, even a spelling or a grammar mistake, please let me know.

⭐ Hire me! - https://github.com/dumindu/hire-me/blob/master/resume_dumind...

⭐ Buy me a coffee! - https://www.buymeacoffee.com/dumindu

⭐ Contribute! - http://learning-rust.github.io

Thanks

At that time search was not working, had bit ugly ui, no indicator for current page and etc. Even it's duplicate, this time people actually saw it correctly. So sometimes trying things again is a good thing :) Have a nice weekend!

Thanks for the feedback! It's a good idea to add questions section at the end of each section.

My target is preparing a short and sweet way to learn Rust.

Thanks, glad it helped :)

Have plans to add a "Labs" section besides docs. The idea is in https://www.reddit.com/r/rust/comments/5a2q4k/suggestion_rus... (and https://medium.com/@dumindu/pushing-rust-to-2019-9616d82172d...) unfortunately I am super busy with my career. So have very less time to spend on Learning Rust and updating this.

What you guys think about a documentation like on https://learning-rust.github.io . Will it be difficult to learn Rust with this type of documentation?