[{"data":1,"prerenderedAt":705},["ShallowReactive",2],{"article-alternates":3,"article-\u002Fde\u002Flifestyle\u002Ftechstack-partnership":13},{"i18nKey":4,"paths":5},"lifestyle-004-2026-05",{"de":6,"en":7,"es":8,"fr":9,"it":10,"ru":11,"tr":12},"\u002Fde\u002Flifestyle\u002Ftool-stack-2026-operationelle-wirbelsaeule","\u002Fen\u002Flifestyle\u002Ftool-stack-2026-roibase-daily-operations","\u002Fes\u002Flifestyle\u002Ftechstack-2026-operaciones-diarias","\u002Ffr\u002Flifestyle\u002Ftechstack-partnership","\u002Fit\u002Flifestyle\u002Ftech-stack-2026-operazioni-team","\u002Fru\u002Flifestyle\u002Ftool-stack-2026-operational-backbone","\u002Ftr\u002Flifestyle\u002Ftool-stack-2026-roibasein-operasyonel-omurgasi",{"_path":14,"_dir":15,"_draft":16,"_partial":16,"_locale":17,"title":18,"description":19,"publishedAt":20,"modifiedAt":20,"category":21,"i18nKey":4,"tags":22,"readingTime":28,"author":29,"body":30,"_type":699,"_id":700,"_source":701,"_file":702,"_stem":703,"_extension":704},"\u002Fde\u002Flifestyle\u002Ftechstack-partnership","lifestyle",false,"","Tool Stack 2026: Tägliche Abläufe des Roibase Teams","Linear, Notion, Slack, Figma, Granola — Integrationsmuster und messbare Produktivitätsdisziplin in einem 12-köpfigen Wachstumsteam.","2026-05-30","techstack-partnership",[23,24,25,26,27],"tool-stack","async-workflow","linear","notion","team-operations",8,"Roibase",{"type":31,"children":32,"toc":684},"root",[33,41,48,68,76,111,123,130,155,161,173,182,187,195,239,244,250,271,304,312,342,347,353,358,363,369,397,407,412,418,423,562,567,573,578,586,604,612,630,638,668,673,679],{"type":34,"tag":35,"props":36,"children":37},"element","p",{},[38],{"type":39,"value":40},"text","Tool-Stack-Diskussionen enden meistens in einer Katalogliste: „Wir nutzen diese Apps.\" Das eigentliche Problem ist aber nicht das einzelne Tool — es sind die Integrationsmuster, die Kosten des Context Switching, die Async-First-Disziplin. Das Roibase-Team arbeitet seit 2018 zu zwölft remote-first. 2026 prägen fünf Tools unsere tägliche Operation: Linear, Notion, Slack, Figma, Granola. Dieser Artikel listet die Tools nicht auf — stattdessen dekodieren wir die Integrationenschicht: Wo lebt welches Datum, welcher Workflow triggert was, welche Benachrichtigungsschicht ist abgeschaltet.",{"type":34,"tag":42,"props":43,"children":45},"h2",{"id":44},"linear-nicht-sprint-sondern-flow-metriken",[46],{"type":39,"value":47},"Linear: Nicht Sprint, sondern Flow-Metriken",{"type":34,"tag":35,"props":49,"children":50},{},[51,53,59,61,66],{"type":39,"value":52},"Linear wird als Projektmanagement-Tool verkauft, bei Roibase funktioniert es aber als „Work-in-Progress-Sichtbarkeitslayer\". Wir planen keine Sprints — nutzen keine Zyklen oder Milestones. Stattdessen bekommt jedes Issue eine ",{"type":34,"tag":54,"props":55,"children":56},"strong",{},[57],{"type":39,"value":58},"Priority (P0\u002FP1\u002FP2)",{"type":39,"value":60}," und ein ",{"type":34,"tag":54,"props":62,"children":63},{},[64],{"type":39,"value":65},"Estimate (1-3-5-8)",{"type":39,"value":67},". Die Priority setzt das System, nicht die Person: P0 = Deployment wird heute blockiert, P1 = muss im Zyklus erledigt sein, P2 = Backlog.",{"type":34,"tag":35,"props":69,"children":70},{},[71],{"type":34,"tag":54,"props":72,"children":73},{},[74],{"type":39,"value":75},"Flow-Metriken:",{"type":34,"tag":77,"props":78,"children":79},"ul",{},[80,91,101],{"type":34,"tag":81,"props":82,"children":83},"li",{},[84,89],{"type":34,"tag":54,"props":85,"children":86},{},[87],{"type":39,"value":88},"Cycle Time:",{"type":39,"value":90}," Von Issue-Eröffnung bis Abschluss durchschnittlich 2,3 Tage (Q4 2025 Daten). Issues über 5 Tage eskalieren automatisch auf P0.",{"type":34,"tag":81,"props":92,"children":93},{},[94,99],{"type":34,"tag":54,"props":95,"children":96},{},[97],{"type":39,"value":98},"Work-in-Progress-Limit:",{"type":39,"value":100}," Maximum 3 offene Issues pro Person. Ein 4. Issue kann nur angenommen werden, wenn eines davon geschlossen oder abgegeben wird.",{"type":34,"tag":81,"props":102,"children":103},{},[104,109],{"type":34,"tag":54,"props":105,"children":106},{},[107],{"type":39,"value":108},"Merge-to-Close-Zeit:",{"type":39,"value":110}," Vom PR-Merge bis zum Linear-Abschluss — Ziel \u003C30 Minuten (CI\u002FCD + QA Automation).",{"type":34,"tag":35,"props":112,"children":113},{},[114,116,121],{"type":39,"value":115},"Die Slack-Integration von Linear ist abgeschaltet. Statt Benachrichtigungsbombardement nutzen wir ein ",{"type":34,"tag":54,"props":117,"children":118},{},[119],{"type":39,"value":120},"Digest-System",{"type":39,"value":122},": Jeden Morgen 09:00 Uhr geht eine tägliche Zusammenfassung in den Slack-Channel (P0-Issue-Anzahl, Cycle-Time-Durchschnitt, WIP-Verteilung). Niemand erwähnt Linear in Slack — alle lesen morgens das Digest.",{"type":34,"tag":124,"props":125,"children":127},"h3",{"id":126},"linear-notion-synchronisierung",[128],{"type":39,"value":129},"Linear → Notion Synchronisierung",{"type":34,"tag":35,"props":131,"children":132},{},[133,135,142,144,153],{"type":39,"value":134},"Abgeschlossene Linear-Issues werden wöchentlich in Notion archiviert (Zapier Workflow). Notion hat eine „Retrospective Database\" — jedes geschlossene Issue wird nach zugehörigem Service getaggt. Beispiel: Issues zum Projekt ",{"type":34,"tag":136,"props":137,"children":139},"code",{"className":138},[],[140],{"type":39,"value":141},"branding",{"type":39,"value":143}," werden unter dem Service ",{"type":34,"tag":145,"props":146,"children":150},"a",{"href":147,"rel":148},"https:\u002F\u002Fwww.roibase.com.tr\u002Fde\u002Fbranding",[149],"nofollow",[151],{"type":39,"value":152},"Markenconsulting & Brand Identity",{"type":39,"value":154}," rapportiert. Diese Daten nutzen wir vierteljährlich zur Capacity-Planung: Wie viel Engineering-Zeit steckt in welchem Service?",{"type":34,"tag":42,"props":156,"children":158},{"id":157},"notion-source-of-truth-keine-wiki",[159],{"type":39,"value":160},"Notion: Source of Truth, Keine Wiki",{"type":34,"tag":35,"props":162,"children":163},{},[164,166,171],{"type":39,"value":165},"Notion nutzen wir nicht als Wiki — sondern als „Decision Log\". Jede strategische Entscheidung (z.B. „Server-Side oder Client-Side Tracking für Kampagne X?\") wird in Notion als ",{"type":34,"tag":54,"props":167,"children":168},{},[169],{"type":39,"value":170},"RFC (Request for Comments)",{"type":39,"value":172}," dokumentiert. RFC-Template:",{"type":34,"tag":174,"props":175,"children":177},"pre",{"code":176},"## Entscheidung\n[Ein Satz — was tun wir]\n\n## Kontext\n[Warum ist das jetzt nötig]\n\n## Alternativen\n[Mindestens 2 Optionen + Tradeoff-Tabelle]\n\n## Messung\n[Wie prüfen wir in 4 Wochen, ob die Entscheidung richtig war]\n\n## Verantwortung\n[Wer trägt die Verantwortung]\n",[178],{"type":34,"tag":136,"props":179,"children":180},{"__ignoreMap":17},[181],{"type":39,"value":176},{"type":34,"tag":35,"props":183,"children":184},{},[185],{"type":39,"value":186},"Nach RFC-Eröffnung gibt es 48 Stunden async Comment-Zeit. Niemand ruft eine Besprechung ein — alle lesen asynchron, schreiben Kommentare. Nach 48 Stunden schreibt der Decision Owner die endgültige Entscheidung, die Arbeit wandert in Linear.",{"type":34,"tag":35,"props":188,"children":189},{},[190],{"type":34,"tag":54,"props":191,"children":192},{},[193],{"type":39,"value":194},"Datenschichten in Notion:",{"type":34,"tag":196,"props":197,"children":198},"ol",{},[199,209,219,229],{"type":34,"tag":81,"props":200,"children":201},{},[202,207],{"type":34,"tag":54,"props":203,"children":204},{},[205],{"type":39,"value":206},"RFC Database",{"type":39,"value":208}," — alle Entscheidungen",{"type":34,"tag":81,"props":210,"children":211},{},[212,217],{"type":34,"tag":54,"props":213,"children":214},{},[215],{"type":39,"value":216},"Retrospective Database",{"type":39,"value":218}," — erledigte Arbeiten aus Linear",{"type":34,"tag":81,"props":220,"children":221},{},[222,227],{"type":34,"tag":54,"props":223,"children":224},{},[225],{"type":39,"value":226},"Client Playbook",{"type":39,"value":228}," — Operationsnoten pro Klient (wo ist welches Dashboard, welcher API-Key)",{"type":34,"tag":81,"props":230,"children":231},{},[232,237],{"type":34,"tag":54,"props":233,"children":234},{},[235],{"type":39,"value":236},"Brand Assets",{"type":39,"value":238}," — Figma-Links, Tone-of-Voice-Dokument",{"type":34,"tag":35,"props":240,"children":241},{},[242],{"type":39,"value":243},"Notion-Suche funktioniert nicht optimal, sagen Leute. Aber wir suchen gar nicht — jede Database ist filterbar und getaggt. Wenn jemand suchen möchte, bedeutet das meist: „Ich habe das Datum am falschen Ort abgelegt.\"",{"type":34,"tag":42,"props":245,"children":247},{"id":246},"slack-async-first-real-time-second",[248],{"type":39,"value":249},"Slack: Async-First, Real-Time-Second",{"type":34,"tag":35,"props":251,"children":252},{},[253,255,261,263,269],{"type":39,"value":254},"Die Notification-Logik von Slack ist teamweit deaktiviert. Nur ",{"type":34,"tag":136,"props":256,"children":258},{"className":257},[],[259],{"type":39,"value":260},"@channel",{"type":39,"value":262}," und ",{"type":34,"tag":136,"props":264,"children":266},{"className":265},[],[267],{"type":39,"value":268},"@here",{"type":39,"value":270}," sind aktiviert — und es gibt eine Regel dafür: außer P0 Incidents verboten. Messaging ist auf 3 Kanäle aufgeteilt:",{"type":34,"tag":196,"props":272,"children":273},{},[274,284,294],{"type":34,"tag":81,"props":275,"children":276},{},[277,282],{"type":34,"tag":54,"props":278,"children":279},{},[280],{"type":39,"value":281},"#daily-digest:",{"type":39,"value":283}," Linear\u002FNotion-Zusammenfassungen, CI\u002FCD Deploy-Logs",{"type":34,"tag":81,"props":285,"children":286},{},[287,292],{"type":34,"tag":54,"props":288,"children":289},{},[290],{"type":39,"value":291},"#async-questions:",{"type":39,"value":293}," Fragen, wo sofortige Antwort nicht erwartet wird (Antwort innerhalb 24 Stunden ausreichend)",{"type":34,"tag":81,"props":295,"children":296},{},[297,302],{"type":34,"tag":54,"props":298,"children":299},{},[300],{"type":39,"value":301},"#sync-now:",{"type":39,"value":303}," Echtzeitkoordination nötig (z.B. Production Incident, Live-Kampagnen-Optimierung)",{"type":34,"tag":35,"props":305,"children":306},{},[307],{"type":34,"tag":54,"props":308,"children":309},{},[310],{"type":39,"value":311},"Response-Time-Erwartungen:",{"type":34,"tag":77,"props":313,"children":314},{},[315,326,337],{"type":34,"tag":81,"props":316,"children":317},{},[318,324],{"type":34,"tag":136,"props":319,"children":321},{"className":320},[],[322],{"type":39,"value":323},"#sync-now",{"type":39,"value":325}," → 15 Minuten",{"type":34,"tag":81,"props":327,"children":328},{},[329,335],{"type":34,"tag":136,"props":330,"children":332},{"className":331},[],[333],{"type":39,"value":334},"#async-questions",{"type":39,"value":336}," → 24 Stunden",{"type":34,"tag":81,"props":338,"children":339},{},[340],{"type":39,"value":341},"DM → 48 Stunden (es gibt keine DM-Kultur, Kanäle werden genutzt)",{"type":34,"tag":35,"props":343,"children":344},{},[345],{"type":39,"value":346},"Slack-Threads sind obligatorisch. Direkte Kanalnachrichten sind untersagt — jede Nachricht eröffnet einen Thread. So vermischen sich parallele Gespräche nicht.",{"type":34,"tag":124,"props":348,"children":350},{"id":349},"slack-granola-integration",[351],{"type":39,"value":352},"Slack → Granola Integration",{"type":34,"tag":35,"props":354,"children":355},{},[356],{"type":39,"value":357},"Granola ist ein Meeting-Notes-Tool — bei Roibase nutzen wir es aber nur für Client Calls. Interne Meetings gibt es nicht (0–1 Sync Calls pro Woche). Nach dem Client Call sendet Granola sein AI-Transcript in Slack, das Team liest async. Action Items werden automatisch in Linear-Issues umgewandelt (Zapier Trigger).",{"type":34,"tag":35,"props":359,"children":360},{},[361],{"type":39,"value":362},"Granolas Killer-Feature: Grenzenlose numerische Commitments im Transcript werden highlighted („In 2 Wochen A\u002FB-Test-Ergebnisse\", „CTR muss um 15 % steigen\"). Dafür gibt es automatische Reminders — niemand vergisst.",{"type":34,"tag":42,"props":364,"children":366},{"id":365},"figma-nicht-design-handoff-sondern-living-spec",[367],{"type":39,"value":368},"Figma: Nicht Design Handoff, sondern Living Spec",{"type":34,"tag":35,"props":370,"children":371},{},[372,374,380,382,388,389,395],{"type":39,"value":373},"Figma ist nicht nur ein Design-Tool — sondern die „Frontend-Spec\"-Schicht. Jede UI Component ist in Figma als Variant definiert. Developer kopiert keinen Code aus Figma (keine Copy-CSS-Aktivitäten) — aber liest das Component-Behaviour davon. Zum Beispiel: Ein Button hat in Figma ",{"type":34,"tag":136,"props":375,"children":377},{"className":376},[],[378],{"type":39,"value":379},"hover",{"type":39,"value":381},", ",{"type":34,"tag":136,"props":383,"children":385},{"className":384},[],[386],{"type":39,"value":387},"active",{"type":39,"value":381},{"type":34,"tag":136,"props":390,"children":392},{"className":391},[],[393],{"type":39,"value":394},"disabled",{"type":39,"value":396}," States als Frames. Der Code implementiert dieselbe State-Logik.",{"type":34,"tag":35,"props":398,"children":399},{},[400,405],{"type":34,"tag":54,"props":401,"children":402},{},[403],{"type":39,"value":404},"Figma → Linear Verbindung:",{"type":39,"value":406},"\nIn jeder Figma-Datei ist das Plugin „Linear Issue\" installiert. Nach Design-Genehmigung eröffnet der Designer direkt ein Linear Issue, pastet den Figma-Link in die Issue-Beschreibung. Der Developer nimmt sich das Issue — er kennt bereits das Design, fragt nicht nach.",{"type":34,"tag":35,"props":408,"children":409},{},[410],{"type":39,"value":411},"Figma-Kommentare fließen nicht in Slack (sonst Benachrichtigungschaos). Stattdessen ein wöchentliches „Figma Digest\" — offene Kommentare werden in Linear-Issues konvertiert.",{"type":34,"tag":42,"props":413,"children":415},{"id":414},"integrationsmuster-wo-lebt-das-datum",[416],{"type":39,"value":417},"Integrationsmuster: Wo lebt das Datum?",{"type":34,"tag":35,"props":419,"children":420},{},[421],{"type":39,"value":422},"Tool-Stack-Diskussionen starten meist mit „Welches Tool nutzt du?\" Die eigentliche Frage sollte aber sein: „Wo ist das Datum canonical?\" Bei Roibase ist Data Ownership so verteilt:",{"type":34,"tag":424,"props":425,"children":426},"table",{},[427,451],{"type":34,"tag":428,"props":429,"children":430},"thead",{},[431],{"type":34,"tag":432,"props":433,"children":434},"tr",{},[435,441,446],{"type":34,"tag":436,"props":437,"children":438},"th",{},[439],{"type":39,"value":440},"Datentyp",{"type":34,"tag":436,"props":442,"children":443},{},[444],{"type":39,"value":445},"Source of Truth",{"type":34,"tag":436,"props":447,"children":448},{},[449],{"type":39,"value":450},"Synchronisiert zu",{"type":34,"tag":452,"props":453,"children":454},"tbody",{},[455,474,492,510,528,546],{"type":34,"tag":432,"props":456,"children":457},{},[458,464,469],{"type":34,"tag":459,"props":460,"children":461},"td",{},[462],{"type":39,"value":463},"Aktive Arbeit (WIP)",{"type":34,"tag":459,"props":465,"children":466},{},[467],{"type":39,"value":468},"Linear",{"type":34,"tag":459,"props":470,"children":471},{},[472],{"type":39,"value":473},"Slack Daily Digest",{"type":34,"tag":432,"props":475,"children":476},{},[477,482,487],{"type":34,"tag":459,"props":478,"children":479},{},[480],{"type":39,"value":481},"Erledigte Arbeit (Retrospektiv)",{"type":34,"tag":459,"props":483,"children":484},{},[485],{"type":39,"value":486},"Notion",{"type":34,"tag":459,"props":488,"children":489},{},[490],{"type":39,"value":491},"Linear (archiviert)",{"type":34,"tag":432,"props":493,"children":494},{},[495,500,505],{"type":34,"tag":459,"props":496,"children":497},{},[498],{"type":39,"value":499},"Strategische Entscheidungen",{"type":34,"tag":459,"props":501,"children":502},{},[503],{"type":39,"value":504},"Notion (RFC)",{"type":34,"tag":459,"props":506,"children":507},{},[508],{"type":39,"value":509},"Linear (Action Items)",{"type":34,"tag":432,"props":511,"children":512},{},[513,518,523],{"type":34,"tag":459,"props":514,"children":515},{},[516],{"type":39,"value":517},"Client Meeting Notes",{"type":34,"tag":459,"props":519,"children":520},{},[521],{"type":39,"value":522},"Granola",{"type":34,"tag":459,"props":524,"children":525},{},[526],{"type":39,"value":527},"Slack Thread",{"type":34,"tag":432,"props":529,"children":530},{},[531,536,541],{"type":34,"tag":459,"props":532,"children":533},{},[534],{"type":39,"value":535},"UI Spec",{"type":34,"tag":459,"props":537,"children":538},{},[539],{"type":39,"value":540},"Figma",{"type":34,"tag":459,"props":542,"children":543},{},[544],{"type":39,"value":545},"Linear Issue-Beschreibung",{"type":34,"tag":432,"props":547,"children":548},{},[549,553,557],{"type":34,"tag":459,"props":550,"children":551},{},[552],{"type":39,"value":236},{"type":34,"tag":459,"props":554,"children":555},{},[556],{"type":39,"value":486},{"type":34,"tag":459,"props":558,"children":559},{},[560],{"type":39,"value":561},"Figma (Embed Link)",{"type":34,"tag":35,"props":563,"children":564},{},[565],{"type":39,"value":566},"Kein duales Source-of-Truth. Falls ein Datum an zwei Stellen canonical aussieht, stimmt eins nicht.",{"type":34,"tag":42,"props":568,"children":570},{"id":569},"benachrichtigungsdisziplin-wann-stumm-wann-lärm",[571],{"type":39,"value":572},"Benachrichtigungsdisziplin: Wann stumm, wann Lärm",{"type":34,"tag":35,"props":574,"children":575},{},[576],{"type":39,"value":577},"Die größte Gefahr bei modernem Tool-Stack ist Notification Creep. Bei Roibase sieht die Benachrichtigungsstrategie so aus:",{"type":34,"tag":35,"props":579,"children":580},{},[581],{"type":34,"tag":54,"props":582,"children":583},{},[584],{"type":39,"value":585},"Vollständig abgeschaltet:",{"type":34,"tag":77,"props":587,"children":588},{},[589,594,599],{"type":34,"tag":81,"props":590,"children":591},{},[592],{"type":39,"value":593},"Linear Mentions (stattdessen Slack Thread)",{"type":34,"tag":81,"props":595,"children":596},{},[597],{"type":39,"value":598},"Figma-Kommentare (wöchentliches Digest)",{"type":34,"tag":81,"props":600,"children":601},{},[602],{"type":39,"value":603},"Notion Page Updates (niemand watched)",{"type":34,"tag":35,"props":605,"children":606},{},[607],{"type":34,"tag":54,"props":608,"children":609},{},[610],{"type":39,"value":611},"Als Digest:",{"type":34,"tag":77,"props":613,"children":614},{},[615,620,625],{"type":34,"tag":81,"props":616,"children":617},{},[618],{"type":39,"value":619},"Linear Daily Summary (morgens 09:00 Uhr)",{"type":34,"tag":81,"props":621,"children":622},{},[623],{"type":39,"value":624},"Figma Open Comments Summary (Freitag 17:00 Uhr)",{"type":34,"tag":81,"props":626,"children":627},{},[628],{"type":39,"value":629},"CI\u002FCD Deploy Log (nach jedem Deploy Slack-Zusammenfassung)",{"type":34,"tag":35,"props":631,"children":632},{},[633],{"type":34,"tag":54,"props":634,"children":635},{},[636],{"type":39,"value":637},"Echtzeit:",{"type":34,"tag":77,"props":639,"children":640},{},[641,651,656],{"type":34,"tag":81,"props":642,"children":643},{},[644,649],{"type":34,"tag":136,"props":645,"children":647},{"className":646},[],[648],{"type":39,"value":260},{"type":39,"value":650}," (nur P0 Incident)",{"type":34,"tag":81,"props":652,"children":653},{},[654],{"type":39,"value":655},"Granola Client Call Summary (5 Minuten nach Call-Ende)",{"type":34,"tag":81,"props":657,"children":658},{},[659,661,666],{"type":39,"value":660},"Production Error (Sentry → Slack, aber nur in ",{"type":34,"tag":136,"props":662,"children":664},{"className":663},[],[665],{"type":39,"value":323},{"type":39,"value":667},")",{"type":34,"tag":35,"props":669,"children":670},{},[671],{"type":39,"value":672},"Bei jedem neuen Tool ist die erste Frage: „Sollte das Echtzeit oder als Digest laufen?\" Default-Antwort: Digest.",{"type":34,"tag":42,"props":674,"children":676},{"id":675},"was-tun-wir-jetzt",[677],{"type":39,"value":678},"Was tun wir jetzt?",{"type":34,"tag":35,"props":680,"children":681},{},[682],{"type":39,"value":683},"Statt in Tool-Stack-Gesprächen „Lasst uns auch das verwenden\" zu reflexartig zu kopieren, sollte man fragen: „Wo sollte das Datum canonical sein?\" Roibases 2026-Stack läuft auf Linear\u002FNotion\u002FSlack\u002FFigma\u002FGranola, aber diese Tools sind austauschbar — wichtig ist das Integrationsmuster, die Benachrichtigungsdisziplin, die Async-First-Kultur. Falls im Team noch jemand sagt „Tool X sendet mir keine Benachrichtigungen,\" ist das Problem nicht das Tool — es ist: Data Ownership ist unklar.",{"title":17,"searchDepth":685,"depth":685,"links":686},3,[687,691,692,695,696,697,698],{"id":44,"depth":688,"text":47,"children":689},2,[690],{"id":126,"depth":685,"text":129},{"id":157,"depth":688,"text":160},{"id":246,"depth":688,"text":249,"children":693},[694],{"id":349,"depth":685,"text":352},{"id":365,"depth":688,"text":368},{"id":414,"depth":688,"text":417},{"id":569,"depth":688,"text":572},{"id":675,"depth":688,"text":678},"markdown","content:de:lifestyle:techstack-partnership.md","content","de\u002Flifestyle\u002Ftechstack-partnership.md","de\u002Flifestyle\u002Ftechstack-partnership","md",1782050760904]