# freecode.academy

**Website:** https://freecode.academy

## What It Is

Freecode Academy is positioned as an **AI R&D Lab + private execution network**, rather than a classic freelance marketplace. The core idea is not just to connect clients and contractors, but to participate in the full cycle: clarify the problem, assemble the right team, organize collaborative execution, and maintain responsibility until the actual delivery of results.

The network has existed since 2012 and was reimagined for the AI era in 2026. The website states **4,000+ members** and **100+ studios and teams**.

## Key Principles

* **Curated / invite-only:** restricted access for high signal-to-noise and trust among participants.
* **AI-native:** AI is used not only as a production tool, but also as a navigation and matching layer for people, projects, and offers.
* **Shared responsibility:** the platform does not end its involvement after introducing the parties, but declares shared responsibility for the result.
* **Real collaboration:** emphasis on collaborative teams and real projects instead of random one-off gig orders.
* **Research → execution:** public research and experiments should transition into prototypes, products, and working systems.

## Main Working Cycle

1. **Define the problem** — turn a vague idea into a clear scope.
2. **Assemble the team** — select specialists and teams within the verified network.
3. **Execute together** — work in a coordinated team with shared goals and transparency.
4. **Deliver results** — drive the work to a concrete outcome.

## Main Platform Entities

* **Members** — network participants; public viewing is open, direct contact is restricted to invited participants.
* **Teams** — studios and working teams that can accumulate portfolios and jointly take on more complex projects.
* **Offers** — a flexible format for proposals: service, collaboration, research, hiring, and other initiatives.
* **Projects** — projects with the opportunity to search for partners, investments, and assistance.
* **Tasks** — specific bounded tasks within projects; completed work can become a public worklog/case study.
* **Topics / Publications** — the research and public layer of the platform.

## Who It Is For

### Clients

For companies and founders who need not just to find a contractor, but to navigate the AI chaos, determine the right solution, and assemble a reliable team for implementation.

### Specialists

For professionals who need real projects, strong teams, reputation, and access to a closed deal flow.

### Studios and Team Leads

For teams that want to combine competencies, scale up to larger tasks, and collaborate with other studios.

## Historical Context

Freecode.academy retains an earlier educational layer: learning sections on HTML/CSS/JavaScript/React, algorithms, data structures, and practical projects. In past versions of the project, much attention was paid to teaching web development through real public tasks and pull request workflows. The current positioning is significantly broader: a closed professional network and AI-native project execution infrastructure.

## Why the Project Matters

freecode.academy combines several areas that usually exist separately: a professional community, R&D, project management, team matching, reputation, and AI-assisted matching. The main product hypothesis is that **network quality and responsibility for results are more important than the open scale of a marketplace**.

## Research Sources

* https://freecode.academy/
* https://freecode.academy/about
* https://freecode.academy/projects
* https://freecode.academy/start/developers

Freecode Academy is a private AI-native execution network: a platform that brings together clients, independent specialists, and studios, helping to formalize tasks, assemble teams, and drive projects to results with shared responsibility.

freecode.academy

# Format content

Currently, many pages on the website have poor formatting as a result of an unsuccessful website update.

You need to go through the problematic pages and bring the content to a neat, uniform appearance.

## What to do

- identify pages with broken or messy formatting;
- fix the structure of headings, lists, paragraphs, and other blocks;
- remove visual artifacts and traces of incorrect migration/update;
- bring the formatting to a single style across the website;
- check the final display of the pages after edits.

## Result

The content on the pages should look neat, consistent, and without obvious traces of a poor-quality website update.

Fix poor page formatting resulting from a low-quality website update.

Format content

# Objective

After deploying the fix for percent-encoded URL processing, recheck internal logs and ensure that most of the previously occurring false 404 errors have been resolved.

## What to Check

1. Collect 404 errors for the period following the fix deployment.
2. Compare the nature of the errors with the issue documented in the parent task.
3. Specifically check URLs with special characters and percent-encoding (`%22`, `%40`, Cyrillic, and other encountered cases).
4. Ensure that the fixed routes no longer result in 404 errors.
5. Categorize the remaining errors into:
   - genuinely missing pages;
   - other routing / URL normalization errors;
   - outdated internal or external links;
   - new isolated bugs.
6. If any systemic 404 errors remain, document examples and create separate tasks for the specific root causes.

## Acceptance Criteria

- [ ] Internal 404 logs checked after deploying the fix.
- [ ] Confirmed that the widespread URL decode issue has been resolved or significantly reduced.
- [ ] Remaining 404 errors classified by cause.
- [ ] Systemic residual issues, if any, spun off into separate tasks with specific examples.

Check internal logs after deploying the URL decode fix and identify remaining 404 errors.

Recheck internal 404 logs after URL decode fix

# Specific Pages

Need to recheck the 500 error on the following URLs:

