Release notes for the Codex-built admissions website

Redesigning the site around a diagnostic-first premium academic system

The public site now uses a more institutional academic design language and points the primary journey toward the Diagnostic Test instead of a generic consultation path.

• adds the shared academic palette, Source Sans 3 interface typography and Source Serif 4 editorial headings;
• adds a bilingual Diagnostic Test entry section to the homepage with a short visitor-safe intake form;
• updates header, hero, course, TOEFL, footer and mobile CTAs around the primary Start Diagnostic Test action;
• adds cache-busting query strings for the shared CSS and public JavaScript assets;
• keeps public/admin behavior hooks intact while applying compact dashboard styling to the protected admin workspace.

Confirming the local publishing toolchain

The project maintenance environment has been checked after the PATH update, so the static site can continue to be reviewed, versioned and published with the expected command-line tools.

• confirms GitHub CLI authentication for the repository account;
• confirms Node.js and npm are available for frontend and validation tasks;
• confirms ripgrep is available for fast EN/UA parity checks across the static files;
• confirms Git is available on the `main` branch with the expected GitHub remote.

Clarifying the selected teacher team

The founder profile and homepage trust copy now explain how Trinity Upgrade Academy selects teachers through TatianaSF's long education-operations history, rather than presenting the team as a generic tutoring roster.

• adds the 15+ year company-history signal to the founder profile;
• adds 10,000+ teacher interviews and 1,000+ educators worked with as teacher-selection context;
• connects the homepage trust block to the internal TatianaSF profile;
• keeps the claim focused on careful selection and avoids guaranteed admissions or unsupported outcomes.

Adding an internal founder profile for TatianaSF

The public site now has a dedicated bilingual founder profile, so visitors can understand the minimum relevant public context behind Trinity Upgrade Academy without sending every founder mention to an external profile.

• added founder.html and the synchronized founder-uk.html profile pages;
• moved public-safe founder context into the profile: education leadership, admissions methodology and careful scale signals;
• changed visible TatianaSF mentions across public pages to use the matching internal profile page;
• kept LinkedIn and TatianaSF.com as secondary external links from the profile page only;
• updated the source notes, visual sitemap, technical sitemap and maintenance rules for the new internal-link requirement.

Adding a protected weekly log for admin workspace updates

The protected admin workspace now has its own Russian-only weekly update log, so internal operating notes can stay separate from the public build log.

• adds a private admin log index at `admin.trinityua.com/log/` with a week-number naming strategy;
• starts the full weekly archive with `2026-w17`, covering the admin workspace and analytics setup;
• reduces the protected admin hero title size by roughly three times for a denser workspace view;
• updates protected deployment so `admin/log/` publishes only to the Cloudflare-protected admin subdomain.

Marking the public funnel for GA4 sales signals

The public site now sends structured dataLayer events for the main sales-first funnel: CTA clicks, roadmap downloads, offer interest, section engagement and future form interactions.

• adds automatic GA4/GTM events for consultation, diagnostic, course, roadmap and language-switch actions;
• tracks section views, scroll depth and public offer interest without storing personal lead details;
• prepares future diagnostic forms to emit `form_start` and `form_submit` events;
• documents recommended GA4 key events and keeps off-site sales activity in private CRM/admin systems.

Automating Search Console data for the protected admin workspace

The admin workflow can now generate a read-only Search Console report during protected deployment, so SEO priorities do not depend on manual copy-paste from Google Search Console.

• adds a Search Console API script that writes an aggregated admin-only JSON report;
• shows automated summary metrics and SEO opportunities inside the EN/UA admin dashboards;
• keeps OAuth secrets, refresh tokens and generated reports out of committed public files;
• lets GitHub Actions refresh the protected admin report when GSC secrets are configured.

Making the public site and admin workspace more compact

The shared type scale now uses smaller hero and section headings, and the protected admin language switch matches the public EN / UA pill format.

• reduces global `h1` and `h2` sizes across the live website;
• adds tighter admin-specific heading sizes and hero spacing;
• changes admin language switching from flag labels to the same `EN` / `UA` format used on public pages;
• keeps the admin links inside the protected `admin.trinityua.com` domain.

Keeping admin language switching inside the protected workspace

The admin area now has a protected Ukrainian workspace and a clearer owner dashboard structure centered on Search Console and Google Analytics 4 signals.

• adds `https://admin.trinityua.com/uk.html` as the protected Ukrainian admin page;
• keeps `🇺🇸 EN` and `🇺🇦 UA` admin shortcuts inside the protected admin domain;
• adds a GA4 acquisition and conversion board alongside the Search Console board;
• keeps OAuth tokens, API keys and raw analytics exports out of the static admin workspace.

Adding a Search Console decision board to the admin workspace

The protected owner workspace now has a lightweight GSC planning board for turning Search Console snapshots into prioritized SEO actions without storing API secrets in static HTML.

