I need an EYEZY ultimate theme website via Shopify. I will start with only 4 product items. If you are not familiar with that theme there are some YouTube videos. Please let me know if you’re are able to help.

Full-Stack Developer | Freelance, Project-Based About Our Requirement We are seeking an experienced full-stack developer to work with us in transforming an early-stage concept into a polished, market-ready web and mobile application. This is a long-term opportunity to play a key role in shaping and continually improving the product architecture, user experience, and technical implementation while collaborating closely with the founders. Our objective is to create a subscription-based educational technology platform that helps families and students to better organize and manage academic information through a simple, intuitive interface The ideal solution will securely integrate commonly used educational tools and systems into a student dedicated web and mobile app providing users with a streamlined experience that reduces complexity and improves day-to-day organization. The project has progressed beyond the concept stage, with core functionality, a preliminary dashboard and workflows already defined. We are now looking for a developer with the skills to refine the platform, build a scalable and secure architecture, integrate with appropriate third-party services and APIs, and prepare the product for commercial launch. The Opportunity Based on the parameters noted above, we are seeking a mid-level full-stack developer to work directly with the project owners (non-technical but closely involved in every design decision) to help us finalize or vision and providing †he expertise to scale up our platform by applying secure real data integrations, adding durable data storage, and improving reliability — while preserving and enhancing the ease of functionally and user accessibility. Project Scope (Phase 1) • Interact with the founders to develop the means to migrate dedicated data from multiple platforms into our unique web based/mobile App. • Assist the founders in the creation and deployment of hosting and custom domain configuration. • Design and build a lightweight backend + database layer (e.g. Vercel serverless functions with a hosted Postgres database, or similar) to replace localStorage-only persistence • Evaluate whether to keep the current vanilla HTML/CSS/JS front end or migrate to a lightweight framework (e.g. Next.js), and implement that recommendation • Maintain and extend the accessibility standards already established (WCAG contrast, dyslexia-friendly typography, reduced-motion support) — nothing developed should regress readability for a dyslexic user • Set up a system of basic monitoring/error logging so issues surface before the subscribers are negatively (in terms or platform use) affected. • Document the codebase and deployment process clearly enough for a non-technical owner to follow Required Skills & Experience • 3+ years of professional full-stack development experience • Strong JavaScript/TypeScript, both front-end and back-end (Node.js) • Experience building and securing REST APIs, including OAuth 2.0 integrations with third-party services • Experience with serverless deployment (Vercel, Netlify, AWS Lambda, or similar) • Comfortable designing a database schema and working with a hosted database (Postgres, MySQL, or similar managed service) • Solid understanding of Git/GitHub workflows • Working knowledge of web accessibility standards (WCAG 2.1 AA or better) • Able to work independently against a scoped project brief with minimal day-to-day oversight • Experience integrating with EdTech platforms • Experience designing for neurodivergent users (dyslexia, ADHD, or similar) or prior accessibility-focused UX work • Familiarity with Next.js or similar lightweight React frameworks • Comfortable explaining technical tradeoffs to non-technical stakeholders Working Style This project is owned by a student’s parent, not a technical team — clear, patient, jargon-free communication matters as much as the code. You should be comfortable: • Proposing options in plain language and guiding the founders to understanding critical issues in order to (as a team) make informed decisions • Working within an existing, already-designed visual system rather than starting from scratch • Delivering in small, reviewable increments rather than one large handoff at the end Engagement Details Type: Freelance, project-based (fixed scope with a defined set of ending objectives) and a long-term potential for follow-on work) Location: Remote Estimated timeline: [Phase 1 – target implementation date – August 31, 2026] [Phase 2 – to include platform refinements based of in-use feedback and scaling the platform up to allow for beta testing of 10-20 users] Budget: [Phase 1 - $ 2,000.00] [Phase 2 - $ 1,500.00] Start date: [Immediately] How to Apply Please provide relevant past projects (especially any EdTech, accessibility, or OAuth/API integration work), your estimated timeline and desired rate (fixed or hourly) for the scope above, and any questions or alternative approaches you'd suggest for the backend/data layer. Please Note: A signed Non-Disclosure Agreement (NDA) is required before the start of this project engagement. This ensures that all confidential information shared throughout the project remains protected and that both parties have a clear understanding of their confidentiality obligations.

