This isn't designed as of yet, the only thing clear at the moment is that it is supposed to be viewable as either its own page and as a modal.

components:

• #72
• #77
• #73
• #76
• #78
• #75

pages / more complex structures:

• #70
• #79
• #80
• #82
• #81
• #83

other:

• #71

There were a few things still missing in PR #61, these will be addressed here:

• a few translations here and there
• layout fixes where different translations have given elements different sizes per language
• language switching using some kind of UI
• persisting language choices

Take a look at our erd

A system which creates a config object based on environment variables and does some basic type checking (preferably using zod).
This can then be used wherever and does environment variable handling (especially when it comes to default values) is centralized.

Potential problem is that some things get executed during nextjs' build step.

Basically make open graph link validators happy, set appropriate <title />-tags per page, add a favicon, manifest.json, ...

Dream up the endpoints 🥹, the backend isn't all that far yet 😕

It should be documented in the README.MD the development process

Currently, the linter only lints app instead of both app and landing-page.

Basic sections like shown in figma

Current design approach: ignore/redesign-contact-section

We should also add the notice for BrowserStack to our repositories.

This project is tested with BrowserStack.

Can remain mostly empty, filling it with actual content is its own issue

Jannik designed a new contact page. We can implement this in the future. Low priority because we already have a decent contact page.

• Informations about the project
• Basic informations about the Team?
• Contact infos -> HubSpot Form?
• Images? Mocks?

On the long run we should be able to serve different languages (english and german).

#85 (comment)
According to @JannikWibker we should create a wrapper around the gRPC-web codegen.

reference: https://twind.style & https://github.com/tw-in-js/twind

Twind is a replacement for Tailwind which is compatible with Tailwind's classname system but generates the styles on the fly. This removes one major annoyance with Tailwind, this being not being able properly work with conditional styles.
With SSR this isn't anything all too different from just using tailwind as the backend generates styles and hands these over to the client. The important difference now is that the client can continue to generate styles for new branches taken during execution.

Getting twind working just how you want it is somewhat complicated and requires a little bit of digging through source code

limited in scope to reduce feature creep

Fill landingpage with some descriptive texts for helpwave

Button, Checkbox, etc.

no need for having husky around with a properly configured CI, it's doing nothing of value and only slowing down development

• Merge teams and partners sections
• Remove roadmap sections

• Set default language to german
• Merge contacts with a new text sections
• Shorten feature texts

• Different routes / views for our erd entities
• Mock for user settings / user-icon in navbar
• Settings page
• Button component (maybe some others as well)

• #31
• #32
• #33
• #37
• #53

We need a sign-in and sign-up for our dashboard. We authenticate a user by email and password.

The contact form on that page should track name, email and a message.

Create a separate package called @helpwave/common (file path: common/; this name can be chosen freely, this won't be published anywhere (as of yet!)), which contains common files such as i18n related things, a few components, a partial twind config (colors most importantly), and anything else that comes up that is better shared between app/ and landing-page/.

I kind of want to do something experimental with this as well: we won't transpile the TypeScript to JavaScript, we will import the TypeScript files directly, this might require some finessing with bundling however and I'm not sure how this may work out with dependencies.

Here's how I imagine this being used:
import { useTranslation } from '@helpwave/common/hooks/useTranslation'

• Twitter
• Instagram
• GitHub
• LinkedIn

• Team member pill
• Team member section