INTL
Freelancer
전문가
외주
원격 가능
CodeIgniter 4 Developer for E-Commerce Rebuild (CI3 → CI4 Clean-Slate)
예산
$250~$750 USD
예상 기간
2~3주
난이도
전문가
기술 스택
PHP
CodeIgniter 4
Tailwind CSS
Alpine.js
JavaScript
CI4 Shield
Stripe API
SQL
GitHub
AI 분석 요약
라이브 독일 이커머스 웹사이트를 CodeIgniter 3에서 CodeIgniter 4로 클린 슬레이트 방식으로 재구축하는 프로젝트입니다. 개발자는 엄격한 사양에 따라 기존 비즈니스 로직 포팅, Tailwind CSS 및 Alpine.js를 활용한 UI 재구현, Stripe 결제 통합, 그리고 2~3주 내 라이브 환경 배포를 단독으로 수행해야 합니다.
프로젝트 원문 설명
# CodeIgniter 4 Developer for Spec-Driven E-Commerce Rebuild (CI3 → CI4)
## Read this first
**One individual freelancer. One contract. One outcome.**
If you bid, you personally write every line of code and own this project from first commit to production. No agencies. No subcontracting. No "dedicated developer slots." No team assignments. Discovery = contract terminated without payment.
If you represent an agency or a "team of one," this isn't for you.
**Budget: 1.000–1.500 EUR fixed price for the complete project.** Payment on delivery of a working CI4 shop in production. No milestones, no partial payments, no upfront.
---
## What this project is
Rebuilding a live German e-commerce shop (topschaum.de, custom-cut foam products — mattresses, cushions, acoustic foam) from CodeIgniter 3 to a clean CodeIgniter 4 codebase. The shop generates revenue and must stay online during the transition.
The preparation is done. What remains is execution.
### What's already in place
- **13 feature specs**, 5.246 lines, implementation-ready
- **18 Architecture Decision Records** — framework, auth, payment, cart, theming, all decided
- **CI3 reference codebase** fully documented (35+ files: controller/model/view/route maps, DB schema)
- **Contracts**: naming conventions, URL map, DB schema, service interfaces — frozen
- **Project Constitution (CLAUDE.md)** with 10 strict implementation rules
- **Blank CI4 v4.7.2** running on target server (DomainFactory, PHP 8.3.30), SFTP ready
- **Stripe integration fully specified** — Payment Intents, Express Checkout, webhook handling, duplicate-PI prevention all documented. Pattern proven in production on another shop of mine; for this project the exact implementation is pre-planned.
- **Clickable frontend prototype in Lovable** — live preview of target layout, components, responsive behavior:
**https://id-preview--50498af7-392c-40d3-899f-d6523746cb61.lovable.app/**
Prototype is built in React for preview only. You rebuild the UI in Tailwind CSS + Alpine.js — layout, components, interactions defined by the prototype; implementation is yours. Header/footer follow the existing CI3 template structure; product and category pages follow the prototype.
**You do not design. You implement, integrate, test, and deploy.**
The volume of prep work should tell you how I expect this executed. If it doesn't, this isn't for you.
---
## Timeline & working model
- **Timeline:** 2–3 weeks from contract signing to production go-live. Focused execution, not open-ended engagement.
- **Language:** English preferred. German welcome if you speak it.
- **Working setup:** you work directly in the GitHub repos I provide (CI4 write, CI3 read-only reference). Every feature a branch, every merge a PR against main — so I can review code as it's written, not at the end.
- **Communication:** async primary via Slack or WhatsApp (shared channel for day-to-day questions). GitHub PRs for code review. One short kickoff call at the start to verify fit and walk through repos/specs/prototype. After that, async unless something needs a call.
- **Time zone:** any, but a few hours of overlap with European business hours (UTC+1) so questions don't sit for 12+ hours.
- **Testing:** unit tests required for `GeometryService` (all 25+ shapes verified against reference values I provide). Integration testing on dev server before every PR merge. Final production verification is your responsibility before go-live.
- **Production cutover:** CI4 runs on `ci4.topschaum.de` during development. DB schema frozen = straight SQL dump at go-live. DNS switch executed jointly, scheduled for weekend low-traffic window. Old CI3 readable for 30 days as rollback.
---
## Why one developer, end-to-end
The work breaks into three parts:
1. **Port CI3 PHP business logic (controllers, models) into CI4 structure.** The existing code works. Naming, namespaces, loader syntax, service-layer patterns change — the logic doesn't.
2. **Replace 9 theme directories with ONE responsive template.** Tailwind + Alpine.js. Views reduced from 950 to ~50–80. UI rebuilt against the Lovable prototype (React → Tailwind/Alpine translation). Stripe integration built to spec.
3. **Integrate, test, and deploy to production without breaking the live shop.** Catch what the earlier steps got subtly wrong. Verify pricing against real product data. Verify URL preservation. Cut over without downtime.
Parts 1 and 2 are careful, spec-driven work. Part 3 is where a real developer earns their fee — and part 3 only works if the same person did parts 1 and 2. You can't hand someone a half-built system and ask them to fix problems they didn't create.
One contract, one developer, start to finish.
---
## Target architecture
- CodeIgniter 4.7.2 on PHP 8.2+
- Tailwind CSS + Alpine.js — **NO jQuery, NO Bootstrap**
- CI4 Shield for auth — **NOT Ion Auth**
- Stripe Payment Intents + Express Checkout (Two-Element Pattern, webhook-driven)
- Mobile-first, ONE responsive template
## Read this first
**One individual freelancer. One contract. One outcome.**
If you bid, you personally write every line of code and own this project from first commit to production. No agencies. No subcontracting. No "dedicated developer slots." No team assignments. Discovery = contract terminated without payment.
If you represent an agency or a "team of one," this isn't for you.
**Budget: 1.000–1.500 EUR fixed price for the complete project.** Payment on delivery of a working CI4 shop in production. No milestones, no partial payments, no upfront.
---
## What this project is
Rebuilding a live German e-commerce shop (topschaum.de, custom-cut foam products — mattresses, cushions, acoustic foam) from CodeIgniter 3 to a clean CodeIgniter 4 codebase. The shop generates revenue and must stay online during the transition.
The preparation is done. What remains is execution.
### What's already in place
- **13 feature specs**, 5.246 lines, implementation-ready
- **18 Architecture Decision Records** — framework, auth, payment, cart, theming, all decided
- **CI3 reference codebase** fully documented (35+ files: controller/model/view/route maps, DB schema)
- **Contracts**: naming conventions, URL map, DB schema, service interfaces — frozen
- **Project Constitution (CLAUDE.md)** with 10 strict implementation rules
- **Blank CI4 v4.7.2** running on target server (DomainFactory, PHP 8.3.30), SFTP ready
- **Stripe integration fully specified** — Payment Intents, Express Checkout, webhook handling, duplicate-PI prevention all documented. Pattern proven in production on another shop of mine; for this project the exact implementation is pre-planned.
- **Clickable frontend prototype in Lovable** — live preview of target layout, components, responsive behavior:
**https://id-preview--50498af7-392c-40d3-899f-d6523746cb61.lovable.app/**
Prototype is built in React for preview only. You rebuild the UI in Tailwind CSS + Alpine.js — layout, components, interactions defined by the prototype; implementation is yours. Header/footer follow the existing CI3 template structure; product and category pages follow the prototype.
**You do not design. You implement, integrate, test, and deploy.**
The volume of prep work should tell you how I expect this executed. If it doesn't, this isn't for you.
---
## Timeline & working model
- **Timeline:** 2–3 weeks from contract signing to production go-live. Focused execution, not open-ended engagement.
- **Language:** English preferred. German welcome if you speak it.
- **Working setup:** you work directly in the GitHub repos I provide (CI4 write, CI3 read-only reference). Every feature a branch, every merge a PR against main — so I can review code as it's written, not at the end.
- **Communication:** async primary via Slack or WhatsApp (shared channel for day-to-day questions). GitHub PRs for code review. One short kickoff call at the start to verify fit and walk through repos/specs/prototype. After that, async unless something needs a call.
- **Time zone:** any, but a few hours of overlap with European business hours (UTC+1) so questions don't sit for 12+ hours.
- **Testing:** unit tests required for `GeometryService` (all 25+ shapes verified against reference values I provide). Integration testing on dev server before every PR merge. Final production verification is your responsibility before go-live.
- **Production cutover:** CI4 runs on `ci4.topschaum.de` during development. DB schema frozen = straight SQL dump at go-live. DNS switch executed jointly, scheduled for weekend low-traffic window. Old CI3 readable for 30 days as rollback.
---
## Why one developer, end-to-end
The work breaks into three parts:
1. **Port CI3 PHP business logic (controllers, models) into CI4 structure.** The existing code works. Naming, namespaces, loader syntax, service-layer patterns change — the logic doesn't.
2. **Replace 9 theme directories with ONE responsive template.** Tailwind + Alpine.js. Views reduced from 950 to ~50–80. UI rebuilt against the Lovable prototype (React → Tailwind/Alpine translation). Stripe integration built to spec.
3. **Integrate, test, and deploy to production without breaking the live shop.** Catch what the earlier steps got subtly wrong. Verify pricing against real product data. Verify URL preservation. Cut over without downtime.
Parts 1 and 2 are careful, spec-driven work. Part 3 is where a real developer earns their fee — and part 3 only works if the same person did parts 1 and 2. You can't hand someone a half-built system and ask them to fix problems they didn't create.
One contract, one developer, start to finish.
---
## Target architecture
- CodeIgniter 4.7.2 on PHP 8.2+
- Tailwind CSS + Alpine.js — **NO jQuery, NO Bootstrap**
- CI4 Shield for auth — **NOT Ion Auth**
- Stripe Payment Intents + Express Checkout (Two-Element Pattern, webhook-driven)
- Mobile-first, ONE responsive template
Freelancer에서 원본 확인
원본 보기