legacy-webforms-portal-shell

스타0

포크0

업데이트2026년 5월 14일 06:04

Pattern for a believable back-office ASP.NET Web Forms portal shell

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

jongalloway

jongalloway/EnterpriseModernizationSample

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Context

Use this when the sample needs an internal portal that feels like it grew up beside WinForms tools and MVC sites instead of replacing them. It works well for supervisor dashboards, bulletin centers, and admin shells that should look obviously older than the public storefront.

Pattern

Create a dedicated Web Forms project instead of burying back-office pages inside the MVC storefront.
Give it a master page with blue-gradient corporate chrome, utility nav, terminal hints, and footer copy that feels operational instead of marketing-led.
Bind one representative page directly to existing business-layer services so the portal feels server-heavy and believable.
Add modest AJAX-era behavior such as UpdatePanel refreshes, ACT tabs/modals, and a small legacy script file that can use jQuery when present.
Keep the page practical: dispatch grids, labor watch tables, zone notes, and supervisor reminder panels tell the modernization story faster than generic lorem ipsum admin pages.

Notes

If the page uses ScriptManager or UpdatePanel, add System.Web.Extensions explicitly.
If the page uses classic MVC ViewBag or older Web Forms AJAX packages, expect to restore packages and add missing framework references before validating the full solution.

이 저장소의 다른 Skills

같은 저장소

git-workflow

jongalloway/EnterpriseModernizationSample

Squad branching model: main-only workflow with feature branches

2026-05-180

skill-name

jongalloway/EnterpriseModernizationSample

{what this skill teaches agents}

2026-05-180

legacy-entlib-runtime-bootstrap

jongalloway/EnterpriseModernizationSample

Wire legacy .NET Framework service hosts through Enterprise Library-flavored appSettings so Unity, service location, exception policies, logging, and database aliases all hang off one configuration seam.

2026-05-180

legacy-webforms-order-binder

jongalloway/EnterpriseModernizationSample

Build internal order-management Web Forms pages with ObjectDataSource, GridView, DetailsView, and ViewState-heavy filter handling.

2026-05-180

legacy-dal-seam

jongalloway/EnterpriseModernizationSample

Build a believable mid-2000s .NET data layer around connection catalogs, stored-procedure wrappers, DataSets, and repository facades.

2026-05-150

legacy-storeops-workbench-schema

jongalloway/EnterpriseModernizationSample

Anchor store-ops workbench screens in separate StoreOps tables for order state, status snapshots, workforce alerts, and zone bulletins, with dispatch tickets linked back to orders.

2026-05-150

name	legacy-webforms-portal-shell
description	Pattern for a believable back-office ASP.NET Web Forms portal shell
domain	web-forms
confidence	medium
source	earned

Context

Pattern

Create a dedicated Web Forms project instead of burying back-office pages inside the MVC storefront.
Give it a master page with blue-gradient corporate chrome, utility nav, terminal hints, and footer copy that feels operational instead of marketing-led.
Bind one representative page directly to existing business-layer services so the portal feels server-heavy and believable.
Add modest AJAX-era behavior such as UpdatePanel refreshes, ACT tabs/modals, and a small legacy script file that can use jQuery when present.
Keep the page practical: dispatch grids, labor watch tables, zone notes, and supervisor reminder panels tell the modernization story faster than generic lorem ipsum admin pages.

Notes

If the page uses ScriptManager or UpdatePanel, add System.Web.Extensions explicitly.
If the page uses classic MVC ViewBag or older Web Forms AJAX packages, expect to restore packages and add missing framework references before validating the full solution.