1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
---
name: Progmaweb improvement
about: Propose an account, ViGet, or corporate-web improvement
title: "[Proposal] "
---
<!-- SPDX-FileCopyrightText: 2026 Progmasoft <support@progmasoft.com> -->
<!-- SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Grant-1.1 -->
This repository owns the Next.js public surfaces and ASP.NET Core account API. Requests about the Tala language website or compiler belong in their respective repositories.
### User need and host
Who needs the change, on which host and route, and what cannot they do today? For publisher-related changes, remember that the ViGet publisher is the canonical Progmasoft account name, not a second profile field.
### Proposed behavior
Describe the page, API, or account flow with a concrete example. For registry changes, specify whether the subject is a `.vipkg` or Kotlin DSL plugin JAR and how its public path should appear.
### Security and data impact
Would this change authentication, authorization, account identity, sessions, private data, publication rights, or existing package URLs? Explain how a user would recognize and recover from failure without exposing secrets.
### Presentation and acceptance checks
Describe `en-US`/`de-DE`, light/dark, accessibility, and mobile implications where relevant. What frontend/API tests and live-host checks would prove completion?
|