Rebuilding the marketing site so it's deployable to GPages @virufy. It supports static exports with image optimization, and internationalized routing with App Router.
1. ../{en | es | ja}/bio/amil
2. ../{en | es | ja}/bio/ankit
3. ../{en | es | ja}/bio/john
4. ../{en | es | ja}/bio/chris
5. ../{en | es}/virumap-msg
6. ../ja/virumap-msg
7. ../{en | es}/virumap-slides
8. ../ja/virumap-slides
I added placeholder metadata for Japanese for the following reasons:
if a user wanted to look at the virumap slides or virumap msg in Japanese, instead of creating 4 different routes like so,
a. ../{en | es}/virumap-msg
b. ../{en | es}/virumap-msg-jp
c. ../{en | es}/virumap-slides
d. ../{en | es}/virumap-slides-jp
We can just leverage the locale to determine which document the url should redirect to. For example, if a user wants to see the japanese version of virumap-msg or virumap-slides, go to ../ja/virumap-msg or ../ja/virumap-slides.
Japanese will be one of the languages the site will need to support.
Addresses #47
To test locally,
..
representslocalhost:{port}
:I added placeholder metadata for Japanese for the following reasons:
../{en | es}/virumap-msg
b.../{en | es}/virumap-msg-jp
c.../{en | es}/virumap-slides
d.../{en | es}/virumap-slides-jp
We can just leverage the locale to determine which document the url should redirect to. For example, if a user wants to see the japanese version of virumap-msg or virumap-slides, go to
../ja/virumap-msg
or../ja/virumap-slides
.