<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/apps/web/app/globals.css, branch site/not-found</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Fit every page to phones and test the layout with Playwright</title>
<updated>2026-11-16T17:28:33+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T17:28:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=537b1f3a4a605b7aa980eec520628ff37648f683'/>
<id>537b1f3a4a605b7aa980eec520628ff37648f683</id>
<content type='text'>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Name the copyright license alone in SPDX expressions</title>
<updated>2026-11-15T10:14:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T10:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=3bda6d7bc28c5aa588418d12d9e3129f8526df50'/>
<id>3bda6d7bc28c5aa588418d12d9e3129f8526df50</id>
<content type='text'>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix what Playwright found at phone width; keep the header inside it</title>
<updated>2026-11-14T13:31:03+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-14T13:31:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=02b9cd891bdc5e2e2eb6ed4ffe6ef6272ff93b77'/>
<id>02b9cd891bdc5e2e2eb6ed4ffe6ef6272ff93b77</id>
<content type='text'>
Checked in Chromium through Playwright against a production build:
seven catalog pages, four languages, 1366 and 390 pixels wide, with the
console, CSP and horizontal overflow watched.

- The site header was 51 px wider than a 390 px phone on every host
  (progmasoft.com, account, viget and the catalog): the brand, the
  account button and the two preference controls did not fit. Below 480
  px the gaps shrink and the header may wrap to a second line; overflow
  is 0 on all of them now.
- .pm-catalog already named the dashed box of the home page, which
  framed the whole index; the index is .pm-index.
- Phone width: the four numbers sit two by two, the project column of
  the table keeps 200 px, and the index starts closer to the hero.
- A project's description goes into the hero, as before, instead of
  running into the heading of its list.

No console errors, no CSP violations, no overflow on any of the 56 page,
language and width combinations.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Checked in Chromium through Playwright against a production build:
seven catalog pages, four languages, 1366 and 390 pixels wide, with the
console, CSP and horizontal overflow watched.

- The site header was 51 px wider than a 390 px phone on every host
  (progmasoft.com, account, viget and the catalog): the brand, the
  account button and the two preference controls did not fit. Below 480
  px the gaps shrink and the header may wrap to a second line; overflow
  is 0 on all of them now.
- .pm-catalog already named the dashed box of the home page, which
  framed the whole index; the index is .pm-index.
- Phone width: the four numbers sit two by two, the project column of
  the table keeps 200 px, and the index starts closer to the hero.
- A project's description goes into the hero, as before, instead of
  running into the heading of its list.

No console errors, no CSP violations, no overflow on any of the 56 page,
language and width combinations.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Ask for the Privacy and Security Policies at registration</title>
<updated>2026-11-06T09:57:27+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-06T09:57:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=53fb8b8bde857025d12655ae53857fc30226b186'/>
<id>53fb8b8bde857025d12655ae53857fc30226b186</id>
<content type='text'>
progmasoft.com/privacy and progmasoft.com/security publish the two
policies in en-US, de-DE, ru-RU and he-IL, and the footer links both.
The Privacy Policy says what an account keeps and that Progmasoft keeps
an IP address for one purpose only: with a ViGet upload, to establish
where an upload that turns out to be malicious software came from and
to give it to the competent authorities. It says that no data, the IP
address included, is sold, rented or traded. The Security Policy covers
passwords, sessions, HTTPS, the ban on malicious software in ViGet and
how to report a weakness.

The registration form asks the person to accept both policies, and the
API refuses a registration without that acceptance, with a password
(acceptPolicies, a validation error of that field) or through Google:
the start of a Google registration without acceptPolicies=true goes
back to /register?google=policies-required, and the completion creates
no account unless the authentication state carries the current version.
An account keeps the version it accepted and the moment, in two new
columns that schema step 2 adds; accounts created before it keep null.
PolicyAcceptance.CurrentVersion and policyVersion on the web side name
the same date, and a web test reads the C# constant to keep them equal.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
progmasoft.com/privacy and progmasoft.com/security publish the two
policies in en-US, de-DE, ru-RU and he-IL, and the footer links both.
The Privacy Policy says what an account keeps and that Progmasoft keeps
an IP address for one purpose only: with a ViGet upload, to establish
where an upload that turns out to be malicious software came from and
to give it to the competent authorities. It says that no data, the IP
address included, is sold, rented or traded. The Security Policy covers
passwords, sessions, HTTPS, the ban on malicious software in ViGet and
how to report a weakness.

