progmaweb/apps/web/tsconfig.json, branch docs/code-of-conduct The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API. Make product.progmasoft.com a catalog like projects.apache.org 2026-11-14T13:21:48+00:00 Leitwolf11 2026-11-14T13:21:48+00:00 fd5d1dfc8223dd660815ee7cca118507985ccc39 The catalog listed two products as cards. It now works as an index of every Progmasoft project, in all four languages: - The front page counts the projects (released, in development, languages), searches them by text, category, language and status with a plain GET form, so no script runs, and lists them in one table: name and tagline, category, language, status, latest release; then the latest releases. - /categories and /languages group the projects; /releases lists the latest release of each, newest first, then those without one. - A project page has a facts box as Apache's has: status, category, language, license, latest release, start date, site, repository and issues. A project in development heads its list "What it is being built to do" instead of "What it does". - Agenceland, Archer and Etincelle join Tazel and Catch3, each marked in development; the archived Tala projects stay out of the catalog. - product.progmasoft.com has a sitemap of its own: the views and every project page. The data is in lib/products.ts (facts, search, releases) and the text in lib/catalog-messages.ts; tsconfig allows .ts imports between lib files so that node:test can load them. Tests: the five projects and their facts, search by text, category, language and status, the query-string parsing, and release order (42 pass); lint and tsc clean; every route rendered by next dev with the product host, in de-DE, ru-RU and he-IL (right to left) too. Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1 
The catalog listed two products as cards. It now works as an index of
every Progmasoft project, in all four languages:

- The front page counts the projects (released, in development,
  languages), searches them by text, category, language and status with
  a plain GET form, so no script runs, and lists them in one table: name
  and tagline, category, language, status, latest release; then the
  latest releases.
- /categories and /languages group the projects; /releases lists the
  latest release of each, newest first, then those without one.
- A project page has a facts box as Apache's has: status, category,
  language, license, latest release, start date, site, repository and
  issues. A project in development heads its list "What it is being
  built to do" instead of "What it does".
- Agenceland, Archer and Etincelle join Tazel and Catch3, each marked in
  development; the archived Tala projects stay out of the catalog.
- product.progmasoft.com has a sitemap of its own: the views and every
  project page.

The data is in lib/products.ts (facts, search, releases) and the text in
lib/catalog-messages.ts; tsconfig allows .ts imports between lib files
so that node:test can load them. Tests: the five projects and their
facts, search by text, category, language and status, the query-string
parsing, and release order (42 pass); lint and tsc clean; every route
rendered by next dev with the product host, in de-DE, ru-RU and he-IL
(right to left) too.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Initialize Progmaweb 1.0.0 corporate and account platform: add a responsive Next.js corporate site without Visual X# compiler-pipeline content, host-aware account routes, registration and dashboard UX, an ASP.NET Core authentication API with account policies, password hashing, secure sessions, rate limiting and security headers, integration tests on Microsoft Testing Platform, locked dependency graphs, reproducible local orchestration, and separate frontend, backend and security workflows. 2026-08-28T20:03:57+00:00 Leitwolf11 2026-08-28T20:03:57+00:00 18da54ce240b1bfefce36aa2ec3b44b58bd0dbde