Changelog

New

• Site-wide search. There is search now — across interview questions, roadmap topics, the C++ Core Guidelines and blog posts, over their full text rather than their titles. It is hybrid: a vector (semantic) engine joins the full-text one — query and content are embedded and compared by meaning, and the two result sets are fused by RRF ranking. So the right piece turns up even when you named it in your own words instead of the author's. The index re-syncs on a schedule, so newly published, edited or deleted content shows up — and disappears — in search the way it does on the site.
• A ⌘K search palette. Search opens from any page with ⌘K (Ctrl+K), from the field in the top bar, or from the search icon on mobile. Results are tagged by what they are — question, topic, guideline, article — the ones you opened recently are kept, and quick jumps to the main sections sit alongside them. The full result list with filters lives on its own search page.
• Search asks you to sign in. Every query runs a paid lookup behind the scenes, so search lives behind a free account, with an allowance of 1,000 searches a month that resets on the 1st. Signed out, the search field, the mobile search icon and the ⌘K shortcut all open a sign-in dialog carrying the same Telegram, Google and Apple buttons as the login page.
• The roadmap as a map or a list. Each track's page now has a Map | List switch. The list is the same topics line by line, with the level, the number of sub-topics and questions, and a hint at where to go next; search works over the same fields in both views, so anything you find on the map you also find in the list. The control bar sticks to the top, and the intro now describes what the page actually does, instead of promising a phone map and prerequisite gating that were never there. The redundant stat block is gone.
• Nicer code blocks, callouts and tables in articles. Code blocks now carry a top bar with the language name and a one-tap copy button. Callouts render as coloured badges, and tables read as clean cards. Blog authors get matching callout and table tools in the editor.
• Images in articles: sizes and rows. An image can now be small (320 px), medium (560 px), or the full column width — and full width is still the default, so nothing published earlier changed. Several images can sit in one row, where the size stops meaning width and starts meaning share of the row: a "before" and an "after" line up in whatever proportion you want. On a phone a row folds back into a column. Blog authors get sizes and rows from a floating toolbar above the selected image.
• A view counter on articles. The number of views now sits next to the date and reading time. One reader counts once a day, and until a post passes 50 views no number is shown at all — a fresh article doesn't have to look empty.
• Articles open instantly in Telegram. A link shared to Telegram now unfolds into Instant View: the cover leads as the first photo, code reads without the surrounding chrome, callouts and tables stay in place, spoilers become expandable blocks, and YouTube videos play right inside the article.

Improved

• A calmer top bar. The navigation bar got more breathing room and a lifted active-page pill, and the whole site now lines up to one shared content width — the brand mark, the menu and each page's heading finally share an edge.
• Code in search results. Code fragments inside question wording render as code instead of text with raw markup characters — both in the ⌘K palette and on the search page.
• Article covers sit properly. A cover that a crop would butcher is now shown whole against a blurred backdrop instead of losing half the frame, and each slot — the card in the feed, the article header — picks how to fit it independently.
• Reading time is measured from the text. The "N minutes" estimate is derived from the article's own body when it is saved, rather than typed in by the author, so it no longer disagrees with the real length of the piece.
• The AI interviewer's follow-up questions sound more natural and stop giving the answer away. A follow-up no longer hands you the expected answer in brackets or after a colon, no longer breaks off mid-sentence, and always ends in a question — it used to be able to collapse into "You said that…", leaving nothing to reply but "yes, correct". The leak check got sharper too: it no longer objects to a question built out of your own words, and it now sees the code being discussed.
• A custom AI interview costs what it lasts. The launch price was computed from the number of selected topics, and the builder selects the whole stack by default — so a "five-minute" Go run planned 36 questions and asked for 72 tokens. The question count is now capped by the chosen length, and the price matches the session's duration, the way it already did in mixed mode.
• A report from an interview carries its context. The Report button now attaches a snapshot of the session at the moment you send it — the question, your answer, the grade and the conversation so far — and the report is stored on our side even if Telegram is unreachable right then.

Fixed

• Cleaner tables of contents. A heading that uses tinted text, a spoiler or strikethrough no longer leaks its raw markdown markers into the article's contents list and sidebar.
• A new article shows up in the feed right away. The blog index could be served from a stale cache, so a freshly published post was missing from the list even though its own link worked.
• A deleted post leaves search. Removing a blog post now also removes it from the search index — it used to keep surfacing a result whose page 404s.
• Copy works in the quiz again. In test mode, Ctrl/Cmd+C and Ctrl+A were being read as "answer option C" and "answer option A", so you could not copy a question. Keyboard shortcuts now ignore any keystroke that carries a modifier or lands in a text field.
• Switching language no longer resets an interview. Flipping RU⇄EN mid-session restarted an AI interview on a fresh set of questions and sent tests back to question one.
• Granted tokens no longer lock the settings. When a balance rested on admin-granted tokens, the builder marked every length and the voice toggle as unavailable on your plan, even though the launch would have gone through.
• Paying by card closes the window and grants access right away. After a successful payment the checkout window stayed open, access did not refresh until a page reload, and the community invitation never appeared.
• Switching accounts shows your own subscription. Signing in, signing out or moving to another account within one tab could keep showing the previous user's subscription — on pricing and in the subscription panel — until a full reload.
• Buttons in the community invitation no longer overflow. On a wide screen two long channel names did not fit the card; the buttons now stack in a column, as they already did on mobile.