Where should blog articles live?

The cleanest setup is Markdown sources in content/blog/ru and content/blog/en, then generated HTML pages in site/ru/blog and site/en/blog.

Why use Markdown for articles?

Markdown is easier to edit, review, and scale than raw HTML. It also works well for automated generation.

What does the blog generator handle?

It converts Markdown into HTML, adds schema.org, Open Graph, breadcrumbs, and updates sitemap.xml automatically.

How to Launch a Blog on InfoLady

The blog is more than a content area. For InfoLady, it becomes a search visibility engine because the site already uses a static, multilingual structure that is easy to crawl and index.

Recommended workflow

Store source articles in content/blog/ru and content/blog/en.
Generate static pages into site/ru/blog and site/en/blog.
Keep a separate index.html for each language.
Refresh sitemap.xml after every content build.

What every article should include

a clear title;
a short meta description;
publish and update dates;
FAQ blocks for richer search results;
internal links to related product pages.

Why this fits InfoLady

InfoLady already has a bilingual static architecture, so the blog extends the same model naturally:

separate URLs for each language;
no CMS dependency;
simple FTP deployment;
strong SEO and GEO potential.

If we start with 8-12 posts, the blog can quickly build a useful topical cluster:

AI SEO basics;
GEO optimization;
content for AI search;
technical SEO checklist;
visibility case studies;
FAQs about ChatGPT and Perplexity search.

That content mix helps the blog support the product pages instead of competing with them.