• adds a no-secret GSC summary block for clicks, impressions, CTR, position and review window;
• adds a Search Console opportunity list for queries, pages, intent and next action;
• calculates simple decision signals for low-CTR, near-page-one and indexing opportunities;
• keeps the admin workspace noindex and outside public sitemap surfaces.

Adding a human-readable visual site map

The public website now includes a bilingual visual site map so visitors can quickly understand the main pages, admissions sections, TOEFL 2026 paths, roadmap downloads and build-log resources.

• adds synchronized English and Ukrainian visual site map pages;
• places a quiet site map link in the homepage footer in both languages;
• updates the technical sitemap with canonical EN/UA alternates for the new pages;
• keeps the protected admin workspace outside public navigation and sitemap surfaces.

Simplifying the protected admin workspace

The admin workspace now relies on Cloudflare Access before the page loads, so the extra local login gate has been removed and the workspace opens directly after PIN authentication.

• removed the local admin username/password gate and lock button;
• kept the owner workspace as a protected noindex page on `admin.trinityua.com`;
• changed the admin interface to English as the primary working language;
• added `🇺🇸 EN` and `🇺🇦 UA` shortcuts to the public language versions in the upper-right navigation.

Adding the TOEFL 2026 hub and CTA destinations

The public site now has a bilingual TOEFL 2026 hub with stable anchors for diagnostic, exam selection consultation and course placement.

• adds synchronized English and Ukrainian TOEFL 2026 hub pages;
• connects homepage English-test mentions and final CTAs to the new hub;
• updates the sitemap with canonical EN/UA alternates for the TOEFL hub;
• records the scheduled TOEFL 2026 article queue for future automated publishing.

Moving the owner workspace behind the protected admin subdomain

The owner workspace is now prepared for a separate `admin.trinityua.com` deployment, while the public academy website no longer publishes the admin HTML page.

• split the GitHub Actions workflow into public and protected admin deployment targets;
• deploys the admin workspace as `index.html` on the protected admin subdomain;
• removes the legacy `admin.html` file from the public academy deployment during release;
• adds origin hardening for the admin subdomain with noindex headers and Cloudflare-only access rules.

Keeping the release timeline first

The build log keeps the original version-date-summary format as the main reading flow, with expanded technical context moved into a separate section below the timeline.

• restored the compact release timeline as the first major blog section;
• moved the longer technical explanations into technical notes below;
• kept each expanded note linked from the versioned release log instead of replacing the release log;
• updated the homepage project note to point to the build log overview again.

Making the build log more useful and safer to read publicly

The build log now includes longer technical summaries that explain the project as a content, deployment and SEO system without exposing private operating details.

• added public-safe technical notes about bilingual content architecture, static deployment and SEO infrastructure;
• reframed the build log intro and metadata toward engineering, release process and search visibility;
• kept private strategy, sensitive operations and personal context out of the public article-style summaries;
• linked this release entry to the separate technical notes section.

Separating the public build log from internal operating notes

The project now has a hidden noindex owner workspace for internal operating notes, plus a clear rule for what belongs in the public build log and what stays private.

• added an internal owner workspace with a lightweight login gate and browser-local notes;
• kept the internal page out of public navigation and the sitemap, with noindex metadata;
• documented the boundary between public release notes and private operational planning;
• updated project instructions, content notes, SEO guidance, version badges and the Russian changelog.

Clarifying the first-step CTA flow

The homepage now uses clearer start labels so visitors are not sent to a process section by a button that sounds like a confirmed booking link.

• renamed the primary homepage CTAs to guide visitors toward the first-step section;
• made the final CTA explain the choice between reviewing the process and downloading the roadmap;
• kept the English and Ukrainian CTA structure aligned;
• preserved existing SEO metadata, hreflang, canonical URLs and internal anchors.

Making Codex changes publish to the live website

The maintenance process now states that Codex-made live-site changes should be committed and pushed to main after validation, because GitHub Actions deploys only after that push.

• added the publication rule to project instructions and content maintenance notes;
• documented that local edits do not update the live Hostinger site until main is pushed;
• called out the need to review git status, stage only intended files and include referenced assets;
• kept the English and Ukrainian build log entries synchronized.

Optimizing the hero image after the SEO quick check

The live SEO review confirmed that crawl access, sitemap discovery, canonical URLs, hreflang and structured data are healthy, then identified the hero PNG as the biggest performance win.

• added a WebP version of the homepage hero image while keeping the PNG fallback for compatibility;
• updated the English and Ukrainian homepage preload and hero markup to use the lighter WebP asset;
• kept social preview image metadata stable for link sharing;
• removed the leftover Demo wording from the Ukrainian build-log page title.

Documenting the local authoring environment fallback

The project notes now record that content maintenance can continue with PowerShell-only search commands when ripgrep is visible but cannot run in the current environment.

• checked the local availability of ripgrep, Git, GitHub CLI, Node.js and npm;
• documented the no-ripgrep fallback in the live homepage project note;
• kept English and Ukrainian homepage messaging synchronized;
• updated version badges, source notes and the Russian changelog.

