ArtFixPro Project Instructions

These instructions apply to the entire ArtFixPro website repository. Read and follow them before changing files. Direct instructions from the project owner, system instructions and platform instructions have higher priority than this document.

1. Project identity

ArtFixPro is a New York City home-service company. The website presents professional services for apartments and homes, including:

The website domain is https://artfixpro.com.

Website language:

2. Technology and project structure

This is a Jekyll website using Liquid templates, HTML, existing CSS and vanilla JavaScript.

Important files and folders:

The main package commands are:

npm run genimg
npm run build
npm run serve
bundle install
bundle exec jekyll build
bundle exec jekyll serve

On Windows PowerShell, use npm.cmd if the PowerShell execution policy blocks npm.ps1:

npm.cmd run build
npm.cmd run serve

The normal deployment artifact is the content of _site/.

3. Mandatory workflow before making changes

Before editing any file:

  1. Inspect the repository structure and current Git status.
  2. Read the most relevant existing page, layout, include, stylesheet and script.
  3. Find a visually similar page and follow its structure.
  4. Check whether the requested form, modal, calculator, image component or JavaScript behavior already exists.
  5. Preserve unrelated user changes in a dirty working tree.
  6. For a new service page, research comparable US services when the request benefits from current market positioning or wording.
  7. Before implementation, explain the proposed concept, page structure and important assumptions to the owner. If the owner asks to proceed, implement the approved direction.

When a task is only a diagnosis or review, do not implement a fix unless the owner asks for one.

When a task requests a change or a new page:

  1. Make the smallest coherent set of changes.
  2. Reuse existing components and styles.
  3. Keep content, pricing, selectors, form fields and JavaScript data consistent.
  4. Validate the result proportionally to the risk.
  5. Report changed files, checks performed and any remaining environment limitation.

Do not create a Git commit or push changes unless the owner explicitly asks for it.

4. Design and frontend rules

5. Creating a new service page

Every new service page should normally include:

  1. Front matter with layout, head_include, description and any service FAQ data used by the project.
  2. A page-specific head include in _includes/heads/ with title, description, keywords, canonical, Open Graph and Twitter metadata.
  3. One clear H1 containing the service and location keyword naturally.
  4. A hero image using the existing picture.html include.
  5. A short hero promise focused on the customer result, not just a list of tasks.
  6. A primary CTA connected to the existing form or booking flow.
  7. A section explaining how the service works.
  8. A section explaining what is included and what makes ArtFixPro different.
  9. Pricing or plans only when pricing is defined and can be kept consistent with the form.
  10. FAQ content answering real customer questions.
  11. Relevant internal links to existing ArtFixPro services.
  12. Service, FAQPage, BreadcrumbList and LocalBusiness structured data when appropriate.

Do not add a separate main-navigation link unless the owner requests it. A page can still be indexed through the sitemap, footer, contextual internal links, FAQ links or relevant booking prompts.

Use relative_url for internal Liquid links:

<a href="/tv-mounting">TV Mounting</a>

Use absolute URLs for canonical, Open Graph and JSON-LD URLs.

6. Content and positioning rules

The page must sell the finished result and the emotional benefit. Explain:

Use plain, specific language. Avoid keyword stuffing, generic filler, exaggerated claims and vague phrases such as “best service” without evidence.

Do not invent:

Existing claims such as insurance, warranties, review counts and service areas must remain consistent across page copy, FAQ, metadata and JSON-LD.

7. Full-service moving and turnkey relocation positioning

The full-service moving service is not merely a moving-truck or labor service. The central promise is a designer-led, move-in-ready home.

The intended customer journey is:

  1. A move manager and designer review the new apartment and plan the layout.
  2. The client approves where furniture, accessories and personal belongings will go.
  3. ArtFixPro can coordinate approved furniture, lighting, rugs, window treatments, decor and everyday essentials when the selected plan includes purchasing.
  4. The team packs, protects and transports the client’s belongings.
  5. The team assembles furniture and installs TVs, shelves, mirrors, art, frames, curtain rods and curtains.
  6. Clothing, linens, kitchen items, bathroom items, decor and everyday belongings are placed in their agreed locations — drawers, cabinets, closets, shelves, tables and other surfaces.
  7. Boxes and packing debris are removed; the apartment is cleaned and styled.
  8. The client may spend one night with friends or at a hotel, depending on the approved project schedule, then arrive at a fully prepared home.

The core idea is:

You do not move into a project. You move into your home.

The finished apartment should be described as a place where the bed is made with the agreed linens, clothes are organized, belongings are already in their intended places, and the client can arrive and live comfortably from day one.

Current full-service moving components:

Current plan direction:

Current apartment-size options:

Current service-area wording:

New York City, New Jersey and destinations within approximately 100 miles of Manhattan. Longer-distance relocations may be arranged after a project review.

Use this wording unless the owner changes the coverage policy.

8. Forms, pricing and interactive behavior

Use the existing booking flow instead of creating a duplicate form.

For full-service moving:

Current Deposit Saver pricing is 40% of the previously used values:

Apartment size Price
Studio $276
1-Bedroom $396
2-Bedroom $596
3-Bedroom $876
4+ Bedroom $1,196

Do not change prices or add-ons without explicit owner approval.

9. Images and responsive image pipeline

Source images belong in assets/images/. The script tools/generate-images.js scans source images and generates responsive WebP variants at 360px, 720px and 1080px into assets/generated/. It also updates _data/generated_images.json.

Use the existing include:












<picture>
  <source
    type="image/webp"
    srcset="/assets/generated/service-image-name-360.webp 360w,
            /assets/generated/service-image-name-720.webp 720w,
            /assets/generated/service-image-name-1080.webp 1080w"
    sizes="(max-width: 768px) 100vw, 740px">
  <img
    src="/assets/generated/service-image-name-720.webp"
    alt="Descriptive SEO-friendly alt text"
    loading="lazy" decoding="async">
</picture>

Rules for new images:

10. SEO and AI discoverability

Each service page should answer the main question directly in the first screenful of text. Use natural phrases such as:

Use only phrases relevant to the actual service. Include the city or service area naturally, not in every sentence.

Structured data must be valid JSON. After editing JSON-LD, parse it or validate it as part of the checks. Keep the visible copy, FAQ, metadata and JSON-LD consistent.

11. Validation checklist

Before reporting completion:

12. Deployment

Build the site from the repository root:

bundle install
npm run build

On Windows PowerShell:

bundle install
npm.cmd run build

Upload the contents of _site/ to the hosting provider’s public web directory, such as public_html, www or the configured document root.

Do not upload the source repository unless the hosting provider is configured to build Jekyll itself.

13. Git and user changes

Chat