We are a small estate planning law firm in Texas looking for a Lawcus CRM + Zapier/Make consultant to help with a controlled workflow cleanup and implementation project. We already have internal project-management support and a draft cleanup framework. We are not looking for a general operations consultant or someone to redesign everything from scratch. We are looking for someone with CRM automation experience who can help verify what is currently live, troubleshoot Lawcus/Zapier/Make issues, and execute narrow approved technical tasks. This is a law firm environment, so confidentiality and careful change control are very important. Initial Project The initial engagement will be a small paid test project of approximately three to five hours. The goal of the test project is to review one limited part of our Lawcus/Zapier setup, identify what is live, flag risks or issues, and recommend or complete only approved changes. Possible systems involved include: * Lawcus CRM; * Zapier or Make; * DecisionVault; * OpenPhone; * Google Drive; * Dropbox Sign; * ClickUp; * scheduling tools; * Missive or Gmail. Initial work may include: 1. Reviewing our existing Lawcus Inventory Sheet and Matter Hygiene/Cleanup Handoff; 2. Verifying selected items against the live Lawcus setup; 3. Identifying which stages, task templates, automations, fields, tags, and integrations are currently live; 4. Flagging anything outdated, duplicative, unclear, risky, or dependent on a former team member; 5. Reviewing Lawcus/Zapier/Make automations for reliability or broken connections; 6. Helping implement only specific approved changes; 7. Documenting all changes made; 8. Providing a short written summary and, if helpful, a Loom/video walkthrough. What This Project Is Not This is not: * a broad operations role; * client communication; * legal judgment; * a full CRM rebuild; * bulk editing without approval; * deleting or changing live automations without approval; * independent decision-making about client matters. No broad live changes should be made without written approval. Required Experience Please apply only if you have experience with at least some of the following: * Lawcus CRM; * Zapier or Make; * CRM pipeline/stage cleanup; * workflow automation mapping; * law firm CRMs or professional-services CRMs; * intake workflows; * task/template cleanup; * Google Sheets or Excel-based audit tracking; * clear documentation of system changes. Lawcus experience is strongly preferred. If you do not have Lawcus experience but have strong CRM + Zapier/Make experience, please explain why your experience transfers well. Ideal Candidate The ideal person is: * detail-oriented; * careful with confidential information; * comfortable documenting every change; * willing to work from an existing plan; * able to say “this needs approval before changing”; * not someone who makes broad changes first and explains later; * good at translating messy CRM workflows into clear technical next steps. Budget / Structure This will be hourly. I would like to start with a small paid test project capped at three to five hours unless additional time is approved in writing. If the test project goes well, there may be additional implementation work. Questions for Applicants Please answer these in your proposal: 1. Have you worked directly in Lawcus before? If yes, what did you do? 2. Have you built or reviewed Zapier/Make automations connected to a CRM? 3. Have you worked with a law firm or another confidential professional-services business? 4. How would you approach this project without making risky live changes? 5. What would you want to review first: pipelines, task templates, automations, fields/tags, or integrations? Why? 6. Are you comfortable documenting every change and providing a short written summary or Loom walkthrough? 7. What is your hourly rate, and how many hours would you suggest for an initial review/test project? Deliverable for Initial Test Project At the end of the initial project, I want: * a verified list of what is currently live in the selected Lawcus/Zapier workflow; * recommended keep/revise/delete/defer items; * a list of risks or unknowns; * a list of changes made, if any; * a list of changes that require approval before implementation; * and a recommended next implementation step.

