I am looking for an experienced Shopify developer to seamlessly connect our Printify account to our Shopify store. The scope of work includes: syncing the product catalog, ensuring automated order routing works flawlessly, configuring shipping rates between both platforms, and checking that variant images sync correctly. Please share examples of print-on-demand Shopify stores you have previously configured.”

Project Overview:
I need an experienced Wix Studio developer to migrate an existing Wix-created landing page (4 sections) into Wix Studio, integrate a Wistia video embed, and set up the buying experience for a proof-of-concept (POC) product page. All content/copy/Wistia links are finalized and ready to provide — this is primarily a build, integration, and customization (where recommended) job. I need this completed within 21 days. See attached PDF below for Scope of Work, Requirements, Deliverables, Budget

I have a book cover in Canva that I'd like to convert to HTML/CSS so I can re-use it for different books and create them programmatically. It needs to match the existing one perfectly.

I created a custom Wordpress plugin with the help of Chat. It is a job board plus individual job pages that uses an API to send and receive data through my Applicant Tracking System. You can see it here: https://baptistsearchpartners.com/jobs/ . It is live and is the highest trafficked page on my site. It also powers a drop down job application in a custom page for different clients seen here: https://baptistsearchpartners.com/largechurchleadsample/ (scroll to bottom and "Click here to apply") I'm 90% satisfied with it, but I need someone to "look under the hood" to get me across the finish line. 1. Submission of applications takes 12+ seconds. I did code the submit button to give a message for the user to be patient while it submits the application. Still, it's way too long. I'd love to figure out why and resolve the submission time. 2. We get applicants every day that submit it just fine, but I have had a few in the last two weeks email me that they received errors. Could there be a caching issue or some problem that just doesn't work right very occasionally? I can give more details about error messages and browsers later. 3. I would love to be able to track page view stats for each job page. Neither Jetpack or Google seems to be picking up the individual job pages even though they have a unique URL (like https://baptistsearchpartners.com/jobs/?bsp_job_id=51) 4. There is a small issue with the Experience and Educations sections and the currently working buttons that cause users problems if they enter them in a certain way. It's easy to figure out how to fix when you are going through it, but it's annoying. 5. You cannot submit files from cloud services. 6. The Large Church Lead sample where the application shows up in a dropdown is not showing all of the application fields (personal information, file uploads, and custom questions). It did at first, but that seems to have gone away. 7. I'd love suggestions for any other UX improvements. I do have a "Test Job" set up in my ATS that can be a sandbox for it all, but a live job can be used as a test as well.

