Taskforce is a Turkish community course library, one folder per topic

The stated goal is project based material from basics to advanced

The repository describes its aim in one sentence, and the sentence is the whole product. The goal is to create community supported and open source educational content, and to provide project based material from the fundamentals to an advanced level for people who want to learn programming. That is the promise, and it is a promise about coverage and language rather than about any particular tool. The primary language recorded for the repository is Jupyter Notebook, which tells you the content is delivered as notebooks and code samples rather than as prose documents, and the licence is GPL-3.0, which is the licence the Kodluyoruz project uses. The readme closes by pointing out that this is a Kodluyoruz project, so the repository is one programme's public material rather than an independent course, and the audience is the Turkish developer community that the programme serves.

The directory listing is the curriculum

The top level of the repository is a long list of topic directories, and it is the clearest evidence of what the project covers. The tracks that appear include basics-for-everyone, bootstrap, css and css-temelleri, a series of backend preparation folders numbered by week from backend-hazırlık-1.hafta through backend-hazırlık-6.hafta, android-kotlin, csharp-basics, csharp-basics-proje, csharp-egitimi and csharp-hafta1 through csharp-hafta4, a csharp project on a game collection management system, python tracks including advanced-python, data-analysis-introduction, data-analysis-projects, data-science-100, data-science-101 and data-science-projects, career-preparation, cloud101, Web3, blockchain-basics and algorand, and a long run of build-on directories for individual chains such as build-on-solana, build-on-stellar, build-on-agoric, build-on-aptos, build-on-scroll, build-on-stacks, build-on-internet-computer-with-icp-rust-cdk and build-on-multiversx. There is also a family of bnb-chain directories covering cryptography, fundamentals, smart contract development and solidity fundamentals. The shape of the listing is a curriculum assembled by many people rather than a sequenced course.

Contributing means writing a tutorial and opening a pull request

The readme spends most of its length on the contribution path, and it is specific about it. If you want to help develop the content, you can look at the content creation template and send the content you propose as a pull request, and the content is then reviewed by the team and added to a branch if it is approved. The template matters, because a tutorial that does not follow it will not survive review, and the readme points at its own pull request guide for the mechanics. The readme also states plainly that you do not need the time or the technical knowledge to create content, because you can read the lessons and share the details that slipped past the team, which is the second contribution route. The suggestion or issue report section covers both simple typos and code samples that do not run, and it points to a GitHub issue template chooser so reports arrive in a consistent shape, with ready made templates prepared to make that easier.

The project is explicit that it is a collective effort

There is a passage that explains the scale of the work in a way that also explains the structure. The Turkish proverb quoted is roughly that one hand is no match for two hands, and the readme says this content was not created by a few people but by hundreds, together, always. The contributor graph link is given for the people who made it happen, and readers are pointed back at the section on how to help. The practical reading of that is that the repository is a corpus maintained by rotation, and a newcomer is expected to arrive with one topic rather than with a plan for the whole thing. The images in the repository root, Chiliz.png, OpenCapmus.png and Stellar.png alongside the logo files, fit the pattern of chain specific material that arrives with its own branding, which is one more piece of evidence that the directory structure is the work of many independent contributions.

What a reader gets and what a contributor gets

The two audiences are served by the same tree, and they experience it differently. A reader browsing the repository sees a directory per topic, each presumably containing a notebook or a project, and the value of that is that the content is project based and spans the range from an introduction to a specialist chain or a backend week. A contributor gets a template, a review process and a code of conduct, plus a stated expectation that content is reviewed before it lands. The third audience is the person who found an error, and the readme treats that as a first class contribution rather than a support ticket. What the repository does not offer is any kind of curriculum guarantee. There is no version, no release list and no stated ordering, so the practical way to use it is to pick a track that matches your level and work through it, which is what the directory naming supports well and what a single linear course would support badly.

Where the project is the wrong resource

The first limit is language. The content is written in Turkish, and the readme, the templates and the issue forms are all in Turkish, so for a reader who does not read Turkish the repository is close to unusable even though the code inside is universal. The second is that the content is community produced and reviewed, which means quality varies by contributor and there is no editor with the authority to impose a consistent level across dozens of topics. The third is the maintenance model, because a notebook about a specific library version goes stale, and nothing in the repository structure suggests who owns updating a given folder. The fourth is scope. The breadth that makes the directory listing impressive, spanning basics through data science through eight blockchain ecosystems, is also the reason you cannot assume any particular track has been reviewed recently or that the difficulty level of a folder is comparable to another one. For an English speaking developer the same content is often better sought in a maintained upstream project, and for a Turkish speaker the same route to a single topic is usually better than a directory this wide.

Editorial conclusion

Taskforce suits a Turkish speaker who wants project based material at their own level, whether they are starting with the basics for everyone track or looking at a backend week, and it suits a developer who wants to contribute a tutorial the way the project wants contributions made. It is the wrong resource if you need material in English, and it is the wrong resource if you need a maintained curriculum with a release schedule, since the content is a directory of community submissions rather than a versioned course. Before contributing, follow the content creation template the readme points to, because a pull request is reviewed by the team before it is merged into a branch, and use the suggestion or issue report flow for anything that is a typo or a broken code sample. The last push was on 2026-08-25 and the repository publishes no releases.

Frequently asked questions

Official sources

1. Issues
2. Kodluyoruz/taskforce on GitHub
3. License: GPL-3.0
4. README