he4rt/4noobs: a community index of beginner tutorials, not a tutorial itself

What he4rt/4noobs actually is, and who it is for

The README states the goal plainly: centralizar tutoriais desenvolvidos pela nossa comunidade para pessoas iniciantes em tecnologia. It is an index. The repository's top level holds .github/, .gitignore, README.MD and Templates/, and nothing else. There is no lesson content in this repository at all.

That distinction matters more than it sounds. A newcomer searching for "how do I learn Go" lands on a table row with a one-line description and a link that leaves the repository. The tutorial itself lives in a separate project, often under a different GitHub account. So the value here is editorial: someone decided which guides are worth listing, grouped them into categories, and credited the people who wrote them. The categories in the index are programming languages, frameworks, automation frameworks, tools, operating systems, design, databases, programming paradigms, and a catch-all "diversos".

The audience is narrow and specific. The README is written in Portuguese and the whole project is oriented around the He4rt Devs community, with links to their Twitter, Instagram, LinkedIn, WhatsApp group and Discord. If you are an English-only reader, or you want a single canonical course with exercises and grading, this is not that. If you mentor Brazilian beginners and want a starting reading list you did not have to assemble yourself, the index does the sorting work for you.

How the index is structured and how a new entry gets in

Everything visible lives in one Markdown file. The README opens with a centred logo, a heading, a row of social links, then the stated objective, then a numbered table of contents with anchor links, and then one table per category. Each table row carries four columns: Nome, Descrição, Contribuidores and Link. The link column is literally the text "Clique aqui" followed by an arrow emoji pointing at an external GitHub repository.

That is the entire data model. There is no build step, no generated site, no schema, no search. Adding a tutorial means editing the README table by hand and, per the README's own instructions, also adding any new category to the index at the top. The README even carries an HTML comment above the index noting that a new category requires an entry there too, which tells you the maintenance burden is manual and easy to forget.

The contributor flow is documented in four steps: think of a topic that would have helped you when you were starting, write it simply and directly with practical examples, follow CONTRIBUTING.md and use the template at Templates/README.md, and optionally reuse the visual identity assets under Templates/capas. So the project enforces a shape for the tutorials it links to, even though it hosts none of them. That template is the closest thing to a quality gate.

Installing nothing: how to use the index in practice

There is no package to install and no binary to run. The README gives no installation instructions because there is nothing to install. What you can do is clone the repository to read it offline or to work on a contribution.

The clone command is the standard one, and the default branch is master:

git clone https://github.com/he4rt/4noobs.git
cd 4noobs

After that, the useful file is README.MD at the repository root. Open it in any Markdown viewer or on GitHub and you get the full category tables. If you want to write a tutorial rather than read one, the README points you at the template:

cat Templates/README.md

That file is the model your tutorial is expected to follow. The README also directs contributors to read CONTRIBUTING.md before opening a pull request, and to look at Templates/capas if they want the He4rt header and cover artwork. Note that the README links to the template and the covers on the master branch of the same repository, so the paths above are the ones the project itself uses.

A first real use looks like this: pick a category, for example Linguagens de programação, scan the Descrição column for a topic you want, and follow the Clique aqui link. You will leave he4rt/4noobs immediately. What you see next is whatever that separate repository contains, and this index makes no claim about its completeness or freshness.

The link-rot problem the index cannot solve

This is the honest limitation. Every entry in the tables is a hyperlink to a repository owned by someone else, and nothing in the visible structure records when those targets were last updated. The index's own last push was on 2026-09-05, which tells you the index was touched recently; it tells you nothing about the twenty-odd tutorials it points to.

A beginner following a link to a repository that has not been touched in years has no warning. The README does not carry a per-entry status, a version, or a last-updated column. There is no CI check visible in the top-level entries that would fail a pull request for pointing at a dead repository. The only guardrail is human review at merge time, and review quality is not something the repository documents.

The second limitation is scope drift. Some entries are first-party projects under the he4rt organisation, such as css4noobs, while others are personal repositories under individual accounts. That means the project has no authority over most of what it lists. If a maintainer deletes their repository or renames their account, the index silently rots until someone notices and opens a pull request. Treat he4rt/4noobs as a starting point for a search, not as a vetted catalogue.

Compared with freeCodeCamp and similar structured curricula

The obvious alternative for a beginner is a self-contained curriculum such as freeCodeCamp, or a documentation site like MDN for web topics. The difference in approach is fundamental. freeCodeCamp owns its content: the lessons, the exercises and the progression live in one place, and the maintainers control the quality and the ordering. he4rt/4noobs owns none of its content. It owns the taxonomy and the credit lines.

That trade-off cuts both ways. Because the index does not host tutorials, it can cover a far wider surface with almost no editorial cost: Assembly, Bash, C, C++, C#, Clojure, Crystal, CSS, Dart, Elixir, Go, HTML, XML, Java, JavaScript, Markdown, OCaml, PHP, Python, R and more, each in a row. A single curriculum would never cover that spread, and certainly not in Portuguese for a Brazilian audience. But the index also cannot fix a bad tutorial, cannot update a stale one, and cannot guarantee that two entries in the same category teach compatible conventions.

If your goal is a linear path from zero to employable, a structured curriculum is the better tool. If your goal is to find a short, community-written introduction to one specific topic, in Portuguese, with a human being's name attached to it, this index is the faster route. The two are not substitutes; they answer different questions.

Maintenance, contribution cost and licensing

The repository is not archived, and its last push was on 2026-09-05. That is recent enough that the index is being touched, but the visible structure gives no release history and no versioning, so there is nothing to upgrade in the usual sense. Consumers have no dependency to pin. Contributors have a recurring cost: every new tutorial means a new table row, a new contributor credit, and a possible new index entry if the category did not exist.

For anyone reusing the material, licensing is the open question. The repository metadata retrieved here carries no license, and the README does not state one. That matters because the README explicitly invites contributors to reuse the He4rt headers and covers under Templates/capas. A repository with no license file grants no default permission to copy, modify or redistribute, whatever the README's tone suggests. Before you republish a tutorial, reuse the artwork, or mirror the index, check the license file on the specific linked repository as well, since each linked tutorial is a separate project with its own terms. This is a factual gap in the project, not a legal opinion, and it is the first thing a cautious adopter should look at.

Editorial conclusion

Adopt he4rt/4noobs if you are teaching or mentoring beginners in Portuguese and want a ready-made reading list, or if you want to write a tutorial and need the project's templates and contributing rules. Do not adopt it if you expect a single self-contained course, English-language material, or a stable API; each entry points to a separate repository with its own maintainer. Before relying on it, open two or three of the linked repositories and check their own last commit dates, because this index cannot vouch for them.

Frequently asked questions

Official sources

1. he4rt/4noobs on GitHub
2. Issues
3. README