A business-service website connecting public content, product and announcement management, administrator authentication, PostgreSQL and cloud image storage.
This case study only uses functions verifiable in the repository. Unverified performance percentages from the README are intentionally excluded, and business contact details are not duplicated here.
ProblemA service website becomes costly to maintain when every product or announcement update requires a code change and redeploy.DecisionUse Vue 3 / TypeScript for the public site and CMS, with Supabase Email Auth, PostgreSQL, Storage and RLS-backed data access.EvidenceThe public site sharegift.tw is live under the 大倉代領 shareholder-gift service brand; the repository verifies 2 primary CMS flows, 3 Supabase capabilities (Auth/Database/Storage), 9 Schema.org types and GitHub Actions CI/CD.NextNext improvements could add admin auditability, content revision history and richer management workflows; the portfolio does not claim these exist today.
01 / Product scope
A public site plus a CMS that keeps the delivered product maintainable.
2Primary CMS flows: announcements and products
3Supabase capabilities: Auth, Database and Storage
9Schema.org types documented in the repository README
CI/CDDeployment workflow managed with GitHub Actions
02 / Architecture
The public experience and admin workflow share one managed data layer.
Vue 3 UIServices, plans, products, announcements and contact flow
Admin CMSAuthenticated create, edit, delete and publish operations
SupabaseEmail Auth, PostgreSQL and Row Level Security
StorageCloud storage for product images and content assets
The portfolio prefers a build-time capture of the production site sharegift.tw currently operated by 大倉代領; if the public site cannot be captured, it falls back to the reviewed architecture visual. The build never accesses authenticated admin pages.
03 / Public website
Responsive Service SiteVue 3, TypeScript, Vite and Tailwind are used for a responsive business-facing experience.Service & Product ContentThe public site includes service plans, product gallery, announcements, contact and recruitment content.SEO FoundationThe repository includes meta handling, sitemap, robots.txt and JSON-LD structured data.Media DeliveryThe README documents responsive images and AVIF / WebP / JPEG fallback support.
04 / Admin operations
Routine content changes move from source-code edits into an authenticated workflow.
Administrators sign in with Supabase Email / Password Authentication.
Announcements support create, edit and delete operations with types and tags.
Products can be created, edited, categorized and switched between published and unpublished states.
Images are stored in Supabase Storage while content records live in PostgreSQL.
Row Level Security is part of the data-access boundary.
05 / Engineering choices
Typed FrontendVue Composition API and TypeScript separate views, composables and data types.Managed BackendSupabase combines Auth, PostgreSQL and Storage to reduce infrastructure overhead.Operational CMSNon-developers can maintain announcements and products without editing source code.Deployment WorkflowGit version control and GitHub Actions provide a repeatable deployment path.
06 / Takeaway
A business website is more useful when the business can keep operating it after delivery.
The project connects the public frontend with content management, identity, data storage, media storage and SEO. Its main distinction from a static marketing page is the maintainable admin workflow behind the public experience.