Hello, I do not know if you can help us or even if I am looking in the right place. We have an inventory system called EPOS (which is from England). Their inventory system at the time was the only one that we could find to do what we needed done. They had a "developer" (in quotes because I'm not sure if that is what you call him) that wrote the code to talk to our EPOS system to our Shopify system. There was a lot of math being coded. We are quilt shop that sells fabric. The fabric is listed in EPOS by the inch. It is then converted to 1/4, 1/2 full yards, etc when a customer sees our listing in Shopify. I hope I haven't lost you yet. The coding also takes the cost from EPOS and converts it over to the cost in Shopify. A major glitch is causing the incorrect math conversion causing our fabric to show exponentially more price wise in our Shopify Store. Is this something you could look at or am I looking at the wrong type of professional perhaps. Thank you, Marla L.

We have Wordpress setup with Elementer plug-in and need some support on making ongoing adjustments.

Overview I have a Next.js website with a newsletter signup form that currently submits directly from the browser to HubSpot's Forms v3 endpoint. I want to add a lightweight LLM-based spam filter that inspects each submission *before* it reaches HubSpot, and silently rejects (or flags) anything that looks like spam/bot/junk input. Current setup - Framework: Next.js (App Router, TypeScript, React client component) - The form component (`NewsletterForm.tsx`) POSTs directly to `https://api.hsforms.com/submissions/v3/integration/submit/[portalId]/[formGuid]` - Fields collected: `firstname`, `lastname` (optional), `jobtitle`, `email` - Portal ID and Form GUID are public form identifiers (no secrets today) What I want you to build 1. Create a server-side API route in the Next.js app (e.g. `app/api/subscribe/route.ts`) that: - Receives the form fields from the client - Runs an LLM spam/quality check (e.g. OpenAI or similar) to classify the submission as legit vs. spam — checking for gibberish names, fake/disposable emails, nonsense job titles, injection attempts, etc. - If legit → forwards the submission to HubSpot (server-side) - If spam → rejects gracefully with a generic message (no HubSpot write) 2. Update the existing `NewsletterForm.tsx` to POST to the new internal API route instead of calling HubSpot directly. 3. Keep the LLM API key server-side only (use an environment variable — never expose it to the client). 4. Preserve the existing UX: loading / success / error states should still work. Deliverables - Working API route with the LLM spam check + HubSpot forwarding - Updated form component - Brief note on which env vars to set (`OPENAI_API_KEY`, etc.) and how to configure them - Clean, typed TypeScript that matches the existing code style Nice to have (optional) - Basic rate limiting / honeypot field as a cheap first line of defense before the LLM call - Configurable spam threshold or a logged "reason" when something is rejected Requirements to apply - Strong Next.js App Router + TypeScript experience - Experience calling an LLM API (OpenAI or equivalent) from a server route - Familiarity with HubSpot Forms API is a plus To apply, please briefly answer: 1. Which LLM/provider would you use and roughly what would it cost per submission? 2. How would you handle the case where the LLM API is slow or down — do you fail open (let it through) or fail closed (block it)? 3. Have you integrated with HubSpot Forms before? (yes/no is fine)

We are seeking a skilled freelancer to build a Shopify B2B webpage for our footwear brand. The ideal candidate will have experience in creating visually appealing and functional e-commerce platforms. Responsibilities include designing a user-friendly interface, integrating payment systems, and ensuring seamless navigation. The project requires a strong understanding of Shopify and B2B e-commerce solutions.

Build polished, performance-conscious React/TypeScript UI for map-driven workflows: 3D entity rendering, real-time status, modal-driven dispatch, complex form ergonomics. Own the UX of multi-step operator flows end-to-end — visual hierarchy, loading/error states, keyboard, accessibility, edge cases. Collaborate on AI-driven features: integrating Claude Agent SDK tool flows, designing prompts and MCP tools, surfacing agent actions and audit logs in the UI. Occasional Python work on FastAPI services when frontend changes need backend hooks. Must-haves 5+ years shipping production React apps with TypeScript. Heavy day-to-day AI tooling — Cursor / Claude / agentic workflows. You move fast with AI, refactor with it, and reason about prompts and tool design (not just autocompletes). Strong UI/UX intuition. You see a Figma or sketch and can ship something that feels right; you push back when the design hurts the user. Works independently and takes initiative — you scope your own work, surface unknowns early, and ship without hand-holding. Detail-oriented — you sweat the loading states, the empty states, the off-by-ones, and the cases everyone else forgot about. Comfort with styled-components, modern hooks, Redux (or equivalent), and careful state design in long-lived single-page apps. Nice-to-haves CesiumJS, Leaflet, Mapbox, or Three.js — anything map / 3D. Python (FastAPI + Postgres) for working across the stack. Experience designing or consuming MCP servers, or building tool-using agents. Real-time / streaming UI experience (SSE, WebSockets, telemetry). A few hard truths before you apply AI is a tool, not a substitute for engineering. We use Cursor and Claude every day, but you still need to understand the code AI produces, debug it when it breaks, and explain trade-offs and decisions when asked. If AI is your only path to a working PR — and you can't defend the PR once it lands — this won't be a fit. You'll inherit complexity. This is a real codebase with history. You'll spend time reading before you write. The bar for "done" is high. "It works on my machine" doesn't ship. We care about edge cases, accessibility, regressions, and the ten things the user might do that you didn't think of. Generic AI-generated cover letters get instant rejection. We can tell. So can the next reviewer.

Troubleshoot and correct "Type Your Job Title" field: https://www.opportunities-unlimited.com/search_while_typing_project_create_profile_test_form.php John ------------------------------- John D. Hoover Jr Chief Executive Officer Hoover Products Corporation College: The Pennsylvania State University Major: Management Information Systems Military: U.S. Navy SN E-3 Character of Discharge: Honorable