I need a Discord bot built that posts positive expected value (+EV) sports betting picks to a channel, plus esports match schedules/scores. I have the full technical spec already written — APIs picked, EV formula defined, architecture outlined. This is integration work, not research. What's provided: Working API keys for The Odds API (sports odds) and PandaScore (esports stats) — I'll provide on hire Complete EV calculation formula (Python, ready to use) Full architecture spec (polling schedule, caching approach, bookmaker lists) Core deliverables (must-have, fixed price): Discord bot that connects to my server Scheduled polling (1-2x daily, not live) of The Odds API for sports moneylines + player props EV calculation comparing soft-book odds (DraftKings/FanDuel/Caesars) against Pinnacle as the sharp reference Caching layer (database) so the bot never calls the API live per Discord command Bot posts flagged +EV picks to a designated channel, above a configurable EV threshold PandaScore integration for esports match schedules/results posted to a separate channel Basic error handling with retry/backoff (no runaway API costs) Documentation: how to run it, how to add new sports/leagues, how to change the EV threshold Stretch goal (only if time allows within budget — not required): OddsPapi integration for esports moneyline EV detection (this API is unverified/free-tier, so treat as experimental) Tech preferences: Python or Node.js, whichever you're stronger in. Open to your hosting recommendation (needs to run 24/7 cheaply). Budget & Payment Structure: $500 fixed price, split into milestones Milestone 1 ($150) — Foundation: Discord bot connects to server, The Odds API integration pulling live sports odds data, caching layer working. Paid on demo of working data pull + bot online in server. Milestone 2 ($200) — Core Logic: EV calculation implemented and verified accurate against manual spot-checks, picks posting to Discord channel automatically on schedule. Paid on demo of at least 3 correctly-calculated +EV picks posted live. Milestone 3 ($150) — Esports + Polish: PandaScore esports schedule/results integration, error handling/retry logic, documentation delivered. Paid on final delivery + handoff call. To apply: Tell me your estimated hours for each milestone, and confirm you've worked with Discord bots + REST API integrations before.

OVERVIEW We are a technical advisory firm that partners with VC-backed companies to design, build, and scale their engineering foundations. We embed with our clients as a core part of their technical team, not as outside consultants handing over a document, but as engineers who own the outcome alongside them. Our current client is a VC-backed company operating in the auto logistics space. They're at an exciting and critical stage: they have product-market fit, they have backing, and now they need to build the production infrastructure to match their ambitions. We've been brought in to lead that build, and we're looking for a senior full stack engineer to join us for it. This is a greenfield backend API platform built in TypeScript on Node.js with Express or Fastify, and you'd be involved from the very beginning. That means shaping the architecture, setting the patterns, and building something that will need to handle real production load in a fast-moving, operationally complex industry. The backend we're building needs to be reliable, well-structured, and built to grow. If you want to do meaningful backend work on a greenfield codebase, in a real industry with real complexity, working with a team that has high standards, this is the opportunity. WHAT YOU'LL BE BUILDING A production-grade backend API platform in TypeScript on Node.js, using Express or Fastify. Because we're starting from scratch, the early decisions carry significant weight and you'll be part of making them. API architecture, project structure, middleware conventions, authentication approach, error handling, observability, data access patterns: these are all on the table and we want engineers who have opinions about them informed by experience. Day-to-day you'll be writing and reviewing TypeScript, contributing to architecture and design discussions, collaborating with the team on Slack, and joining at least one Zoom sync per week with the broader team and client stakeholders. WHAT WE'RE LOOKING FOR - 5 to 10 years of professional software engineering experience with a strong backend or full stack background. Specifically: - Fluent in TypeScript with a solid working knowledge of the Node.js runtime, including async patterns, error propagation, and performance characteristics, not just the surface API - Hands-on Express and/or Fastify experience with real APIs built using them, a clear understanding of their trade-offs, and the ability to make informed structural decisions without needing to be guided - A track record of shipping and operating production systems, having been accountable for something running live, having handled production incidents, and thinking seriously about reliability, logging, and failure modes. - Comfort operating in a greenfield environment with some ambiguity, able to ask the right questions, help define what isn't yet defined, and take ownership of outcomes rather than waiting for a fully formed spec. - Strong English communication skills, written and spoken. We're a distributed team, async-first on Slack, and we interface directly with a client whose business is moving fast. Clear communication is as important as clean code US-based strongly preferred with meaningful overlap with US business hours required for team and client collaboration NICE TO HAVE - Cloud infrastructure experience (AWS, GCP, or Azure) - Familiarity with authentication protocols (OAuth 2.0, OIDC) - API versioning strategy experience - CI/CD pipeline experience - Domain familiarity with logistics, fleet management, or supply chain systems is a genuine bonus HOW WE WORK We are a tight team with high standards and low tolerance for vague communication or dropped balls. Slack is our primary channel, async-first with responsiveness expected during working hours. We sync on Zoom at least weekly, more often during active design and planning phases. We use Jira for our ticket management. You'll receive a Microsoft 365 account on hire for SSO access to all internal and client tooling from day one. We don't micromanage. What we do expect is proactive communication, early flagging of blockers, and the kind of ownership that comes naturally to engineers who treat a codebase as something worth getting right, not just getting done. On a greenfield project with a client at a pivotal growth stage, that distinction matters. HIRING PROCESS - Intro call (15 min) - the firm, the client, the project, your background, and your questions - Technical screen (if applicable, via Coderbyte) - Background check - standard criminal background check required for all hires, no exceptions - Offer and onboarding - Microsoft 365 account and full tooling access provisioned before day one HOW TO APPLY We read every proposal that makes a genuine effort. Please include: - A description of a production backend system you've built, including what it did, the scale it operated at, your specific contributions, and what decisions you made that you're proud of or would revisit today - Your honest assessment of your TypeScript and Node.js depth. We value specifics and self-awareness over a list of buzzwords Links to code, whether GitHub, open source contributions, a portfolio, or anything else that shows us how you think and work We work with companies at inflection points and we hold ourselves and the engineers we bring in to a high standard. If this project sounds like the kind of work you want to do, make that clear in your proposal and tell us why this domain, this stage, and this type of build appeals to you specifically.

