Enludus Company Web
Official website for Enludus, the trade name under which Ibuki Nagase (sole proprietor) makes and runs software.
A single-page site built with Vite, React and TypeScript, in lp-anatomy's "warm" mood (modelled on Bikkuri Donkey): two paper colours with oval edges, the logo's three colours only, hand-drawn SVG illustrations in those colours (src/illustrations.tsx), Fredoka and Zen Maru Gothic (subset to the page text at build time), a centre slider of real product screens, and arched product cards. It presents five products:
Stack
- Vite
- React 19
- TypeScript
- Vanilla CSS
- Vercel
Local development
Run npm install and npm run dev.
Production build: npm run build.
Deploy to Vercel
- Import this GitHub repository in Vercel.
- Vercel should detect Vite automatically.
- Build command: npm run build
- Output directory: dist
- Add enludus.com (and optionally www.enludus.com) under Project → Settings → Domains.
- Apply the DNS records Vercel shows for the domain.
No environment variables are required.
Routes
| URL | Source |
|---|
/ | English top page (index.html → src/App.tsx) |
/ja | Japanese top page (ja.html → same app, lang="ja") |
/portfolio | Founder portfolio, static HTML from site/profile.ts |
/blog, /blog/<slug> | Blog, static HTML from content/blog/*.md |
/blog/feed.xml, /sitemap.xml, /404 | Generated at build time |
/og/*.png | Open Graph cards for every page and post, generated at build time (site/og.ts) |
/products/*, /privacy | Hand-written pages in public/ |
A visitor whose browser prefers Japanese is sent from / to /ja on the first visit. The EN / JA switch in the header is remembered (localStorage) and always wins.
Content
Company copy and product facts (specs, release months, screenshots) for both languages live in src/i18n.ts. Product screenshots are WebP files in public/img/products/, two widths each, taken from the App Store listings and the live web apps. The Japanese object is typed from the English one, so a missing or extra key fails npm run build. The visual system and responsive behavior live in src/styles.css.
The portfolio's facts live in site/profile.ts. Portfolio, blog, posts and 404 share the company top's warm look: public/site/site.css, the same SVG drawings (rendered to static markup at build time by site/art.ts), and Fredoka + Zen Maru Gothic subset to each page's text. public/site/site.js adds the mobile menu, reveal-once, the stack band, the JST clock and the blog tag filter — all motion off for reduced motion and Save-Data. The hand-written product guides and privacy pages use the same palette and fonts through public/products/product.css.
Writing a blog post
-
Add content/blog/<slug>.md. The file name is the URL: content/blog/hello-world.md → /blog/hello-world. Use lowercase letters, digits and -.
-
Start it with front matter:
---
title: 記事のタイトル
date: 2026-10-19
description: 一覧・検索結果・RSS に出る 1〜2 文の説明
tags: [設計, Swift]
# updated: 2026-10-25 (optional)
# draft: true (optional: shown in npm run dev only)
# type: tech (optional: a deep technical write-up; default is a readable "story" post)
---
-
Write Markdown (GitHub flavored: tables, code blocks, lists). Code blocks are coloured at build time; tag them with a language (ts, swift, rust, go, bash, … see LANGS in site/posts.ts). Every ## heading becomes a table-of-contents entry once a post has three or more. Put images in public/blog/<slug>/ and reference them as /blog/<slug>/image.webp.
-
npm run dev and open /blog. Commit and push; the post, its share card (/og/blog/<slug>.png), related posts, the portfolio's "Writing" list, the RSS feed and the sitemap update on deploy.
The share cards fetch Manrope, Noto Sans JP (subset to the characters used) and DM Mono from Google Fonts during the build. If that fails, every card falls back to site/og-fallback.png and the build still succeeds.
Daily blog sync
A daily routine follows BLOG_SYNC.md: it reads each product repository from the commit recorded in blog-sync.json, checks App Store versions, compares the code against the posts written about it, and opens one 「ブログ更新」 PR when something is worth adding. The PR also moves the recorded SHAs forward. It never merges.
