Skip to content
Sign inJoin waitlist

Making it yours — Marai Neesu AI Prompts

After the last prompt you have the Marai Neesu site with its demo text and grey placeholder photos. Everything a visitor reads lives in src/content/, so most changes are edits to text files — or a sentence to your AI tool.

What Where
Site name (the “ | Marai Neesu” ending of the browser titles), the home page’s browser title and description, site address src/content/site.json → site
You as the logo: name, place, avatar, the “Verified” seal’s name and the two lines the desktop logo shows under the pointer src/content/site.json → person
Menu (desktop and phone), the “Contact” button, the e-mail, the footer (its call to action, columns, city and time zone, profiles, credit) src/content/site.json (navigation, phoneNavigation, contactLink, contact, footer)
The copy of each page, with its browser title and description src/content/pages/<page>.json (home.json, about.json, cv.json, …)
The words every project page shares pages/project.json
The words every product page shares; every post page and the newsletter pages/products.json → product; pages/blog.json → post, newsletter
Words several pages share: the stars’ name, the slideshow arrows, the breadcrumb pages/shared.json
Projects, services, testimonials, products, posts, tools, work experiences, social profiles src/content/collections/<name>.json

Change the text between the quotes and keep the field names. Or ask your tool: “Change the name to Lea Park, the place to Lisbon, Portugal and the e-mail to hello@leapark.com in site.json.” Set site.url to your domain before you publish — the sitemap and share links are built from it. The demo’s e-mail (hello@example.com) and the links to example.com, Discord, Calendly, Contra and the course platform are placeholders: replace them all.

Your name appears in more places than person.name: the copy of most pages, the CV, the testimonials’ quotes and the page descriptions. Ask your tool to search src/content/ for “Marai” and “Neesu” to find them all.

The footer’s clock shows the time in footer.timeZone (Asia/Dubai) under footer.city: set both to yours (any IANA time zone, such as Europe/Lisbon). In the footer, {year} becomes the current year. The rolling roles under your greeting are hero.roles in pages/home.json and profile.roles in pages/cv.json: change both.

Each project in collections/projects.json has:

  • slug — its address (/project/goeboek-real-estate-and-property), unique; title; summary — on the cards and the page’s search description; service and date (2023-09-01, shown as “September 2023”) — the card’s meta line;
  • client, image — the main picture (4 : 3); description and highlights — the overview and the highlights, as blocks (see below); gallery — three pictures: two under the overview, one under the highlights (a project without a gallery shows none).

The order of the file is the order on the site: Home and the CV show the first four, the Projects page all of them, and a project page the first two others. To add a project, copy one, give it a new slug and change the fields; it gets its own page and appears in the lists and the sitemap.

collections/services.json: slug, title, description, price (text, shown as “Starting at $3,000 per project”), url — where “More Details” leads (the demo points at Contra) — and four images that move in the card. Home and the Services page show all of them, in the file’s order. Their titles are also the choices of the contact form’s “I’m interested in …” question, so a new service appears there by itself.

  • Testimonials (collections/testimonials.json): name, role, photo (a round portrait), quote and rating (stars out of 5). Home shows all of them on a slow belt (a slideshow on phones).
  • Products (collections/products.json): slug (/product/wedoes), title, tagline, price (text: “$59”), category, buyUrl (the cart and “Buy” buttons), demoUrl (“Live Demo”), image (the cover), two screenshots, the specification and the overview (blocks). Home shows the first six on desktops, four on tablets and three on phones; a product page shows the others under “More Products”.
  • Posts (collections/posts.json): slug, title, image, category (a post page lists up to three others of the same category), date (2024-07-08, shown as “Jul 8, 2024”) and the article body as blocks. The Blog shows six, then the rest with “Load More”; Home shows the first three, the CV’s Writing the first four. Posts are listed in the file’s order, not by date: the demo keeps them newest first, so put a new post first to show it first.
  • Tools (collections/tools.json): the About page’s stack — title, category, url, logo (a 50 px square image) and description. Show the tools you use, with their own logos.
  • Experiences (collections/experiences.json): your jobs on About and the CV — title, company, period (text), url and description.
  • Social profiles (collections/socials.json): the tiles in Home’s hero — label, short (the two letters), href and icon (the 26 px picture shown under the pointer).
  • The CV (pages/cv.json): the status chip, the about text, the contact links, education, certifications and the titles of the lists it fills from the collections.
  • The course (pages/courses.json): the title, the cover, the modules with their lessons (a lesson with a preview link gets a “Free Preview”), the outcomes, the overview card with the price and the enrol link (the demo points at Podia), and the questions. Home’s course banner is course in pages/home.json.

Blocks are { "type": "paragraph", "text": "…" }, { "type": "heading", "level": 3, "text": "…" } and { "type": "list", "ordered": false, "items": [[…], …] }: a list whose items are lists of blocks. In any text, **bold** is bold and \n starts a new line. Ask your tool if you prefer: “Add a post about design systems to posts.json, with the same fields as the others.”

The pack uses placeholders; each shows the size its photo is designed for (for example 1440 × 1080). Put your photos in public/images/ with the same file names and they replace the placeholders:

Photos Files
You: the avatar (the logo, the CV) and the portraits of Home and About avatar.png, home-portrait.jpg, about-portrait.jpg, about-detail.jpg, about-wide.jpg
Home’s course banner, the course page, the Blog’s newsletter home-course.jpg, course-cover.jpg, blog-newsletter.jpg
Projects project-<name>-cover.jpg, project-<name>-gallery-1.jpg … -3.jpg
Products product-<name>-cover.jpg, product-<name>-screen-1.jpg, -screen-2.jpg
Services, posts, testimonials service-<name>-1.jpg … -4.jpg, post-<name>.jpg, testimonial-<name>.jpg

Photos fill their frame and are cropped, so keep their proportions close to the placeholder’s. A new photo can have any name: refer to it in the content as /images/<file>. In a chat builder, upload the photos and tell the tool which file names to give them.

The tool logos (tool-*.png, tool-unsplash.svg), the sample client logos of the Projects page (client-1.svg … client-5.svg, in pages/projects.json → clients) and the social icons (social-*.svg) are real files: replace them with yours, or remove the ones you don’t want.

The last prompt makes the browser tab icon from your avatar (public/icon.png, public/apple-icon.png) and the share image (public/opengraph-image.png, 1200 × 630) from a screenshot of Home’s first screen. Make them again once your photos and text are in, or ask your tool to.

Prompt 1 set up the design tokens: colours (--color-black, --color-grey, --color-accent, --color-background, --color-white, and two single-use values: --color-available, the CV’s “Available for work” dot, and --color-error, a failed send), the font, text styles and spacing. The accent (#FC5000) is every hover colour — links, card titles, buttons — the e-mail’s second copy and the stars, so changing it gives the site your brand colour: “Change –color-accent to #2F6BFF.” Black and its tints carry the rest of the design. Keep the text styles’ sizes per breakpoint unless you want a different rhythm.

The font is Manrope: 400 for the large statements, paragraphs and form fields, 500 for headings, labels and buttons. Another font works the same way — ask the tool to load it and use it in --font-sans.

To remove a page, delete it and ask your tool to take it out of the menus (navigation and phoneNavigation in site.json), the footer’s columns, the sitemap and the buttons that lead to it. Products, Course and Blog are only in the phone menu; on larger screens the footer and the buttons on the pages lead to them. To add a page, write a prompt in the style of the page prompts — list its sections and reuse the components (“a Section title, then Card/Project in two columns”) — so it matches the rest.

To remove a section, ask the tool to take it out of the page, with the divider line next to it if there is one.