I need a React Native developer to help complete and stabilize my social media app, QueFlic, before QA and beta launch. This is not a full rebuild. The app is already built, but it needs missing flows completed, smoother user experience, error handling, and final pre-QA fixes. The app is a social media platform with photo posts, video posts, Live Photo posts, music/location/tag overlays, WordBox polls/Q&A/reactions, comments, messaging, and sharing. Main work needed: 1. Error management Add clear signup/login errors for username already taken, email already used, wrong password, failed login, and network errors. Add upload and post creation error messages. If upload fails, user should see a retry option. If publishing fails, app should not create ghost posts. Permission errors for camera, photos, location, and music should show clear messages instead of crashing or silently failing. 2. Landing pages / overlay destinations Create or complete a music/sound page where users can see posts using the same song or sound. Create or complete a location page where users can see posts tagged at the same location. Make tagged users open their profile. Make WordBox open the correct poll, Q&A, or reaction page. Each page needs clean back navigation. 3. Smooth post creation flow User should be able to upload media, edit, add overlays, preview, publish, and return to the feed/timeline. User should not get stuck in editing screens. New posts should appear correctly after publishing. Basic delete post option should work for the post owner. 4. Live Photo flow Smooth the Live Photo feature so users can add photos into a video timeline, preview the final Live Photo, pause/play, go back to edit, and publish without freezing or getting stuck. 5. QF logo / watermark playback controls Tap QF logo once to pause video or Live Photo. Tap QF logo again to resume/play. Double tap QF logo to restart the video or Live Photo from the beginning. 6. Basic social actions Delete post. Comment on posts. Message option if already built. Share post using the phone’s native share sheet so users can share to Instagram, TikTok, YouTube, text message, or copy link. I want this handled as a fixed-price, milestone-based sprint. First milestone should be a code/app review and written fix plan. After that, we can move into implementation. Budget is $1,000–$1,500 depending on what can realistically be completed. I am looking for someone experienced with React Native, Firebase, media uploads, social app flows, iOS/TestFlight, and Android/Google Play testing. No full upfront payment.

We are looking for help integrating our GHL with our website. The integrations aren't currently working. We have 2 pipelines that should integrate with our website which is Wordpress on Flywheel. We need to update how the site moves visitors to GHL and what happens next. We would like to change it so that a visitor has 2 options, leave a message which adds them to the GHL pipeline OR schedule an appointment. There is a second pipeline that is supposed to send a set of emails over a period of time. I'm not sure this is working. At some later time, we need to get into other lead generation stuff, but for now we just need to fix these current issues. Thanks

