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.

IF YOU CALL MY PHONE OR EMAIL ME YOU WILL BE DISQUALIFIED. FIXED PRICE DELIVERABLES ONLY. SORRY. NO HOURLY. We run SWAGO (swago.com) — a custom-apparel/merch e-commerce storefront — and we're turning its platform into MerchOS (merchos.io), a multi-tenant SaaS where any brand can spin up their own branded merch storefront on a subdomain (brand.merchos.io). SWAGO becomes the flagship tenant; the same codebase serves unlimited tenants. This is not greenfield. A substantial foundation already exists — we need a senior engineer to take it across the finish line to a production, self-serve multi-tenant launch. What's already built Host-based tenant routing (flagship / SaaS / tenant subdomains), tenant context, per-host branding. Tenant data model + row-level-security isolation (Postgres RLS): tenants, members, invites, platform admins, orders/carts/leads scoped by tenant_id. Tenant signup + Stripe Connect onboarding; company-store checkout wired to destination charges + platform application fees. Per-tenant catalog overlay and per-tenant margin/MOQ pricing scaffolding; tenant theming data model + asset storage bucket. What we need you to do (the heavy lift) Finish self-serve tenant commerce — tenant storefront (browse → cart → checkout) fully wired to Stripe Connect + tenant-scoped orders; activation/go-live. Payments hardening — Connect refunds & dispute/chargeback handling, account.updated/payout.failed Connect webhooks, per-tenant tax, and SaaS subscription billing (tiered plans/monthly fees, dunning, upgrades/cancellations). White-label — tenant branding editor UI (logo/favicon/hero/colors/portfolio), custom domains (shop.brand.com w/ cert provisioning), and per-tenant transactional email sending domains (Resend). Isolation & lifecycle completeness — audit remaining tables/storage for tenant scoping, tenant suspension/offboarding/data-export, quotas/rate limits, and content moderation. Ops — per-tenant observability, platform-admin impersonation/support tooling, audit logging. Tech stack (you must be strong in these) React (React Router v7, framework/SPA mode, TypeScript), Supabase (Postgres, RLS, Edge Functions/Deno, Auth), Stripe Connect (destination charges, application fees, webhooks), Vercel (deploys, domains, edge/rewrites), Resend. Ideal candidate Has shipped a real multi-tenant SaaS (subdomain + custom-domain routing, tenant isolation). Deep Stripe Connect experience (marketplaces/platforms), including refunds/disputes/payouts. Fluent in Postgres RLS and secure multi-tenant data modeling. Comfortable owning ambiguous, cross-cutting infra work end-to-end. Screening questions (please answer to apply) Link a multi-tenant app you built. How did you handle tenant isolation and custom domains? In Stripe Connect, who bears the fee/liability on a refund and a chargeback, and how do you implement it? How would you enforce per-tenant data isolation in Postgres so one tenant can never read another's orders?

If your design standards are not absolute perfection, do not apply. We are not looking for someone to dump text into a template, swap a font, and call it a day. We own a high-end brand (Aurelius Aesthetic Med Spa) operating on a Midnight Black and Imperial Gold aesthetic. The foundational framework and copy are already built inside our GoHighLevel account. We require an expert front-end visual designer to execute a meticulous, high-end design alignment and mobile responsiveness polish. If you cannot spot visual flaws, layout glitches, or micro-spacing errors with absolute precision, you will not survive our review process. Your Specific Scope: 1. Flawless Mobile Responsiveness: Scale text overlays and image banners so nothing clips, wraps awkwardly, or distorts on any mobile screen size. 2. Pixel-Perfect Asset Integration: Correctly frame and drop transparent luxury graphic assets into headers, carousels, and sections without layout glitches or warping. 3. Elite Aesthetic Polish: Optimize the padding, tracking, margins, and custom layout elements across the entire page for a seamless, ultra-premium experience. Project Type: Fixed-Price Milestone Budget: $300 for Completed Polish Funds will be fully escrowed upfront, but milestones will only be released once the layout has been thoroughly inspected on desktop and mobile and verified to meet our elite quality standards. If you are a true elite designer who takes pride in flawless execution, reply with your portfolio.

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)

I need assistance in pointing my Wix.com domain to a new hosting service while ensuring my Google Workspace account remains active. The task involves managing DNS settings to facilitate a seamless transition. The ideal candidate should have experience in domain hosting and DNS management.