- https://freecode.academy/learn/exercises/bd7158d8c442eddfaeb5bd13
- https://freecode.academy/learn/exercises/5900f4231000cf542c50ff35

## What to Check

1. Open both pages and confirm whether the 500 error reproduces.
2. Find the corresponding entries in the internal logs and stack trace.
3. Determine the exact cause of the error for each URL.
4. Check if the issue is related to the recent URL/URI handling changes or if it is a separate data/rendering/exercise loading bug.
5. If the cause is common, document a single fix; if different, split into separate tasks.
6. After the fix, recheck both pages.

## Acceptance Criteria

- [ ] Both pages checked manually.
- [ ] For each page, a corresponding 500 error is found in the logs or it is confirmed that the error no longer reproduces.
- [ ] Technical root cause identified.
- [ ] Separate fix tasks created if necessary.
- [ ] After fixes, pages return a correct response without 500 errors.

Check for 500 errors on two specific freecode.academy exercise pages after the latest changes.

Recheck 500 errors on exercise pages

Add multilingual support

Boost SEO/GEO

## Goal

Connect the [Freecode Academy](https://freecode.academy/) project with Nikolai Lantz's personal entity at [fi1osof.ru/about](https://fi1osof.ru/about) without merging the project and the person into a single entity.

Unified person identifier:

```text
https://fi1osof.ru/about
```

## What to Do

1. Define the main Schema.org entity of the project on [freecode.academy](https://freecode.academy/): `Organization`, `WebSite`, `SoftwareApplication`, or a combination via `@graph` — based on the actual project model.
2. Add reverse linkage to Nikolai Lantz via a relationship matching his actual role:
   - `founder` — if it is a project/organization founded by him;
   - `creator` — if a software product created by him is being described;
   - if necessary, `author`/`contributor` for specific materials or parts of the site.
3. Use the exact same `Person.@id` in all links:

```json
{
  "@id": "https://fi1osof.ru/about"
}
```

4. Do not use [freecode.academy](https://freecode.academy/) itself as `Person.sameAs`: the project is a separate entity.
5. If a personal page for Nikolai/Fi1osof exists on the site, determine whether it is even needed as a separate public `ProfilePage`; do not substitute the project entity with it.
6. JSON-LD must be present in the server-side HTML.
7. Validate the resulting markup using the [Schema.org Validator](https://validator.schema.org/) and the source HTML.

## Expected Graph

```text
Freecode Academy
    ↓ founder / creator
https://fi1osof.ru/about
    ↓ @type
Person
```

## Definition of Done

- [ ] Freecode Academy is described as a separate project entity.
- [ ] The project is linked to `https://fi1osof.ru/about` via an accurate factual relationship.
- [ ] The project is not added to `Person.sameAs`.
- [ ] JSON-LD is present in the server-side HTML.
- [ ] The markup passes the Schema.org Validator without errors.
- [ ] There are no duplicate independent `Person` entities for Nikolai Lantz.

Add reverse Schema.org linkage on freecode.academy to Nikolai Lantz's personal entity at fi1osof.ru/about.

Connect Freecode Academy with Nikolai Lantz's Person using JSON-LD

## Idea

Add a **"Summarize the core essence"** button to long-form article pages.

Users may not want to read the entire text themselves, but they want to quickly grasp the main idea, arguments, and conclusions. Upon clicking the button, the material is sent to an AI, which returns a concise, to-the-point summary.

## Context

The idea stems from observing real user behavior: long texts are increasingly being bypassed for direct reading, sent to AI instead, and queried for content. In such a scenario, AI becomes an intermediary layer between the author and the reader.

For FreeCode, this is a natural AI-native feature: authors can publish full, well-argued pieces, while readers can choose their depth of consumption.

## Basic Scenario

1. The user opens a long article.
2. Clicks **"Summarize the core essence"**.
3. The AI analyzes the current material.
4. Returns a compact summary:
   - what the material is about;
   - the main idea;
   - key arguments;
   - main conclusions.
5. The user continues reading the original if necessary or asks clarifying questions.

## Important Principle

This is not just an automatic fixed-length `summary`.

The goal is to reduce reading volume **without losing the semantic core**. That is, the summary must convey precisely what changes the reader's understanding, rather than mechanically compressing each section.

## Potential Development

Later, the feature can be expanded with depth levels:

- "In two sentences";
- "Briefly";
- "Key arguments";
- "What's new here?";
- "What is important for me to know?";
- interactive Q&A based on the material.

However, the first MVP is a single clear **"Summarize the core essence"** button and a short, high-quality response based on the current material.

## Result Criterion

The user should be able to grasp the meaning of a long article in significantly less time and decide whether to read it in full or ask additional questions.

Give users the ability to get a short semantic summary of a long article using AI instead of reading the entire text themselves.