GenEnterprises is a healthcare technology company seeking a specialist to validate patient-access APIs. The role involves ensuring seamless integration with healthcare systems and verifying API functionality. The ideal candidate will have experience in healthcare technology and API validation, with a strong understanding of data security and compliance. What you'll do (per vendor) -Discover the vendor's SMART-on-FHIR endpoints from their conformance statement (/metadata) or .well-known/smart-configuration. -Complete a provided configuration file with the correct authorize/token/FHIR endpoints and patient-access scopes. -Run our provided validation harness against the vendor's sandbox and prove the full authorization flow completes end-to-end — either public-client (PKCE) or confidential-client (client secret) depending on the vendor: authorize → code → token exchange → patient context. -Document any vendor quirks (audience value, extra scopes, non-standard discovery, sandbox limits). What we provide -The validation kit (a small Node harness + config template + rules — runs locally). -The sandbox credentials for the vendor: a client_id, plus a client_secret for confidential vendors, and the registered redirect URIs. -Sandbox access details and the specific vendor to start with. Deliverables -A completed connector configuration — patient-scoped only. Public vendors carry no secret; confidential vendors carry only the sandbox secret we provide (never a production secret). -The endpoint-discovery source you used (the /metadata or .well-known URL). -Evidence of a successful sandbox run: the harness "PASS" page/screenshot and console output showing an access token and a resolved patient ID. -Confirmation the registered redirect URI matches the config exactly. -Notes on any vendor-specific quirks. Requirements -Hands-on experience with SMART-on-FHIR patient-access authorization. -Solid understanding of OAuth 2.0 Authorization Code, both PKCE (public client) and client-secret (confidential client) flows, and when each applies. -Comfortable reading FHIR R4 conformance statements to locate endpoints and scopes. -Enough Node.js to run a provided harness (npm install, edit a JSON config, npm start). -Precise and evidence-driven — you prove things work rather than assuming. Nice to have -Prior integration with EHR/health-data vendors (Veradigm/FollowMyHealth, athenahealth, Epic, Cerner/Oracle Health, Aetna, or similar). -Familiarity with patient access APIs and healthcare interoperability standards. What you will NOT have access to (and won't need) -No production systems, no real patient data — everything is sandbox/synthetic. -No access to our codebase or database — the kit is fully standalone. -No vendor account administration — we own the developer registration; you receive the sandbox credentials only. This keeps the engagement clean and low-risk for both sides. An NDA is required before we share the kit. Engagement -Fixed price per vendor. First vendor is a paid pilot (budget: $[SET BUDGET]); strong work leads to ongoing per-vendor engagements. -Remote, flexible hours. Turnaround for the pilot is typically a few days once you have the sandbox credentials. To apply — please answer these (applications without answers will be skipped) -Which EHR vendor sandboxes have you completed a SMART-on-FHIR patient-access OAuth flow against (PKCE or client-secret)? Name them. -Given only a FHIR base URL, how do you find the authorize and token endpoints? -In one or two sentences: what is the difference between a public and a confidential OAuth client, and when would you use PKCE?

