Started by GitHub push by younex162264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/main2264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/main2264c156533706f135d03479119c61e6af91fa0d2264c156533706f135d03479119c61e6af91fa0drefs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.git2264c15/var/www/blut24.com/web/releases/6-2264c156-2264c15https://jenkins.younex.de/job/blut24-landing/6/artifacthttps://jenkins.younex.de/job/blut24-landing/changeshttps://jenkins.younex.de/job/blut24-landing/6/https://jenkins.younex.de/job/blut24-landing/6/testReportfalseCheckoutGuard: main onlyShip source to targetBuild, health-check and swapSmoke testfalse#6 2264c152654228038blut24-landing #6 2264c156false65451SUCCESS1785228290744https://jenkins.younex.de/job/blut24-landing/6/- app/pages/datenschutz.vue2264c156533706f135d03479119c61e6af91fa0d1785228279000https://jenkins.younex.de/user/infoinfoinfo@logyou.dedatenschutz: name the actual controller, matching the Impressum
Both pages must name the same responsible party or they contradict each other,
so the Verantwortlicher section now carries the same operator data as the
Impressum (Younes Kalakhi, IT Beratung & Dienstleistung, Lahnau) instead of
bracketed placeholders.
Two judgement calls, both noted in the file:
- the e-mail is still a placeholder because it is obfuscated on the source page
and could not be read; Art. 13 DSGVO requires a contact route, so it must be
filled before this is treated as live
- no Datenschutzbeauftragter is claimed - a freelancer of this size is generally
not required to appoint one under § 38 BDSG, and asserting one that does not
exist would be worse than saying none is appointed
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 10:44:39 +02002264c156533706f135d03479119c61e6af91fa0ddatenschutz: name the actual controller, matching the Impressumeditapp/pages/datenschutz.vue
githttps://jenkins.younex.de/user/infoinfoinfofalseStarted by GitHub push by younex174476c9c4298767c7d1e75e392fda5233727c5d914476c9c4298767c7d1e75e392fda5233727c5d91refs/remotes/origin/main4476c9c4298767c7d1e75e392fda5233727c5d914476c9c4298767c7d1e75e392fda5233727c5d91refs/remotes/origin/main4476c9c4298767c7d1e75e392fda5233727c5d914476c9c4298767c7d1e75e392fda5233727c5d91refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#7 4476c9c2682928038blut24-landing #7 4476c9c7false75453SUCCESS1785228855796https://jenkins.younex.de/job/blut24-landing/7/- app/components/SectionCourier.vueapp/components/SectionHowItWorks.vueapp/components/SectionHero.vueapp/components/SiteFooter.vueapp/components/SectionRegistration.vueapp/components/SectionProof.vue4476c9c4298767c7d1e75e392fda5233727c5d911785228842000https://jenkins.younex.de/user/infoinfoinfo@logyou.delanding: copy pass — courier value proposition, step 4, spacing, footer
- Step 4 now says what actually happens: if the other clinic is on Blut24 too,
order, delivery note and unit data stay inside the system with nothing retyped
or faxed; DGTI-Lieferschein, PDF and e-mail remain available for houses that
are not yet connected, rather than being the default path.
- Courier section rewritten around the app: orders arrive on the phone, pickup
and delivery are confirmed there, and participation is free so a courier can
win additional runs without buying software. Kept strictly to goods transport
wording - no patient-transport terms.
- "dauerhaft kostenlos" -> "für Kliniken kostenlos" everywhere.
- Tightened the gap between the header and the hero headline on both breakpoints.
- Dropped the Bundes-Klinik-Atlas source line from the footer.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 10:54:02 +02004476c9c4298767c7d1e75e392fda5233727c5d91landing: copy pass — courier value proposition, step 4, spacing, footereditapp/components/SectionHowItWorks.vueeditapp/components/SectionProof.vueeditapp/components/SectionRegistration.vueeditapp/components/SectionHero.vueeditapp/components/SectionCourier.vueeditapp/components/SiteFooter.vue
githttps://jenkins.younex.de/user/infoinfofalse8https://jenkins.younex.de/job/blut24-landing/8/6https://jenkins.younex.de/job/blut24-landing/6/Started by GitHub push by younex159d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/main9d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/main9d957078b237f5dd9f22e2d14badac3ff8e33bd69d957078b237f5dd9f22e2d14badac3ff8e33bd6refs/remotes/origin/mainhttps://github.com/younex1/blut24-landing.gitfalse#5 9d957072664528038blut24-landing #5 9d957075false55449SUCCESS1785227610682https://jenkins.younex.de/job/blut24-landing/5/- deploy/README.mdapp/app.vueapp/components/SectionHero.vueserver/api/registration/submit.post.tsapp/components/SiteFooter.vueapp/components/SiteHeader.vueapp/components/SectionRegistration.vueapp/pages/datenschutz.vueREADME.mdapp/components/SectionCourier.vue.idea/vcs.xmlapp/components/SectionApp.vueapp/components/RegistrationDialog.vueserver/utils/registrationValidation.tsscripts/test-registration.mjsapp/composables/useRegistrationDialog.tsserver/utils/registrationDb.tsapp/components/AndroidBadge.vueapp/components/AppIcon.vueapp/components/RegistrationForm.vuedeploy/nginx-blut24.confapp/components/SectionProof.vue9d957078b237f5dd9f22e2d14badac3ff8e33bd61785227601000https://jenkins.younex.de/user/infoinfoinfo@logyou.delanding: modal registration, value-led proof band, autocomplete fix, APK live
- Registration moved into a native <dialog> modal driven from every CTA, with
focus trap/return, scroll lock, backdrop + ESC dismissal, full-screen sheet on
mobile and prefers-reduced-motion respected.
- Replaced the data-source stats ("Quelle: Bundes-Klinik-Atlas", 293, 906) with
three statements of what the product actually does. No invented metrics: the
only figure left is the real 1.581 Klinik-Atlas count that was already there.
- Fixed the autocomplete staying open after a clinic was picked. Root cause was
watch(query): selecting wrote the label back into the field, which the watcher
read as a new search and reopened the list ~220ms later. The input is now
:value + @input so a programmatic write cannot be a search intent, with a
pendingQuery flag gating every path that opens the list.
- Removed Anrede end-to-end. The DB column is deliberately NOT migrated: it keeps
its NOT NULL DEFAULT '' so inserts that omit it stay valid on existing databases.
- Android badge switched live: the APK is published at
https://blut24.com/downloads/blut24-mobile.apk and served from disk by nginx
with the correct package MIME type.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-28 10:33:21 +02009d957078b237f5dd9f22e2d14badac3ff8e33bd6landing: modal registration, value-led proof band, autocomplete fix, APK liveeditapp/components/AppIcon.vueeditapp/components/SectionHero.vueeditapp/components/SiteFooter.vueeditapp/components/SiteHeader.vueeditserver/utils/registrationValidation.tseditapp/app.vueeditapp/components/SectionCourier.vueeditscripts/test-registration.mjseditdeploy/README.mdeditapp/components/RegistrationForm.vueadd.idea/vcs.xmleditapp/components/SectionProof.vueaddapp/components/RegistrationDialog.vueeditREADME.mdeditapp/components/SectionApp.vueeditapp/pages/datenschutz.vueeditdeploy/nginx-blut24.confaddapp/composables/useRegistrationDialog.tseditserver/api/registration/submit.post.tseditapp/components/SectionRegistration.vueeditserver/utils/registrationDb.tseditapp/components/AndroidBadge.vue
githttps://jenkins.younex.de/user/infoinfofalse6https://jenkins.younex.de/job/blut24-landing/6/4https://jenkins.younex.de/job/blut24-landing/4/