SYSTEM PROMPT:
Create a fully functional website for Insurance small business in cs language for the country CZ.
The site name is Gyqive. Use it in metadata and in the text of the site.
It should contain the required pages: About (show in header, show in footer), Services (show in header, show in footer), Contacts (show in header, show in footer), Privacy Policy (show in footer), Cookies Policy (show in footer), Terms And Conditions (show in footer), Payment And Refund Policy (show in footer), legal notice (show in footer) in cs language. These must be full-fledged pages, not dynamic, but created manually!!! Add links to these pages manually in the header and the footer (if neccessary).

Do not add legal notice / impressum page to header links!!!!

Also add dynamic pages. Create a data/pages.json file containing an array with the following contents:
[
{
"title": "Example Page",
"slug": "example-page",
"content": "This is the full content of the example page. It can be as long as needed.",
"show_in_header": true,
"show_in_footer": true
}
]
DO NOT ADD ANY OTHER PAGES IN THE ARRAY EXCEPT THE PROVIDED ONE.
Make these pages dynamic so that they are displayed depending on data/pages.json file. Be sure to add the generateStaticParams function for the static export to work correctly.
Necessary use dangerouslySetInnerHTML to render the dynamic page content, as it HTML content is provided. Add h1 with title and div with content on the dynamic page.
Add dynamic pages links to header and footer (use only slug for link) depending on show_in_header and show_in_footer properties. Dynamic pages are at the same nesting level (main) as the main pages.

Use the following placeholders for contact and other data on any pages where it is required:
email - {site.email}, address - {site.address}, phone - {site.phone}, site name - {site.name}
Not make config helper, just paste string with placeholder in any place where it is needed.

Important: do not add links to social networks on the website.
The Contacts page should contain an interactive contact form, which, although not processed, displays a successful submission message after sending.

Make sure that all links on the site work and direct users to the appropriate sections, as this is
crucial for user navigation.
In addition, all interactive elements must be functional, which is very important. Don't use filters or sorting.
Allowed interactive elements: contact form, newsletter subscription form. Do not add maps!!
All forms must simulate actual submission by delaying and changing the text on the button. Do not use alert() to
simulate form submission. All pages MUST be server components. If you need to add interactivity, it should be moved to
separate client components. There should be no client handlers in page.tsx files.
The final product must be ready for immediate use and provide a seamless experience for visitors.
The text on all elements should contrast well with the background. The website should look fresh and modern.
Use object-cover on all photos.

ALWAYS use font loading by use @import url in the app/globals.css file instead of importing fonts as JavaScript packages!!!
Use css variable for fonts (--font-sans, --font-serif, --font-mono) in :root in app/globals.css file.
Please always use semantic color tokens from your design system instead of hardcoded colors.
ALWAYS use rem for radius and spacing css variables in app/globals.css file.
Replace ALWAYS USE semantic tokens (like bg-primary, text-secondary, bg-background, text-foreground, etc.) instead color values (like bg-blue-500, text-red-600, #ffffff, etc.) that will work better with the design system and support proper theming.
Don't forget add "container mx-auto" for centering sections.

All input fields should have a 'bg-background' class. All forms should work without reloading the page.
Put the Header and Footer and Cookie Banner in the Layout. Do not add the @vercel/analytics/next module to the Layout
file. Do not
indicate anywhere that the site was made using v0.
Always use a light theme. Do not add sub-items to the menu in the header, only top-level items. Do not add
links to pages that do not exist in the header and footer.
Do not write the site name in the header and footer sections. For the logo, always use src="/logo.png". Do not pay
attention
that such a file does not exist. I'll add it later on my own.
For the logo, make a height restriction only, and let it be automatic in width.

The website must have a clear commercial component.
You can add product prices and discounts (but no more than 30-40%).
However, it should not be possible to actually purchase anything on the website; all interactions should lead to
a contact page.

The website must have a blog. Create a data/articles file.json containing an array with the following contents:  
[  
{  
"title": "Example Article",  
"slug": "example-article",  
"summary": "This is a summary of the example article.",  
"content": "This is the full content of the example article. It can be as long as needed.",  
"image": "placeholder.svg",  
"author": "John Doe",  
"image_alt": "An illustrative image for the example article",  
        "date": "2025-10-01",  
    "is_ad": false  
}  
]  
Make the blog dynamic so that articles are displayed depending on data/articles.a json file. Be sure to add  
the generateStaticParams function for the static export to work correctly. The slug property  
is used for the detailed article page. If is_ad is true, add a warning stating that this is an advertising article  
(only on the detailed page of the article). Do not generate articles yourself, use only the provided content (1 article).  
Do not add tags or categories of articles, article search, filtering or sorting. Don't make a featured article, that's  
it the articles should be equivalent. Don't add the option to share or leave a comment on the article page. Use src={article.image} on single article page and blog page.  
Necessary use dangerouslySetInnerHTML to render the article content on the article detail page, as it HTML content is provided.  
Always use «blog» slug for the blog main page but Title can be in site language.  
Always use article.image property for article image src.  
  

The site should be fully responsive and look equally good on desktop and mobile devices.
It is mandatory to have a banner in the corner informing about the use of cookies on the site.

Important! When adding images, write them to data/images.json in this format:
[
{
"id": "team-man-01"
"url": "https://example.com/image.jpg ",
"alt": "Studio photo of a man with a beard and glasses"
}
]
In alt, be sure to add what is shown in the picture.
Alt always must be in english regardless of the site language.
Write a helper function to get an image by id from data/images.json and use it wherever you need to specify the src
of the image.

In design, adhere to the following principles: Layout: left_nav, Spacing: 12col, Color: bold, Typography: soft_humanist, Header: patterned, Navigation: center_buttons, Hero: product_slider, Imagery: retro_filter, UI: inline_forms, Footer: icons_only, Homepage structure: hero -> product_cards -> faq -> timeline -> workflow_steps -> contact_form -> text_block_full_width