Tableau Consultant – Ongoing Dashboard Development & Analytics Partnership About PMMI PMMI is the trade association for the packaging and processing industry, serving over 1,100 member companies and operating major trade shows including the PACK EXPO portfolio. We use Tableau Cloud to power business analytics across our organization, with data sourced primarily from Salesforce (including Fonteva for membership management), as well as third-party platforms and internal systems. What We're Looking For We're not just looking for someone who can configure Tableau — we're looking for a collaborative partner who can sit with us, understand our business needs, and translate complex multi-source data into clean, intuitive visualizations that anyone in our organization can use, from analysts to executives. Scope of Work This is an ongoing engagement with two primary modes of work: Maintain and enhance existing workbooks — We have a suite of production dashboards in Tableau Cloud covering member engagement, revenue and spend analysis, trade show data, and more. You'll be expected to troubleshoot, optimize, and extend these as our data and business needs evolve. New development — We regularly identify new analytics needs across departments. You'll work with us to scope, design, and build net-new dashboards and workbooks as these projects arise. Our data sources span Salesforce objects, Fonteva (membership management), trade show registration systems, third-party APIs, and occasional manual data uploads. Projects often involve blending data across multiple systems into a coherent, executive-ready view. Requirements 4–7 years of hands-on Tableau and Tableau Cloud experience (minimum 3 years considered with exceptional portfolio) Proficient in setting up and modifying Tableau Data Sources Proficient in Tableau Prep Strong knowledge of data blending and table relationships Strong requirements-gathering skills — you should be comfortable leading discovery conversations with non-technical stakeholders Solid grasp of dashboard design and data visualization best practices Nice to Have Experience with Salesforce data structures, Salesforce data sources, and/or SOQL Tableau certification(s) Logistics US-based individuals only — no agencies or offshore teams, please This is a part-time, ongoing freelance engagement with potential to grow You'll be working closely with our IT and data team, and interfacing with business stakeholders across departments How to Apply Please include in your proposal: Links to Tableau Public dashboards or portfolio samples A brief description of a multi-source dashboard project you've built end-to-end Your hourly rate We look forward to finding a long-term partner who grows with us as our analytics program matures.

Here is what we have so far , a zapier website form that once submitted for a ride request triggers my sms approved twilio number to send me a text with the requested ride info ( lighting fast ) what wouldbe better is Twilio Expert to Build Dispatch Broadcast & Lockout System via Functions & Studio Project Description: We run a local Free community micro courtesy shuttle business utilizing a fleet of 6 gas-powered passenger vans. We need a backend developer to build a text-message-based dispatching system using Twilio Studio, Twilio Functions, and Twilio Sync for data tracking. Core Workflow Required: Web Request Ingestion: Webhook takes ride data (Name, Pickup, Dropoff, Resident Status, Pax count). Active Schedule Check: System checks an internal list of active, on-duty drivers (needs an easy way for me to update weekly schedules or toggles). Simultaneous SMS Broadcast: Send a ride text to only the active drivers on-duty right now. First Responder Wins (Lockout Logic): When a driver replies with a number (e.g., "15"), a Twilio Function checks Twilio Sync. If the ride is still unclaimed, lock it to that driver, store their name and their inputted ETA, and mark the ride as "Claimed". Late drivers must get an automated "Already claimed" text back. Customer Interactive Flow: Trigger a Twilio Studio flow to text the customer: "Your ride is confirmed! [Driver Name] will arrive in [ETA] minutes. Reply CANCEL within 3 minutes if you don't want to wait." Handle customer cancellation loops cleanly. Archival: Push all completed or canceled ride data to a permanent history log. Requirements: Deep experience with Twilio Node.js runtime environments. Proven experience managing race conditions via Twilio Sync Maps/Documents. Ability to build clean, well-commented code so non-technical owners can easily swap out driver lists/phone numbers. Step 2: Prepare Your System Specs (Before the First Call) To keep this fast and budget-friendly, hand developer clean blueprint of your data structure on day one. Have an Excel or Google Sheet ready that maps out exactly what you want tracked: Driver Name Driver Phone Shift Day Start Hour End Hour Status (On/Off Duty) Driver 1 +1727xxxxxxxx Monday 08:00 16:00 Active Driver 2 +1727xxxxxxxx Monday 16:00 23:00 Off-Duty “Can we use Twilio Sync to manage this schedule list, or would it be easier to have the Twilio Function pull this table dynamically from a Google Sheet using the Google Sheets API?” Step 3: Execution and Safeguards the milestone payments based on clear deliverables: Milestone 1 (Setup & Simulation): The developer creates the Twilio Sync environment and proves that if they send two simulate driver texts at the exact same second, one gets the ride and the other gets locked out. Milestone 2 (Studio Integration): The customer text sends successfully with the winning driver's name and ETA, and replying "CANCEL" triggers the cancellation text back to the driver. Milestone 3 (Live Beta Test): I stand on the beach with 2 or 3 of my drivers on a Tuesday afternoon. i hit submit on your webpage, watch the phones drop the texts, claim the ride, and verify the customer workflow. let me know what I missed ?