Hello from the TOJGAMES Team

We're excited to launch the TOJGAMES Blog — a dedicated space where we'll share what's happening behind the scenes, how we build our games, and what's coming next.

Whether you're a player, a developer, or just curious about mobile gaming, this blog is for you. We plan to post regularly, so make sure to check back often.

What to Expect

Here's what we'll be writing about:

• Game development — How we approach physics, performance, and gameplay feel in Unity
• Product updates — Deep dives into new features, maps, and systems before and after they ship
• Team stories — How we work, what we've learned, and where we're going
• Technical posts — Backend architecture, anti-cheat, store infrastructure, and more

Why a Separate Blog?

Our News section covers announcements and game updates. The Blog is for longer reads — posts that go deeper into how and why things work the way they do. Think of it as the engineering journal behind the product.

Text Formatting

You can use bold text to emphasize key points, italic text for tone or terminology, and strikethrough for things that changed or were removed. You can also combine them: bold and italic at once.

Inline code snippets are great for referencing variable names, functions like getPostBySlug(), or short commands like npm run build.

Ordered and Unordered Lists

An unordered list of features:

• Mobile-first responsive design
• Bilingual content (English and Russian)
• Markdown with full GFM support
• Related game cards on each post

An ordered step-by-step process:

1. Write the article in Markdown
2. Drop the .md file into content/blog/en/
3. Add a Russian translation to content/blog/ru/
4. Push and deploy — done

Task List

• Set up the blog system
• Write the first post
• Add bilingual support
• Write 10 more posts

Blockquote

"The best games are not the most complex — they're the ones that feel just right."

— The TOJGAMES Team

Code Block

Here's an example of the blog utility function that reads posts:

export function getPostBySlug(slug: string, locale: string): BlogPost | null { const localePath = path.join(BLOG_DIR, locale, `${slug}.md`); const fallbackPath = path.join(BLOG_DIR, "en", `${slug}.md`); const filePath = fs.existsSync(localePath) ? localePath : fallbackPath; if (!fs.existsSync(filePath)) return null; const raw = fs.readFileSync(filePath, "utf-8"); const { data, content } = matter(raw); return { slug, content, ...data } as BlogPost; }

Table

Here's a quick comparison of our content sections:

Headings at Every Level

H1 — Page Title (used once, at the top)

H2 — Major Section

H3 — Subsection

H4 — Minor Label or Callout

Links and Images

You can link to our support page, an external resource, or even a mailto link.

Images can be embedded inline — the renderer wraps them in a responsive container:

Stay Tuned

We'll be posting regularly. If you have questions or topics you'd like us to cover, reach out at support@tojgames.net.

Thanks for being part of the journey.

— The TOJGAMES Team