Ran https://www.thestoneindustry.com/ through the W3C validator. We have 63 issues: errors, warnings, and info markers. We need to fix the issues by outsourcing this a person who specializes in this to tackle this list. Here is a list of the first 20 to give you an idea of what we’re looking at (see two attachments).

I am looking for someone who is an expert at creating landing pages, easily using AI, so I can duplicate this model. You just have to show me how to do this. I am looking to create many and I will do them on my own. I simply need direction on how to do it and what proper tools to use to make it quick, simple, and easy.

Frontend: React Native (Expo SDK 54), TypeScript Backend: Firebase — Firestore, Cloud Functions (Node, v1), Firebase Auth, Firebase Storage Architecture: Multi-tenant data model (multiple client organizations sharing one Firestore database, isolated by security rules) Auth: Email/password via Firebase Auth, role-based access (general contractor / subcontractor roles) Firebase / React Native SaaS (Contract, with potential for ongoing work)

We're hiring a senior front-end contractor to take ownership of the front end of CMMC.builders, a production compliance-assessment platform, and then support other applications in our portfolio on an ongoing basis. The app was built quickly using Replit and AI-assisted ("vibe coding") workflows — it works, is in production, but it was not written with long-term maintainability as the top priority. We need someone who can read a large AI-generated codebase, form an independent judgment about what's solid versus fragile, and systematically bring it up to a level you'd defend in a code review at a company that values engineering. This isn’t a "rewrite everything" job. It's an audit-and-refactor process: understand what exists, identify risks, fix them without breaking production, and leave the codebase in a state a regular team could safely build on. This is a long-term role supporting a well-funded, high-stakes MVP, with real potential to turn into a full-time position for the right person. WHAT YOU'LL ACTUALLY BE DOING Phase 1 — Audit (first 1–2 weeks) Review the front-end architecture (component structure, state management, data-fetching patterns, routing, type safety) and prepare a written report on your findings, prioritized by risk and effort. Identify AI-coding issues specifically: duplicated logic, inconsistent patterns across similar features, overly broad "any" typing, prop-drilling where shared state should be, dead code, and components that mix data-fetching, business logic, and presentation. Flag any security or correctness concerns on the front end (unsanitized rendering, client-side trust of server-controlled data, broken access-control assumptions). Phase 2 — Refactor (ongoing) Carry out the refactor plan in reviewable, incremental PRs — no large-scale rewrites. Establish or tighten conventions: component boundaries, shared hooks, data-fetching layer, form/validation patterns, error and loading states. Improve type safety and eliminate unsound patterns introduced by AI-assisted coding. Add or enhance test coverage on the areas you modify. Document decisions throughout to keep the codebase understandable for the next person (human or AI). Beyond CMMC.builders Once the initial audit and top-priority refactoring are stable, you will work on front-end tasks across other applications in our portfolio — developing new features, conducting additional audits, and providing senior front-end support. OUR STACK React 19 + TypeScript, built with Vite TanStack Query for data-fetching and caching, wouter for routing Zod for schema validation Express (Node) backend, PostgreSQL via pg (no ORM — handwritten parameterized SQL) Vitest + Playwright for testing Hosted on Replit, deployed via Replit Autoscale YOU SHOULD APPLY IF You have 5+ years of production React/TypeScript experience and can cite real shipped projects, not just tutorials. You've performed codebase audits or major refactors before — not just greenfield projects. You can share a time when you inherited a messy codebase and what you actually changed. You are comfortable reading unfamiliar code quickly, forming your own judgment, and respectfully pushing back if something seems wrong — including AI-generated code that looks superficially okay. You write clearly. The audit report and PR descriptions are as important as the code. You can work independently with minimal oversight and communicate proactively, not just when prompted. NICE TO HAVE Direct experience refactoring or "productionizing" AI-generated or AI-assisted code. Familiarity with compliance, security, or regulated-industry software (this product deals with CMMC/cybersecurity compliance data). Experience using Replit as a development environment. HOW TO APPLY Your proposal must include: A one- or two-sentence example of a real audit or refactor you led on an existing codebase — what was wrong and what you did. A link to a GitHub repo or code sample showing your TypeScript/React coding style (not just a live demo link). The words "compliance refactor" are somewhere in your opening line, so we know you’ve read this posting. Proposals that are templated, copy-pasted, or don't answer the above won’t be considered, regardless of rate.

We need a portal designed that will enable basic login logout functionality to add to our website. simple website/portal design/styling will be needed. We will need to create a database to store permission sets for 2-3 types of users; customer, employee, and admin. Database will also be used for future features added to portal.