Postgres.ai v2
Goal
- Migrate current pages to the Docusaurus v2.
- Improve primary landing.
Technical details
Engine
We are migrating to Docusaurus v2 to use for our documentation and landing pages. Docusaurus supports React and rendering of JSX, e.g. we can use JSX in MarkDown files or simply create .js
files. Read more about capabilities in Docusaurus documentation | Creating Pages (best page to start from).
CI/CD
Docusaurus can be built and run locally with npm run start
. We are using GitLab CI to automatically deploy all changes from staging-v2
branch to publicly accessible https://v2.postgres.ai domain.
Git
Your commits should be signed. Read how to configure it TODO:here.
TODO
- Pages (prioritized order)
- Resources table
- Primary landing
- Products: Checkup
- Products: Joe
- Careers table
- Products: Nancy (do we need the page? or remove it?)
- Fix HubSpot forms integration. We are using HubSpots form embeded to our site with
script
tags, it seems thatscript
cannot be simply used in React (JSX). Seesrc/pages/get-whitepaper-how-to-prepare-postgreqsl-databases-for-black-friday-and-cyber-monday.md
, for example. The script should be embeded, see how it works currently: https://postgres.ai/get-whitepaper-how-to-prepare-postgreqsl-databases-for-black-friday-and-cyber-monday/ - Make the
Sign in
button in the menu orange like we have currently.
Requirements
- Should look good in both light and dark themes.
- Should look good in both mobile and desktop.
Internal tasks
- Keep using
postgres.ai/signin
part from thefrontend
service, configure NGINX
Steps
-
Landing (value proposition, features, companies, open-source sections), list pages, and HubSpot forms -
Finish mockup -
Approve landing -
Find contractor -
Work -
Approve the results, deploy
-
-
Landing (resources with success stories, pricing sections) -
(lower priority) SEO-optimized success stories pages -
(lower priority) product landings
Edited by Anatoly Stansler