# D.S. Landing page kickoff

Localisation
- Should we get started on this thinking now/
- We can use _our_ workflow, but need to extend to extra langauges
- They have a team too, perhaps we could onboard them to our translation services?

## What is "now" and when is it done?
- hello world?
- sandbox deployment
- This is a known and achieveable goal (S.M.A.R.T)
- Demonstrates progress

^ Milestone one! :rocket:

## Analytics
If we want to show progress, we need to have analytics to back it up

Connie is the expert on this. There are some gaps in reporting since the move from Domo to looker.

[Analytics Miro board](https://miro.com/app/board/uXjVOj3as48=/?share_link_id=137564410750)

Prahtiba is the vista resource for this

## Familisarisation with the process of making requests to Jetstream

- there's a confluence doc
- staging and prod

## Tradeoffs of microfrontend/self hosted/using their stuff
* If we go down the fully hosted route, we have to make a request to Jetstream. If we keep it in Gitlab we get a development preview branch
- We will move to Gitlab at some point too
- Infra trade offs : lambda, fargate, s3 bucket

Jolane weighs in with a preference for statically generated, knowing that products won't change that often

### What are we going for?
- Statically generated
- Server side rendered
- Dynamically

Touch base with Delivery Systems squad

## SEO

What does this page even show? If it's just our products and they're managed by our catalog, then there's complexity in static generation (but you get a boost from performance)

## Monitoring
What can we learn about their monitoring as we go through this process, in the context of consolidating tooling

- Do we insert ourselves into pagerduty or do we pull this into our ownership
- New relic? Uptime?
- If we want to, we can set up a datadog synthetic on just that page to be alerted if we have broken it (check for a 200 response and some basic page content)

# Milestone 2

When do we tip over from staging to prod?

- Iterate by using wireframes first, and filling in various sections as we can

We don't want to have to re-do anything, or much, so how can eng and UX work cross functionally on iterating towards the next version of the landing page.

Products or no products?

We _could_ do a whole static page in a week, but it doesn't progress a bunch of our engineering goals. But our eng options are biased towards the capabilites we are trying to better understand (especially as a partner capability). The objectives of the initial spike encompass more than _just_ the landing page's UX. We don't have to answer _everything_ in this project, but we should keep that objective in mind

## What are some definite guard rails?
Must haves for MVP
- monitoring
- sandbox deployed
- English only; kicked off localisation planning
- analytics
- well documented
- uses swann

Must haves for handed over page?
- localised
- design improvements
- Products?

**Action**
- Get Connie involved asap
- Get clarity around timeframes by which point eng needs wireframes or guidance, so product and UX can have time to iterate through options - estimate, maybe 2-4 sprints
- Maybe not wireframes, but content - data fetching needs etc.
- We do need _some_ rough guidance about the type of page this will be in order to make some calls