Improve the project proposal form to help users understand and select a project short name with less manual follow-up. Today, selecting a short name can require back-and-forth with new project teams. The form should better explain what the short name is, why it is needed, and where it will be used. The form should generate a suggested short name from the project name, allow the user to edit it, and update usage examples in real time. ## Proposed behaviour For example, if the user enters the project name **"Eclipse Ushnuu"**, the form generates a suggested short name (e.g., **ushnuu**) as they type. At the same time, the form displays examples of how the short name will be used throughout the Eclipse ecosystem, such as: * Project identifier: `zoquo.ushnuu` * Project website: `https://eclipse.dev/ushnuu` * Project mailing list: `ushnuu-dev@eclipse.org` * Project metadata (PMI) page: `https://eclipse.dev/zoquo.ushnuu` * GitHub organization: `https://github.com/eclipse-ushnuu` * GitLab group: `https://gitlab.eclipse.org/eclipse/ushnuu` If the user edits the suggested short name, all of the usage examples should update in real time. ## Notes This is a good opportunity to use the **Claude Design → Claude Code** workflow to design how these examples should appear in the Project Proposal form and then implement that design directly in code. ## Original issue https://gitlab.eclipse.org/eclipsefdn/software-dev/websites/projects.eclipse.org/-/work_items/456#note_6798211 /cc @carmendelgado @wbeaton