This is an example post — delete it or replace it with your own.
How this site works
· 1 min read
This site behaves like an operating system: windows drag and snap to edges, there is a dock, and two themes swap into each other. The biggest risk with an interface like this is that search engines see nothing at all.
Content first, shell second
All of the text is rendered on the server and sits in the DOM. The OS shell is layered
on top of it, never in place of it. With JavaScript disabled, a .no-js rule hides
the shell and leaves a plain document behind.
Every section has a real address:
/en/about/en/projects/orbit/en/blog/qanday-ishlaydi
Opening a window also updates the URL — ?app=projects&p=orbit. Share the link and it
opens with that window already open; the browser back button closes it.
Two worlds, one component
No component hard-codes a colour. Everything goes through semantic tokens:
--surface, --accent, --window-border, --radius-window. The theme swaps via
<html data-skin>, so Night and Day do not need separate component sets.
What was watched carefully
| Rule | Why |
|---|---|
| No fake status bar on mobile | The real one lands on top of it |
| Hit areas at least 44px | Even when the visual element is smaller |
prefers-reduced-motion |
Boot is skipped, animation stops |