progmaweb
The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.
Clonegit clone https://git.progmasoft.com/progmaweb
mainroot / README.md
- Serve git.progmasoft.com from the Next.js site instead of cgit
- Serve the Agenceland MCP Marketplace on agencelandmcp.progmasoft.com
- Describe the hosts, routes and limits Progmaweb has
- Remove ViGet; keep the accounts
- Publish the site in French in place of Hebrew
- Fit every page to phones and test the layout with Playwright
- Merge main into legal/patent-grant-notice
- Remove what is left of the former language and its site (#70)
- Name the copyright license alone in SPDX expressions
- Lead the old Tala catalog addresses to the language list
- Describe the language catalogs of ViGet in the README and architecture
- Group ViGet by language and by build system
- Call the language Tala on the Progmasoft and ViGet pages
- Hand version updates to Renovate
- Keep accounts and sessions in PostgreSQL
- Describe the stricter documentation gate in the guides
- Document the architecture, the account API, localization and limitations
- Harden Progmaweb account API and CI coverage credentials
- Add Progmaweb frontend tests and full-stack security and coverage workflows
- Move the ViGet package and DSL-plugin catalogs into Progmaweb as host-aware Next.js routes, add complete en-US and German content, persistent light and dark themes, catalog-specific metadata, robots and sitemap responses, and an Nginx ownership contract for viget.progmasoft.com.
- Describe Progmasoft accurately as an open-source organization across public web surfaces
- Harden Progmaweb identity, localization, and operations
- 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.
- Make the Progmasoft Account name the explicit ViGet publisher identity. Show the exact shared name in account discovery and dashboard views, document that ViGet does not create a second publisher identity, and retain case-preserving canonical account coordinates.
- Align Progmasoft account navigation with the canonical ViGet domain. Document account.progmasoft.com/<Account>/dashboard as the stable account dashboard route and update company and account surfaces to link to viget.progmasoft.com instead of the retired xsharp-lang.xyz registry host.
- Establish Progmasoft copyright ownership across the corporate website and account service, license all project-owned sources under AGPL-3.0-or-later, add the shared defensive Progmasoft patent grant with SPDX and REUSE coverage, preserve source-availability obligations, and align notices, npm and .NET package metadata, frontend, API, tests, deployment configuration, and repository documentation
- 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.