Ontola Home Page

Future home page for Ontola.

Running locally

# Install dependencies
pnpm i
# run dev server
pnpm dev

Deployment

We deploy to AWS Amplify, which is built automatically on pushing commits to github. See amplify.yml file for configuration. Since we use I18n, we can't export the site. Let's hope that changes one day!

Environment variables:

# analytics / tracking
NEXT_PUBLIC_MATOMO_URL=https://analytics.argu.co/
NEXT_PUBLIC_MATOMO_SITE_ID=4
# fixes build issue
AMPLIFY_NEXTJS_EXPERIMENTAL_TRACE=true
# helps with building sitemaps
SITE_URL=https://ontola.io

Adding content

• Written content resides in the content directory.
• Blog post: Create a article-title.en.mdx file in content/blog. Make sure to add a title and a description. Create a Dutch translation with the same name (article-title.nl.mdx), too.
• Tech item: Similar to above, but also make sure to add a techname.svg image to public/images/tech.
• Service: Similar to above, but also make sure to update the content/services/{servicename}.{lang}.mdx file accordingly. You may need to add a FeatureBlock there.
• Custom page: Create a .tsx file in src/pages with the name of the path. Probably easiest to clone about.tsx and copy that logic.
• Translations: We use next-i18next for translations. Most translations are in markdown (.mdx) documents, but some (such as menu item content) are stored in public/locales as .json files.

Tech

• Loosely based on this boilerplate.
• stitches is used for styling