1. Brief
Send the design, target platform, page list, interactions, breakpoints and deadline. NDA requirements can be flagged before source files are shared.
See how projects move from brief to delivery, then find practical answers about formats, hand-coded markup, audits, CMS/e-commerce implementation and project delivery.
Scope first, implementation second, QA before handoff. A clear workflow keeps assumptions visible and delivery predictable.
Send the design, target platform, page list, interactions, breakpoints and deadline. NDA requirements can be flagged before source files are shared.
The implementation approach, assumptions, exclusions, revision scope, delivery format and price are confirmed.
Markup, CSS and interaction code are implemented using the lightest appropriate approach for the project.
Responsive states, key interactions and source organization are reviewed before final files are handed off.
PXHTML front-end work is built around semantic HTML where appropriate, responsive CSS, organized assets and lightweight implementation that avoids unnecessary runtime dependencies. Interaction foundations are designed to remain keyboard-usable, while the final structure is prepared for straightforward handoff or integration into a larger development workflow.
For new builds, see Design to Pixel perfect markup and CMS & e-commerce .
Browser support, WCAG accessibility targets, CMS or framework integration, revision scope and any post-delivery support are confirmed as part of the project scope. Defining these requirements early keeps pricing, testing and delivery expectations aligned with the actual implementation.
Existing interfaces can also be reviewed through a Front-end audit or WCAG accessibility audit .
Answers about accepted design formats, audits, responsive behaviour, email templates and how projects start.
Figma, Adobe XD, Sketch, Photoshop/PSD, Illustrator, PDF, image references and existing website URLs can all be reviewed. The service is design-to-markup; the source format does not define a separate product.
Yes. The front end is implemented deliberately in HTML, CSS and JavaScript rather than treating exported or automatically generated design code as the finished deliverable.
Yes. A front-end audit can review HTML, CSS and JavaScript structure, responsiveness, maintainability and implementation quality within an agreed page or component scope.
Yes. WCAG accessibility audits can cover keyboard access, focus, semantics, forms, ARIA, contrast, content structure and other criteria within the WCAG target agreed for the project. The audit produces remediation findings rather than an automatic claim of legal compliance.
Yes. PXHTML can implement approved front-end designs in WordPress, WooCommerce, Shopify and other agreed CMS or e-commerce platforms. Scope and pricing depend on the platform, templates, reusable content sections, storefront requirements and any custom functionality.
Delivery depends on page count, design complexity, interactions, audit depth and the target platform. Timing is confirmed after the actual scope is reviewed.
Yes. Agency-friendly delivery can include confidential source handling and clean handoff. Any NDA or non-contact requirement should be confirmed before the project starts.
Yes. PXHTML develops responsive campaign and transactional HTML email templates using email-safe markup patterns, with the final scope aligned to the target email platform and client requirements.
Yes, when the interface requires it. Straightforward interactions can be implemented without adding a framework. Framework-specific development should be agreed as part of the scope.
Use the Contact page to send your project scope, design source, platform requirements and deadline. Existing clients can also continue directly to the order area.
Scope, preparation, responsive delivery, SEO, contact forms, pricing and what qualifies for the one-day build.
Yes. PXHTML One-Day Website is a focused website-in-one-day service for compact small-business, consultant and service-company websites when the content, required pages and visual direction are ready before the build begins. The result is a responsive static website rather than an open-ended custom application.
It is designed for small businesses, consultants, freelancers, independent professionals and local service companies that need a credible, responsive business website quickly and do not need a complex application or large custom backend.
The agreed one-day scope can include responsive HTML, modern CSS, lightweight JavaScript, contact-form integration, clear calls to action, technical SEO essentials, organized source files and deployment support for the agreed hosting environment.
Please provide the business name, logo, approved page copy, images, required page list, contact details and any useful visual references or preferred style direction. If deployment is included, provide the relevant domain or hosting details as well.
Yes. The website is built as a responsive static front end intended to work across current desktop, tablet and mobile screen sizes within the agreed scope.
It includes technical SEO essentials such as semantic page structure, sensible heading hierarchy, metadata, crawl-friendly markup and a fast static front end. Ongoing SEO campaigns, content strategy or guaranteed rankings are separate from the one-day build.
Yes, when required by the agreed scope. A lightweight form service can be integrated so visitors can send enquiries without requiring a custom backend.
By default it is a hand-coded static website, which keeps the build fast and lightweight. If you need WordPress, WooCommerce, Shopify or another content-managed/storefront platform, PXHTML offers a separate CMS & e-commerce implementation service.
The scope is reviewed before work begins. If the requested page count, content volume, interactions or platform requirements exceed a realistic one-day build, PXHTML will confirm a different scope or quote rather than force the project into the One-Day Website package.
The published One-Day Website guide price is $129 for the defined service scope. Any materially larger or more complex requirement is confirmed before work begins.
Write the uncertainty directly into your project brief. It is better to price an unknown explicitly than bury it in assumptions.
Prepare project brief