The registration form asks the person to accept both policies, and the
API refuses a registration without that acceptance, with a password
(acceptPolicies, a validation error of that field) or through Google:
the start of a Google registration without acceptPolicies=true goes
back to /register?google=policies-required, and the completion creates
no account unless the authentication state carries the current version.
An account keeps the version it accepted and the moment, in two new
columns that schema step 2 adds; accounts created before it keep null.
PolicyAcceptance.CurrentVersion and policyVersion on the web side name
the same date, and a web test reads the C# constant to keep them equal.
</pre>
</div>
</content>
</entry>
<entry>
<title>Redesign progmasoft.com and add the product catalog and product sites</title>
<updated>2026-10-23T08:29:43+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-23T08:29:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=20a55c4ccbb0f181346444a4c7f083e86389cf9c'/>
<id>20a55c4ccbb0f181346444a4c7f083e86389cf9c</id>
<content type='text'>
progmasoft.com presents Progmasoft as a pool of technology areas instead
of a list of products: languages and compilers, build and packages,
developer tools, quality and testing, identity and access, and
infrastructure. The page has a new hero, a bento of areas, principles and
a developers band that leads to the Progmasoft Console; the products are
one link away in their own catalog.

product.progmasoft.com lists Tala, talac, talafmt, talalint, Tazel, Xide
and Catch3, each with its own page (/tala-lang, /talac, ...) that leads
to the product's site and source. ides.progmasoft.com lists the IDEs and
hosts the Xide site at /xide; catch3.progmasoft.com is the Catch3 site.
The facts follow the READMEs and documentation of the product
repositories: Xide is marked as early work, and Catch3 states that it is
not an official Catch2 release.

The theme switch no longer freezes or flickers. The layout rendered
data-theme="light" on &lt;html&gt;, so every server re-render of the layout
(a language switch) set it back. The control also applied the theme in
an effect after the render while buttons animated their colours. The
attribute now belongs to the bootstrap script and the control alone; the
control applies the theme in the click, and transitions are off for the
two frames of the change.

All new text is in en-US, de-DE, ru-RU and he-IL. The old home messages
leave localization.ts. The proxy maps the new hosts through one table, and
nginx gains their virtual hosts.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
progmasoft.com presents Progmasoft as a pool of technology areas instead
of a list of products: languages and compilers, build and packages,
developer tools, quality and testing, identity and access, and
infrastructure. The page has a new hero, a bento of areas, principles and
a developers band that leads to the Progmasoft Console; the products are
one link away in their own catalog.

product.progmasoft.com lists Tala, talac, talafmt, talalint, Tazel, Xide
and Catch3, each with its own page (/tala-lang, /talac, ...) that leads
to the product's site and source. ides.progmasoft.com lists the IDEs and
hosts the Xide site at /xide; catch3.progmasoft.com is the Catch3 site.
The facts follow the READMEs and documentation of the product
repositories: Xide is marked as early work, and Catch3 states that it is
not an official Catch2 release.

The theme switch no longer freezes or flickers. The layout rendered
data-theme="light" on &lt;html&gt;, so every server re-render of the layout
(a language switch) set it back. The control also applied the theme in
an effect after the render while buttons animated their colours. The
attribute now belongs to the bootstrap script and the control alone; the
control applies the theme in the click, and transitions are off for the
two frames of the change.

All new text is in en-US, de-DE, ru-RU and he-IL. The old home messages
leave localization.ts. The proxy maps the new hosts through one table, and
nginx gains their virtual hosts.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add Hebrew and follow the browser language by default</title>
<updated>2026-10-03T10:00:20+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-03T10:00:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=5a321c2eb1c691bdb7cc96bbab1e28b88ef92aab'/>
<id>5a321c2eb1c691bdb7cc96bbab1e28b88ef92aab</id>
<content type='text'>
Hebrew (he-IL) joins English, German and Russian with a complete message
tree and its own entry in the language menu.

A visitor who has not chosen a language now gets the language their browser
prefers. The Accept-Language header is negotiated by quality, only the
primary language is compared, and `iw` is accepted as the former code for
Hebrew. A browser that prefers no published language gets en-US, as before.
A language chosen in the menu is still stored in the cookie and always wins.

Hebrew does not mirror the page. The layout, the navigation and code keep
their left-to-right arrangement; only text follows the language. Blocks of
prose run right to left, short pieces such as links and buttons take the
direction of their own first letter, and inputs and code stay left to right.
The onward arrow points left in Hebrew, and a left-to-right mark keeps
"Visual X#" intact inside right-to-left text.

The Hebrew text was not reviewed by a native speaker.

Verified locally: node tests, type check, lint, prettier and a production
build; language selection per Accept-Language header against the dev server;
the Hebrew home and registration pages in a browser.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Hebrew (he-IL) joins English, German and Russian with a complete message
tree and its own entry in the language menu.