Installing Google Tag Manager

The live website now includes the Google Tag Manager container so analytics, search verification and future marketing tags can be managed from one place.

• added the GTM head script to all public HTML pages;
• added the noscript fallback immediately after each opening body tag;
• kept the implementation static, without WordPress, PHP application logic or Node deployment;
• documented the analytics setup for future maintenance.

Adding an admissions glossary for key terms

The homepage now explains important admissions terms directly on the page, helping visitors understand the language of selective admissions, exams and application strategy.

• added a bilingual glossary section to the English and Ukrainian homepages;
• explained terms such as Ivy League, MBA, EMBA, target list, application package, test waiver and school fit;
• linked the glossary from homepage navigation, footer links and build log navigation;
• documented the terminology strategy in `docs/terminology-analysis.md`.

Standardizing the creator name and LinkedIn link

The creator name is now written consistently as TatianaSF across live pages, metadata and maintenance notes.

• changed visible creator mentions to the no-space name format;
• made every visible creator-name mention on live pages link to the LinkedIn profile;
• updated metadata, JSON-LD, content notes and project instructions;
• kept the existing SEO structure, canonical links and hreflang setup intact.

Restoring the real-time project note in the homepage hero

The homepage again includes the light project note above the admissions headline, with a short creator context and a direct internal link to the build log.

• restored the real-time project note on the English and Ukrainian homepages;
• returned the single visible Codex SVG logo placement inside that note;
• kept the MBA / Executive MBA outcome panel in the improved light accent style;
• updated synchronized content notes, version badges and the Russian changelog.

Removing the top project note and improving outcome contrast

The homepage now opens directly with the admissions hero instead of a separate project note. The MBA and Executive MBA outcome panel was redesigned as a light accent card for stronger readability.

• removed the top real-time project note from the English and Ukrainian homepages;
• replaced the dark MBA / Executive MBA outcome panel with a high-contrast light accent panel;
• kept the build log links available through navigation and footer links;
• updated synchronized content notes, version badges and the Russian changelog.

Implementing the technical SEO foundation

The website now has a stronger search engine optimization layer: crawl instructions, sitemap, structured data, richer social metadata, absolute language alternates and natural internal links.

• added `robots.txt`, `sitemap.xml` and a brand favicon asset;
• expanded canonical, Open Graph, Twitter Card and structured data metadata;
• added natural internal links for exam preparation, application roadmap and curriculum anchors;
• created `docs/seo-strategy.md` with the SEO strategy and owner tasks.

Removing the top demo banner and simplifying Codex logo usage

The blue top banner was removed so the page starts directly with the site navigation. The Codex logo now appears only once at the beginning of the homepage hero note, using the blue-violet visual direction.

• removed the top demo banner from all live pages;
• updated the Codex SVG colors to blue and violet;
• limited the visible Codex logo to the real-time project note on the homepage.

Updating the creator profile link and SEO maintenance rules

The public LinkedIn profile now points to TatianaSF's portfolio profile, and page maintenance rules explicitly require SEO review and natural internal linking whenever a page changes.

• updated LinkedIn links to `linkedin.com/in/tatianasf/` with `rel="me"`;
• added canonical URLs, Open Graph URLs and x-default alternates for the live domain;
• documented SEO and anchor-based internal linking checks in the project instructions.

Replacing visible Codex text with a local SVG logo

The site now uses a local SVG asset wherever the visible interface refers to Codex, keeping the public pages more visual while preserving accessible alt text.

• added `assets/images/codex-logo.svg` as a reusable SVG logo asset;
• replaced visible homepage and build log references with the logo;
• kept metadata and markdown notes text-based for maintenance and search.

Adding a real-time project note to the homepage hero

The first screen now includes a compact note that introduces TatianaSF as the OpenAI Codex Ambassador building the site live and points visitors to the build log for ongoing updates.

• added a real-time project note to the English homepage hero;
• mirrored the note on the Ukrainian homepage;
• linked the note directly to the synchronized build log.

Making English and Ukrainian content move together

The project instructions now require full language parity across the homepage and the build log. Any change to one language version must be mirrored in the other version in the same update.

• added mandatory synchronization rules to the Codex and content instructions;
• reframed the blog as a readable build log / release-notes timeline;
• added this synchronized release entry in English and Ukrainian.

Adding the creator banner and bilingual build log

The website now introduces the demo context at the very top: TatianaSF, OpenAI Codex Ambassador, is building this project as a public example of working with Codex on a real static website.

• added a top creator banner with LinkedIn and build log links;
• created an English build log page and a Ukrainian companion page;
• updated versioning and markdown content notes.

Automating deployment to Hostinger

The project gained a GitHub Actions workflow that deploys the static site to Hostinger Shared Hosting through SSH and rsync whenever changes are pushed to the main branch.

Splitting the site into English and Ukrainian pages

The homepage became English-first for international presentation, while the Ukrainian page remains available as a complete localized version.