Task: Connect Nikolai Lanets' professional identity with implemented projects via JSON-LD
Connect Nikolai Lanets' professional identity with implemented projects via JSON-LD
Create a unified Person.@id on fi1osof.ru/about and link client and own projects to it using correct Schema.org relationships.
Goal
Create a single machine-readable Person entity with a permanent identifier on the page fi1osof.ru/about:
https://fi1osof.ru/about
And use this @id on client and own websites to form an unambiguous graph of Nikolai Lanets' professional identity.
fi1osof.ru/about
- replace the current
Personwith the updated version; - add
@id: https://fi1osof.ru/about; - align
@idandurl; alternateName:Nikolai Lanets,Fi1osof;- update
jobTitleanddescriptionfocusing on system architecture, product creation, AI research, AI-native systems, and technology foresight; - use a permanent public image URL, not
/_next/static/media/...; - keep only personal profiles in
sameAs; - remove own websites and projects from
Person.sameAs; - for Freecode Academy, use the Fi1osof personal profile rather than the project's home page;
- keep
knowsAboutat the level of stable areas of expertise rather than libraries; - keep
BreadcrumbListas a separate JSON-LD.
HappyBaby2000
On happybaby2000.ru, add Organization and WebSite, keeping the client's organization as the copyright holder. Link Nikolai via:
"contributor": {
"@id": "https://fi1osof.ru/about"
}
and creditText according to his actual role.
Also, add a visible professional signature with a link to Nikolai Lanets' page, for example:
<a href="https://fi1osof.ru/about" rel="author" title="Nikolai Lanets — Technical architecture, development and AI integration">
Technical architecture and development — Nikolai Lanets
</a>
Do not use © Nikolai Lanets if the client is the copyright holder of the website, brand, and content.
Other Projects
Choose Schema.org relationships based on the actual role:
creator— for a genuinely created product;founder— for a founded organization/project;contributor— for technical participation in a client website.
Do not use creator automatically on all client websites.
Language Versions
All language versions of the page fi1osof.ru/about must describe the same person and use a single Person.@id = https://fi1osof.ru/about. Add hreflang if necessary.
Verification
After implementation, verify:
- fi1osof.ru/about;
- happybaby2000.ru;
- other connected websites;
- Schema.org Validator;
- Google Rich Results Test;
- source server HTML.
JSON-LD must be present in the final HTML and not depend solely on client-side JavaScript.
Definition of Done
- single
Person.@idon fi1osof.ru/about; - correct
sameAs; - permanent
imageURL; - stable
knowsAbout; - HappyBaby has
Organization+WebSitewith the client as copyright holder; - Nikolai is specified via
contributor+creditText; - there is a visible professional signature;
- language versions do not create new Person entities;
- server-side JSON-LD passes validation;
- reusable JSON-LD component prepared for subsequent client websites.
Related Tasks
Ворклоги
Progress on Person at fi1osof.ru/about
The current JSON-LD structure for the Person entity at fi1osof.ru/about has been agreed upon.
Key decisions recorded:
@idandurluse a single addresshttps://fi1osof.ru/about;alternateNamecontainsNikolay LanetsandFi1osof;imageuses a permanent public URL;jobTitleis currently formulated asSystems Architect & AI Researcher;descriptionfocuses on systems architecture, AI-native product development, technology foresight, and intelligent systems;sameAsshould only include personal profiles that identify Nikolay Lanets / Fi1osof;- projects must not be mixed with the
Personentity just because they are associated with Nikolay; - Freecode Academy is a separate subproject. The project itself is not part of
Person.sameAs. A personal profile within it is only acceptable if it genuinely identifies the same person; knowsAboutis used for established areas of expertise rather than a random list of libraries.
The current version of Person is considered generally correct in structure. The next stage of this task is implementation and testing of server-side HTML/validators.