Precision Front-End Implementation for Seven-Page Website
Publicada el 2026-07-21
Descripción de la oferta
Front-End Developer Needed to Reproduce Seven-Page Website From Final Visual Mockups I have completed the creative direction for a seven-page informational website. Every page has a final visual mockup, final written copy, approved imagery, one official logo, and specified fonts and type sizes. This is not a design project. I am not seeking creative reinterpretation, alternate layouts, substituted graphics, revised typography, or independent design decisions. The developer’s job is to reproduce the supplied pages accurately and consistently in clean, responsive HTML and CSS. Project Scope Build seven responsive website pages that match the supplied visual mockups as closely as reasonably possible across modern desktop, tablet, and mobile browsers. The completed website must maintain absolute consistency from page to page, including: identical header height and structure; •Identical logo size, position, and clear space; •Identical navigation placement, spacing, typography, and active-page indicators; •Consistent page widths, margins, padding, and content alignment; •Correct fonts, font weights, sizes, capitalization, and line spacing; •Consistent heading, subheading, body-copy, icon, divider, button, and footer treatments; •Consistent colors, borders, shadows, icon styles, and image proportions; •No substitutions, alterations, or redesigns of supplied assets; •No arbitrary page-by-page adjustments that create visual drift. The official logo must be used exactly as supplied. It may not be redrawn, recolored, reconstructed, stretched, cropped, re-typeset, or otherwise modified. Technical Requirements The website should be built using clean, standards-compliant HTML5 and CSS3, with only minimal JavaScript where genuinely necessary. The site must: •Render properly in current versions of Chrome, Safari, Firefox, and Edge; •Scale cleanly for desktop, tablet, and mobile screens; •Avoid horizontal scrolling; •Use optimized image assets; •Load without broken links, missing files, console errors, or layout failures; •Use reusable global styles and shared components rather than independently styling each page; •Maintain a logical, clearly organized file structure; •Avoid page builders, unnecessary frameworks, plugins, or bloated dependencies unless approved in advance. There is no complex dynamic functionality required. The project is primarily a precision front-end implementation. Required Development Method To prevent inconsistent page construction, the developer must first establish a shared site-wide design system for: •Header; •Navigation; •Logo treatment; •Page width; •Typography; •colors; •Icons; •Section spacing; •Dividers; •Forms; •Buttons; •Image presentation; •Footer. These elements should be coded once as reusable global components or styles and then applied consistently throughout the site. The developer must not manually recreate the same shared element differently on each page. Mandatory Staged Review The project will be completed in stages. Stage 1 — Global Framework Before building all seven pages, the developer will complete: •the global header; •Navigation; •Footer; •Typography system; •Color system; •Responsive page container; •Standard section spacing; •Shared icon and divider treatments. These elements must be approved before full page production begins. Stage 2 — One Reference Page The developer will complete one designated reference page in full. That page will be reviewed for: •Logo size and position; •Navigation spacing; •Fonts and type sizes; •Margins and alignment; •Image placement; •Section spacing; •Icon treatment; •Footer placement; •Responsive behavior. The remaining pages should not be completed until the reference page and shared site framework are approved. Stage 3 — Remaining Pages The remaining six pages will then be built using the approved shared framework. Stage 4 — Full-Site Quality-Control Review Before requesting final approval, the developer must personally compare every completed page against its supplied mockup and correct all visible discrepancies. I do not want a partially reviewed draft followed by a general question such as, “How does this look?” The developer is expected to inspect the work carefully before presenting it for review. Accuracy and Revision Expectations The supplied mockups are the controlling visual reference. The following will not be accepted as finished work: •Logo movement or resizing from page to page; •Inconsistent navigation placement; •Incorrect fonts or weights; •Substituted icons or graphics; •Inconsistent heading sizes; •Different margins on similar sections; •Inconsistent footer dimensions; •Altered imagery; •Missing copy; •Accidental text changes; •Inconsistent capitalization; •Approximate rather than matched colors; •One-off page styling that conflicts with the approved global system; •Unresolved issues remaining after similar issues were already identified elsewhere. When one repeated component requires correction, that correction must be applied everywhere the component appears. I should not have to identify the same defect separately on every page. Revisions are included until the site materially matches the supplied mockups and all agreed corrections have been implemented consistently throughout the project. Developer Qualifications Applicants should have demonstrated experience with: •Precise front-end implementation from supplied visual designs; •Responsive HTML and CSS; •Reusable design systems and shared components; •Cross-browser testing; •Careful visual quality control; •Working from exact client specifications rather than improvising. Please provide examples of websites you personally coded from completed mockups or design files. Do not apply if your normal process is to produce a rough approximation and rely on the client to identify every visual discrepancy. Deliverables •Seven completed responsive website pages. •All approved supplied assets properly implemented. •Clean and organized HTML, CSS, JavaScript, image, and font directories. •Shared global styles and reusable components. •Correct page titles and navigation links. •Site uploaded to my hosting account. •Any required relative paths or server paths configured. •Testing on desktop, tablet, and mobile dimensions. •Verification that all pages, links, images, and assets load correctly. •Complete editable source files. •A final ZIP archive of the deployed website. •A brief file-structure and maintenance note. Final Acceptance Criteria The project is complete only when: •All seven pages are live; •The website materially matches the supplied mockups; •Repeated elements are consistent across every page; •Supplied text and assets have not been altered without authorization; •The site functions correctly across modern browsers and common screen sizes; •There are no broken links, missing assets, console errors, or obvious layout defects; •All requested corrections have been completed throughout the site rather than only on the page where they were first identified. Confidentiality Execution of a nondisclosure agreement is required before proprietary materials and complete project assets are released. Application Instructions Please include: •Two or three relevant examples of precise front-end implementation work; •The technology you propose to use; •confirmation that you will use shared global components and styles; •Confirmation that you will complete and obtain approval of one reference page before building the remaining pages; •Your fixed-price bid; •Your estimated completion time; •Tthe number of revision rounds included; •Confirmation that you will deploy the completed site to my hosting account. Generic proposals will not be considered. Include the word "Mahogany" in the first sentence of your proposal
Skills
- HTML
- CSS
- JavaScript
- Design Systems
- Control de Calidad
- Controlling
- Typography
- Render
- Microsoft Word
- TypeScript
- React
Fuente original: freelancer