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 / apps / web / components / Footer.tsx
- Name the copyright license alone in SPDX expressions
- Ask for the Privacy and Security Policies at registration
- Redesign progmasoft.com and add the product catalog and product sites
- Group ViGet by language and by build system
- Call the language Tala on the Progmasoft and ViGet pages
- Describe Progmasoft accurately as an open-source organization across public web surfaces
- Harden Progmaweb identity, localization, and operations
- 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
- Adopt the Progmasoft brand language in the white Microsoft-style site header: replace the improvised gradient P badge with a crisp four-panel mark using the canonical palette, simplify the wordmark treatment, and separate the Account product label without embedding an oversized raster logo.
- 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.