Update Portal current state for marketing and mobile status
This commit is contained in:
parent
1289f24eaf
commit
ad2b225b77
@ -1,6 +1,6 @@
|
|||||||
# Portal — Current State
|
# Portal — Current State
|
||||||
|
|
||||||
Verified against the local Portal repo after the dashboard/nav cleanup pass, fresh API and Agent repo review, and the server status/host lifecycle/IDE UX pass.
|
Verified against the local Portal repo after the dashboard/nav cleanup pass, fresh API and Agent repo review, server status/host lifecycle/IDE UX pass, and the public marketing/SEO refresh.
|
||||||
|
|
||||||
This file records what is implemented now.
|
This file records what is implemented now.
|
||||||
|
|
||||||
@ -20,6 +20,48 @@ This file records what is implemented now.
|
|||||||
- Unused dependencies and Tailwind plugins have reportedly been pruned from the Portal repo.
|
- Unused dependencies and Tailwind plugins have reportedly been pruned from the Portal repo.
|
||||||
- The Portal cleanup pass reports net line-count reduction rather than growth.
|
- The Portal cleanup pass reports net line-count reduction rather than growth.
|
||||||
|
|
||||||
|
## Public marketing / SEO site
|
||||||
|
- Public marketing now follows a hybrid SaaS structure:
|
||||||
|
- homepage acts as the conversion flow
|
||||||
|
- separate pages support deeper product/SEO intent
|
||||||
|
- Homepage now includes:
|
||||||
|
- hero with platform-neutral copy: `Code, test, and run servers from your browser.`
|
||||||
|
- browser/dev + managed server subheadline
|
||||||
|
- product-style visual panel
|
||||||
|
- Build / Test / Ship workflow
|
||||||
|
- differentiators
|
||||||
|
- use cases
|
||||||
|
- SEO topic links
|
||||||
|
- pricing preview
|
||||||
|
- FAQ preview
|
||||||
|
- final CTA
|
||||||
|
- Root metadata has been updated from the old game-hosting-only description to browser dev environments + managed server hosting positioning.
|
||||||
|
- Pricing has been repositioned from `Vanilla / Modded / Heavy` to workload tiers:
|
||||||
|
- Starter
|
||||||
|
- Pro
|
||||||
|
- Performance
|
||||||
|
- Pricing copy now states that every plan includes a browser-based dev environment and managed server hosting.
|
||||||
|
- Public feature copy now presents the platform as build/test/run rather than Minecraft-only hosting.
|
||||||
|
- LXC/system-container differentiator is represented carefully as avoiding Docker-style game-server overhead without unsupported benchmark claims.
|
||||||
|
- The fake `zlh build --target server` hero command was removed and replaced with a real/plausible `$ npm run build` line.
|
||||||
|
- Public SEO/intent pages have been added:
|
||||||
|
- `/minecraft-server-hosting`
|
||||||
|
- `/modded-minecraft-hosting`
|
||||||
|
- `/browser-dev-environment`
|
||||||
|
- Metadata has been added or refreshed for Home, Features, Pricing, FAQ, About, Support, and the three SEO landing pages.
|
||||||
|
- FAQ has been expanded around platform positioning, dev environments, Minecraft, mods, datapacks, local install expectations, backups/restores, and plan limits.
|
||||||
|
- Build and lint reportedly pass after the marketing/SEO changes with the same existing unrelated warnings.
|
||||||
|
|
||||||
|
## Current mobile status
|
||||||
|
- The public and dashboard surfaces are not yet considered mobile-optimized.
|
||||||
|
- Mobile launch pass should focus on usability rather than redesign:
|
||||||
|
- no horizontal scroll at common mobile widths
|
||||||
|
- CTA buttons stack cleanly
|
||||||
|
- pricing cards stack cleanly
|
||||||
|
- auth forms remain readable
|
||||||
|
- dashboard server cards do not clip actions/status
|
||||||
|
- console/file/backup panels are usable enough or clearly limited on mobile
|
||||||
|
|
||||||
## Readiness / operation UI
|
## Readiness / operation UI
|
||||||
- Portal consumes API-normalized state.
|
- Portal consumes API-normalized state.
|
||||||
- Portal understands:
|
- Portal understands:
|
||||||
@ -45,6 +87,7 @@ This file records what is implemented now.
|
|||||||
- delete
|
- delete
|
||||||
- Portal uses API routes, not direct agent calls.
|
- Portal uses API routes, not direct agent calls.
|
||||||
- backup metadata is normalized and displayed when the API includes metadata fields.
|
- backup metadata is normalized and displayed when the API includes metadata fields.
|
||||||
|
- backup/restore actions now provide user feedback and progress/elapsed time during active operations.
|
||||||
|
|
||||||
## Console / action gating
|
## Console / action gating
|
||||||
- console command transport uses POST JSON through API.
|
- console command transport uses POST JSON through API.
|
||||||
@ -54,7 +97,9 @@ This file records what is implemented now.
|
|||||||
|
|
||||||
## Billing / auth / onboarding
|
## Billing / auth / onboarding
|
||||||
- billing UI alignment exists with the newer billing state model.
|
- billing UI alignment exists with the newer billing state model.
|
||||||
|
- billing plan-limit gating has been observed in Portal create flow.
|
||||||
- forgot/reset password flow exists.
|
- forgot/reset password flow exists.
|
||||||
|
- logged-in change-password flow exists.
|
||||||
- first-login onboarding flow exists.
|
- first-login onboarding flow exists.
|
||||||
- Next 16 / current TypeScript cleanup included fixes around nullable normalization and search-param/Suspense usage in affected pages/components.
|
- Next 16 / current TypeScript cleanup included fixes around nullable normalization and search-param/Suspense usage in affected pages/components.
|
||||||
|
|
||||||
@ -81,3 +126,4 @@ This file records what is implemented now.
|
|||||||
## Still true
|
## Still true
|
||||||
- Portal should track API auth / JWT behavior closely because API-side token hardening can require Portal compatibility verification.
|
- Portal should track API auth / JWT behavior closely because API-side token hardening can require Portal compatibility verification.
|
||||||
- Portal cleanup should remain behavior-preserving; build/lint green status is part of the current baseline.
|
- Portal cleanup should remain behavior-preserving; build/lint green status is part of the current baseline.
|
||||||
|
- Mobile responsiveness is still an open Portal validation/polish item.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user