A visitor who has not chosen a language now gets the language their browser
prefers. The Accept-Language header is negotiated by quality, only the
primary language is compared, and `iw` is accepted as the former code for
Hebrew. A browser that prefers no published language gets en-US, as before.
A language chosen in the menu is still stored in the cookie and always wins.

Hebrew does not mirror the page. The layout, the navigation and code keep
their left-to-right arrangement; only text follows the language. Blocks of
prose run right to left, short pieces such as links and buttons take the
direction of their own first letter, and inputs and code stay left to right.
The onward arrow points left in Hebrew, and a left-to-right mark keeps
"Visual X#" intact inside right-to-left text.

The Hebrew text was not reviewed by a native speaker.

Verified locally: node tests, type check, lint, prettier and a production
build; language selection per Accept-Language header against the dev server;
the Hebrew home and registration pages in a browser.
</pre>
</div>
</content>
</entry>
<entry>
<title>Switch language in place and add Russian</title>
<updated>2026-10-02T21:20:50+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-02T21:20:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=35158de28f4a0dfc300f2d3b5787d2064a06105c'/>
<id>35158de28f4a0dfc300f2d3b5787d2064a06105c</id>
<content type='text'>
The language control no longer reloads the page. It calls a server action
that stores the preference cookie; Next.js then renders the current route
again and applies it in place, so scroll position, theme and client state
stay. The lang query parameter remains for links and for browsers without
script, and is the fallback when the action cannot reach the server. Both
paths write the cookie with the same attributes from one function.

The toggle button is now a language menu, a native select that lists each
language by its own name, and Russian (ru-RU) is the third locale with a
complete translation of every message.

Tests require every locale to have exactly the message shape of the default
locale with no empty text, and cover the cookie attributes and host
normalization. Verified locally: prettier, eslint, type check, tests, the
production build, and a browser run on the apex and ViGet hosts where the
language changed with no navigation and the scroll position kept.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The language control no longer reloads the page. It calls a server action
that stores the preference cookie; Next.js then renders the current route
again and applies it in place, so scroll position, theme and client state
stay. The lang query parameter remains for links and for browsers without
script, and is the fallback when the action cannot reach the server. Both
paths write the cookie with the same attributes from one function.

The toggle button is now a language menu, a native select that lists each
language by its own name, and Russian (ru-RU) is the third locale with a
complete translation of every message.

Tests require every locale to have exactly the message shape of the default
locale with no empty text, and cover the cookie attributes and host
normalization. Verified locally: prettier, eslint, type check, tests, the
production build, and a browser run on the apex and ViGet hosts where the
language changed with no navigation and the scroll position kept.
</pre>
</div>
</content>
</entry>
<entry>
<title>Extend Progmaweb dark-theme and German localization coverage across account, authentication, recovery, and dashboard routes; localize page metadata and OAuth feedback; expose persistent preference controls in dashboard states; and apply saved themes before first paint.</title>
<updated>2026-09-09T16:41:09+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-09-09T16:41:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=fa3b1f249f390ecd2248e1c17e70ede1364ff034'/>
<id>fa3b1f249f390ecd2248e1c17e70ede1364ff034</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Harden Progmaweb identity, localization, and operations</title>
<updated>2026-09-07T18:31:05+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-09-07T18:31:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=171b443addac11e07559b6c4127e622341fe1961'/>
<id>171b443addac11e07559b6c4127e622341fe1961</id>
<content type='text'>
Adopt Patent Grant 1.1, make the apex host canonical while excluding account surfaces from indexing, move the Progmasoft mail boundary into its owning repository, migrate the .NET 10 tests to native MTP, and add persistent light/dark and en-US/de-DE preferences across corporate and account experiences.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Adopt Patent Grant 1.1, make the apex host canonical while excluding account surfaces from indexing, move the Progmasoft mail boundary into its owning repository, migrate the .NET 10 tests to native MTP, and add persistent light/dark and en-US/de-DE preferences across corporate and account experiences.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add secure Google sign-in to Progmasoft Account. Use the server-side authorization-code flow with an exact account-domain callback, temporary hardened external cookies, verified provider email matching, canonical Account-name creation for new users, and no separate ViGet publisher identity. Add frontend entry points, provider failure guidance, locked Google authentication dependencies, service secret injection, and backend regression coverage without committing OAuth credentials.</title>
<updated>2026-08-30T18:45:01+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-08-30T18:45:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=76c4c1876a86dbca0adf86750362b3581d6fc69d'/>
<id>76c4c1876a86dbca0adf86750362b3581d6fc69d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
