fix: inverted index markdown (#314)

axross · May 8, 2021 · 115010d · 115010d
1 parent 3774118
commit 115010d
Show file tree

Hide file tree

Showing 2 changed files with 69 additions and 63 deletions.
diff --git a/constants/index-page.ts b/constants/index-page.ts
@@ -1,4 +1,64 @@
 export const INDEX_MARKDOWN_BODY_EN_US = `
+- 📍 Vancouver, BC, Canada
+- 👨‍💻 **Software engineer** - 7 Client-side 📱 (Flutter, React) : 3 Server-side 🖥 (Node)
+- 🃏 **Poker player** - <=5 years recreational career; no so good yet 😛
+
+[Linkedin](https://www.linkedin.com/in/axross/)&nbsp;&nbsp;&nbsp;&nbsp;[Twitter](https://twitter.com/axross_)
+
+## Interests
+
+- ⚛️ **\`UI=F(S)\` model**
+  - Declarative approach is always better than imperative approach
+  - Now UI obtained referencial transparency and idempotence
+- 🚀 **Serverless**
+  - Most ordinal Web APIs are just a validation gateway for databases behind
+  - Cloud functions are more maintainable - easy to deploy/rollback and scale
+- 🧼 **Clean code**
+  - Your major pie of time on IDE is reading code in fact, not just writing code all the day
+  - Logical readability and history trackability is one of the KPI of productivity
+
+## Career
+
+### Parsable Inc.
+
+Senior Software Engineer, Frontend - *March 2020 - Present*
+
+- Working on a digital transformation service for industrial workers
+- Constantly creating new features with React
+
+### Self-employed
+
+Software Engineer, Frontend / Engineering Advisor
+
+- Worked as an engineering advisor for a BtoC crowdsourcing company
+    - Helped to start creating their own design system
+    - Played an agile coach/scrum master role
+- Worked as an external engineering resource at a fitness BtoC company
+    - Helped implementing SPA with React
+
+### Kaizen Platform Inc.
+
+Software Engineer, Frontend - *Nov 2016 - Jul 2018*
+
+- Worked on a crowdsoucing app as a lead engineer
+- Introduced and let the company start to use TypeScript and GraphQL
+- Also worked a little bit for UI design and DB table schema design
+
+### Gunosy Inc.
+
+Software Engineer, Frontend - *Aug 2015 - Jul 2016*
+
+- Worked on a mobile manga reader app with React and Redux
+
+### TriFort Inc.
+
+Software Engineer - *May 2014 - Jul 2015*
+
+- My first engineering career 👶
+- Worked as a player-manager (doing both of product owner and developer) for a crowdsourcing app
+- Used React (v0.12 atm) to create a SNS app that is internally used in client company
+`;
+export const INDEX_MARKDOWN_BODY_JA_JP = `
 - 📍 カナダのバンクーバーというところに住んでいます。2018年の夏までは東京に住んでいました
 - 👨‍💻 **Webのソフトウェアエンジニア**です。専門性はクライアントサイドが7割、サーバーサイドが3割といった感じです
 - 🃏 **ポーカープレイヤーです**。とはいってもリクリエーショナルで、そんなに上手くないです
@@ -66,63 +126,3 @@ Senior Software Engineer, Frontend - *2020年3月から今まで*
 - 受託制作でReactを使った (先方の) 社内向けSNSの開発をしていました
     - Reactがv0.12とかの頃でした... 懐かしい...
 `;
-export const INDEX_MARKDOWN_BODY_JA_JP = `
-- 📍 Vancouver, BC, Canada
-- 👨‍💻 **Software engineer** - 7 Client-side 📱 (Flutter, React) : 3 Server-side 🖥 (Node)
-- 🃏 **Poker player** - <=5 years recreational career; no so good yet 😛
-
-[Linkedin](https://www.linkedin.com/in/axross/)&nbsp;&nbsp;&nbsp;&nbsp;[Twitter](https://twitter.com/axross_)
-
-## Interests
-
-- ⚛️ **\`UI=F(S)\` model**
-  - Declarative approach is always better than imperative approach
-  - Now UI obtained referencial transparency and idempotence
-- 🚀 **Serverless**
-  - Most ordinal Web APIs are just a validation gateway for databases behind
-  - Cloud functions are more maintainable - easy to deploy/rollback and scale
-- 🧼 **Clean code**
-  - Your major pie of time on IDE is reading code in fact, not just writing code all the day
-  - Logical readability and history trackability is one of the KPI of productivity
-
-## Career
-
-### Parsable Inc.
-
-Senior Software Engineer, Frontend - *March 2020 - Present*
-
-- Working on a digital transformation service for industrial workers
-- Constantly creating new features with React
-
-### Self-employed
-
-Software Engineer, Frontend / Engineering Advisor
-
-- Worked as an engineering advisor for a BtoC crowdsourcing company
-    - Helped to start creating their own design system
-    - Played an agile coach/scrum master role
-- Worked as an external engineering resource at a fitness BtoC company
-    - Helped implementing SPA with React
-
-### Kaizen Platform Inc.
-
-Software Engineer, Frontend - *Nov 2016 - Jul 2018*
-
-- Worked on a crowdsoucing app as a lead engineer
-- Introduced and let the company start to use TypeScript and GraphQL
-- Also worked a little bit for UI design and DB table schema design
-
-### Gunosy Inc.
-
-Software Engineer, Frontend - *Aug 2015 - Jul 2016*
-
-- Worked on a mobile manga reader app with React and Redux
-
-### TriFort Inc.
-
-Software Engineer - *May 2014 - Jul 2015*
-
-- My first engineering career 👶
-- Worked as a player-manager (doing both of product owner and developer) for a crowdsourcing app
-- Used React (v0.12 atm) to create a SNS app that is internally used in client company
-`;
diff --git a/pages/[locale].tsx b/pages/[locale].tsx
@@ -17,7 +17,11 @@ import {
   TwoColumnPageLayoutFooter,
   TwoColumnPageLayoutMain,
 } from "../components/page-layout";
-import { WEBSITE_DESCRIPTION_EN_US, WEBSITE_NAME } from "../constants/app";
+import {
+  WEBSITE_DESCRIPTION_EN_US,
+  WEBSITE_DESCRIPTION_JA_JP,
+  WEBSITE_NAME,
+} from "../constants/app";
 import { AUTHOR_NAME } from "../constants/author";
 import {
   INDEX_MARKDOWN_BODY_EN_US,
@@ -38,18 +42,20 @@ interface ServerSideProps extends CommonServerSideProps {
 const Page: NextPage<ServerSideProps> = ({ body, tableOfContents, posts }) => {
   const { trackUiEvent } = useUserMonitoring();
   const { url, locale, alternativeLocales } = useRouter();
+  const description =
+    locale === "ja-jp" ? WEBSITE_DESCRIPTION_JA_JP : WEBSITE_DESCRIPTION_EN_US;
 
   return (
     <>
       <Head>
         <title>{WEBSITE_NAME}</title>
-        <meta name="description" content={WEBSITE_DESCRIPTION_EN_US} />
+        <meta name="description" content={description} />
         <meta name="keywords" content="kohei asai,axross,blog" />
         <meta property="og:type" content="website" />
         <meta property="og:url" content={`${url.origin}${url.pathname}`} />
         <meta property="og:site_name" content={WEBSITE_NAME} />
         <meta property="og:title" content={WEBSITE_NAME} />
-        <meta property="og:description" content={WEBSITE_DESCRIPTION_EN_US} />
+        <meta property="og:description" content={description} />
         <meta property="og:locale" content={locale} />
         {alternativeLocales.map((l) => (
           <meta property="og:locale:alternate" content={l} key={l} />