Senior Full-Stack E-Commerce Developer

## Senior Full-Stack Developer Needed to Launch Editorial E-Commerce and Membership Website I am launching **Young Harlot**, a counterculture editorial and commerce platform focused on female disruptors, revolutionaries, artists, writers, scientists, musicians, and iconoclasts. The website will combine: * Original digital books, dossiers, guides, and downloadable products * A searchable editorial archive * Books, novels, music albums, films, and affiliate recommendations * Paid memberships * Customer accounts * Saved items and reading lists * Secure digital downloads * USD and EUR payments * Newsletter and marketing integrations A working front-end mock, logo, brand direction, initial product catalogue, pricing model, technical plan, and detailed handover package already exist. You will not be starting from a blank page. I need one capable developer to turn the existing mock into a secure, production-ready website and help launch it quickly. ### Contract details * **Contract:** Hourly * **Rate:** **$12–$18 USD per hour** * **Location:** Worldwide * **Initial workload:** Approximately 20 hours per week * **Initial duration:** 4–8 weeks * **Possible ongoing work:** Maintenance, SEO, analytics, affiliate integrations, and new product development This is an international remote contract. Proposals substantially above the listed hourly range will not be considered for the initial build. ## Preferred technical stack The proposed stack is: * Cloudflare Pages * Cloudflare Workers * Cloudflare R2 * Stripe Checkout and subscriptions * Supabase authentication and database * GitHub * Resend for transactional email * Kit for newsletters * Google Analytics * Google Search Console * Microsoft Clarity You may recommend a different stack, but you must explain why it is faster, more secure, easier to maintain, or less expensive. ## Core responsibilities ### 1. Production deployment * Review the existing website files and documentation * Place the project under Git version control * Create staging and production environments * Deploy the site to a custom domain * Configure HTTPS, DNS, redirects, caching, and security headers * Ensure the website works across modern desktop and mobile browsers ### 2. Content management system Create an administrative system that allows non-technical users to add, edit, publish, and organize: * Female disruptor profiles * Original Young Harlot products * Books and nonfiction * Novels and fiction * Music albums * Films and documentaries * Affiliate links * Authors, artists, movements, countries, eras, and categories * Product files and digital editions * Homepage and editorial features Content must be editable without modifying source code. ### 3. Search and discovery Implement search and filtering across the full archive. Users should be able to search or filter by: * Person * Historical period * Country or region * Discipline * Political movement * Book * Author * Musician * Album * Film * Product type * Free or paid content Search results should support internal linking and search-engine indexing. ### 4. Stripe payments Implement: * Stripe Checkout * One-time digital purchases * USD and EUR pricing * Monthly memberships * Annual memberships * Promotional codes * Stripe Customer Portal * Successful-payment handling * Failed-payment handling * Subscription cancellation * Refund handling * Secure Stripe webhooks * Test-mode and live-mode configuration The system must correctly grant and remove access based on payments, cancellations, refunds, and subscription status. ### 5. Customer accounts Implement: * Registration * Login * Email verification * Password recovery * Customer profile * Saved products * Saved books and reading lists * Order history * Purchase history * Subscription status * Member-only archive access * Secure logout and session management Supabase Row Level Security or an equivalent access-control system must be properly configured. ### 6. Secure digital delivery Purchased files must not be publicly accessible through permanent URLs. Implement: * Private file storage * Product entitlement validation * Expiring download links * Download access from customer accounts * Automated purchase emails * Download confirmation emails * Administrative ability to replace product files * Administrative ability to resend access * Correct access removal after refunds or entitlement expiration ### 7. Affiliate commerce The website will contain recommendations for: * Books * Audiobooks * Music * Films * Documentaries * Museum material * Cultural products * City guides * Travel resources Implement an editable affiliate-link system that supports: * Multiple retailers per item * Retailer-specific buttons * Country-specific links where practical * Affiliate disclosures * Click tracking * Link replacement through the CMS * Internal reports showing which links receive traffic Affiliate links must not be hard-coded throughout the website. ### 8. Newsletter and transactional email Implement: * Newsletter signup * Kit integration * Welcome-email flow * Transactional email through Resend or a comparable provider * Account-verification emails * Password-reset emails * Purchase confirmations * Download notifications * Subscription confirmations * Cancellation notices * Failed-payment notifications Email templates should match the Young Harlot brand. ### 9. SEO and analytics Implement: * Search-friendly URLs * Page titles and meta descriptions * Canonical URLs * Open Graph metadata * XML sitemap * Robots.txt * Structured data * Internal linking * Google Analytics * Google Search Console * Microsoft Clarity * Purchase and signup conversion events * Affiliate click events * Cookie and analytics consent Relevant structured-data types may include: * Person * Book * MusicAlbum * Article * Product * Organization * BreadcrumbList ### 10. Legal and operational pages Add and structure: * Terms of service * Privacy policy * Refund policy * Digital-products policy * Membership terms * Affiliate disclosure * Copyright and rights policy * Contact page * Image-credit and source-attribution system Legal text will be reviewed separately, but the technical implementation must support it. ## Existing materials provided The selected developer will receive: * Functional front-end website mock * Responsive design files * Brand logo * Brand direction * Product catalogue * Initial prices * Technical implementation plan * Account and infrastructure plan * Launch-control workbook * Contractor handover brief * Acceptance-test requirements The current front end may be improved where necessary, but this is primarily an implementation and launch project, not a complete redesign. ## Required experience You should have direct experience with several of the following: * Stripe Checkout * Stripe subscriptions * Stripe webhooks * Supabase authentication * Supabase Row Level Security * PostgreSQL * Cloudflare Pages * Cloudflare Workers * Cloudflare R2 * Protected digital downloads * Membership websites * Editorial CMS systems * Transactional email * Affiliate-commerce systems * Technical SEO * Secure production deployments Experience with digital publishing, media archives, online magazines, membership products, or downloadable products is preferred. ## Security and ownership requirements All production accounts will be owned by me. You will receive access through provider invitations and limited user roles. I will not share: * Bank-login credentials * Master passwords * Recovery codes * Two-factor authentication codes * SSN or identity documents * Private banking information You must not store secret keys in: * Browser code * Public repositories * Spreadsheets * Shared documents * Unencrypted files Secrets must be stored in secure environment variables or provider secret-management systems. The final source code, database schema, configuration, documentation, and deployment process must be transferred to accounts I own. No critical component may remain dependent on a contractor-owned account. ## Acceptance criteria The project will not be considered complete until a test user can: 1. Create an account 2. Verify their email address 3. Log in and log out 4. Recover a forgotten password 5. Purchase a digital product in Stripe test mode 6. Receive a purchase confirmation 7. Access the purchased product securely 8. Download the file through an expiring link 9. View the purchase in account history 10. Save an item 11. Subscribe to the monthly or annual membership 12. Access member-only content 13. Cancel the membership 14. Lose access correctly after cancellation, expiration, or refund 15. Receive the correct transactional emails The administrator must also be able to: * Add a new disruptor profile * Add a new book * Add a new album * Add a new affiliate link * Add a new digital product * Upload or replace a product file * Edit prices * Issue or process a refund * View customers and entitlements * Publish and unpublish content ## Documentation required At completion, provide: * Source-code repository * Database schema * Database migrations * Environment-variable list * Deployment instructions * Local-development instructions * Backup procedure * Recovery procedure * Stripe webhook documentation * CMS administration guide * Account and permissions list * Recorded walkthrough of the administrative system ## Paid technical test The engagement will begin with a **paid five-hour test**. During the test, you will: * Review the existing website and handover files * Deploy a staging version * Identify architectural risks * Provide an implementation plan * Demonstrate either: * a working Supabase authentication flow, or * a working Stripe test-mode checkout flow Continued work will depend on the quality of the test. ## Application instructions Begin your proposal with: **I have reviewed the Young Harlot production scope.** Then provide: 1. Three relevant live websites or applications you personally worked on 2. Your exact role on each project 3. Your experience with Stripe webhooks 4. Your experience with subscriptions 5. Your experience with secure digital downloads 6. Your experience with Supabase Row Level Security 7. Your proposed technical architecture 8. What you can complete within the first 40 hours 9. Your estimated total number of hours 10. Your weekly availability 11. Your hourly rate 12. Your earliest start date 13. Whether you are an independent freelancer or part of an agency 14. Your post-launch warranty or support period Generic proposals that do not address the technical requirements will be rejected. The objective is to launch a reliable MVP quickly, while preserving security, ownership, and the ability to expand the platform later.