1. Guide
Explains how a project could be built; it does not claim personal completion.
Projects: separating guides from personal records
As of 27 July 2026, no verified personal project record has been published here. The page instead defines the evidence required before a project can enter a personal portfolio.
HONEST STATUS
Why explain the gap instead of filling it with achievements?
The Academy contains many project guides, but that does not mean Doruk completed them. A guide provides a path that a visitor can follow. A personal project record must show ownership, what was actually built, tests, errors, a second version and permission to publish.
When no verified record is available, the site does not invent a project name, award, team, event or result. This may look less impressive in the short term, but it protects the credibility of a student portfolio.
FOUR STATES
What kind of project content is this?
2. Example
Sample code, circuit or design used to teach a concept.
3. Work log
Dated attempts, errors, feedback and changes.
4. Verified personal project
Ownership, production, testing, contribution, sources and publication permission are verified.
PUBLICATION GATE
Required evidence for a personal project record
| Field | Record to publish | Information to exclude or handle carefully |
|---|---|---|
| Problem | Need and user described in the learner’s own words | Private circumstances or personal data |
| Solution | Diagram, algorithm, materials and version | Presenting a ready-made project as personal production |
| Contribution | Who did which part | Names or images of teammates without permission |
| Testing | Expected result, actual result and error | Showing only the successful outcome |
| Sources | Code, image, data and licence | Copied content with unclear origin |
| Safety | Electricity, tools, data and adult support | Details encouraging unsafe replication |
| Permission | Approval for photographs and personal information | Document numbers, location or private contact details |
PROJECT FILE
How is a record prepared before publication?
A project is not complete merely because it worked once. Another person should be able to understand what happened, repeat the test and trace the sources used.
- Add a date and version number.
- Keep the first and final problem statements.
- List materials, software, data and licences.
- Show at least one failed test and the change made.
- Disclose ready-made modules, AI assistance and adult contribution.
- Remove personal data and location from images and screenshots.
- Record whether a second version feels worthwhile and what it would test.
ACADEMY TRIALS
Three safe guides that do not claim personal completion
micro:bit step counter
A lesson on sensor data, thresholds, false counts and privacy.
Open the guide →Reaction-time game
A lesson on timing, latency, repetition and fair comparison.
Open the guide →Accessible sport dashboard
Presenting data through keyboard access and signals beyond colour.
Open the guide →RETURN RULE
When does this page change?
A personal project is added only after its supporting evidence is complete. A future update must show problem, production, error, revision, source, safety and learner contribution together—not only a result card.
If a project is later removed or reclassified, the old status is not silently rewritten; the reason should be recorded in the version notes. The portfolio then becomes a trustworthy learning archive rather than a showcase that only grows.
RETURN AND REVIEW
What happens when the first personal project is ready?
Publishing the first verified project will not turn the page suddenly into an achievement gallery. Each project will be recorded with its identity, date, problem, contribution and publication status. The Turkish and English narratives are then published consistently from that single record.
The most visible part of the project card will be evidence rather than a polished result: a working or failed prototype, measurement, error, source and second version. Competition entry, an award or an appearance of completion is not required. A safe and honest process is more valuable than a dramatic outcome.
Where other people contributed, only Doruk's own contribution is described. Names, images, school details or work belonging to other learners are not published without permission. Adult support, ready-made modules and AI assistance are disclosed.
- Project record with its date and version
- Turkish and English descriptions based on the same evidence
- Failed test and second version
- Team contribution and privacy boundary