Inter Sozio Tech — Marketplace for Industrial Partnerships
( Role )
Logo Designer & Frontend Developer
( Scope )
- The logo
- The visual system
- Every page of the Next.js site
- English and German with i18next
- The request and partner forms with server-side validation
- The e-mail and storage adapters behind them
- Cookie consent
- SEO and structured data
- The content checks that run on every push
( Stack )
- Next.js
- i18next
- Nodemailer
- GitHub Actions
( Brief )
Finding the right manufacturing or service partner in Germany still runs on phone lists, trade-fair contacts and chance. Inter Sozio Tech is building a curated marketplace for it: a company describes what it needs, a person answers within 72 hours, and only providers with demonstrated capacity, original certificates and counter-confirmed references are admitted. The platform is in beta, so the site has to explain the idea honestly before there is a single listing to show.
( Approach )
I designed the logo — a gear around an "i" with rising bars — and built the website around it: the logo's lime for every call to action, a sky-blue hero, white rounded cards, Libre Caslon Condensed headlines with one italic word, DM Mono for labels. It runs in English and German, and every page is written to be indexed: metadata, canonicals, structured data, a sitemap.
Behind the pages sits a taxonomy of 40 categories across five disciplines and seven sectors, a three-step request funnel, partner registration, service pages for four modules, insights, FAQ, examples and the legal pages. Data protection is part of the build rather than a disclaimer: hosting inside the EU, self-hosted fonts, opt-in consent, and a versioned snapshot of the consent text stored with every request.
( Challenge )
The marketplace does not exist yet, but the site has to sell it. Nothing may look like a provider that has not been admitted: the 28 illustrative companies stay in the code as fixtures, but no public page renders one, the provider route returns 404 and is kept out of the sitemap, and a content check fails the build if any of it is wired back up before there is a real, consented partner behind it. Each form says only what the server actually did with the request.
( Responsibilities )
The logo, the visual system, every page of the Next.js site, English and German with i18next, the request and partner forms with server-side validation, the e-mail and storage adapters behind them, cookie consent, SEO and structured data, and the content checks that run on every push.
