1<!doctype html> 2<html lang="en"> 3 <head> 4 <meta charset="utf-8" /> 5 <meta name="viewport" content="width=device-width, initial-scale=1" /> 6 <meta name="theme-color" content="#0F3020" /> 7 <link rel="icon" href="./favicon.svg" type="image/svg+xml" /> 8 <link 9 rel="preload" 10 href="./fonts/fraunces-latin-var.woff2" 11 as="font" 12 type="font/woff2" 13 crossorigin 14 /> 15 <!--gsrl61--><meta name="description" content="You saved these things on purpose. The platforms buried them. Locus gives them back as a library you own."/> <link rel="canonical" href="https://studiolocus.app/manifesto"/> <meta property="og:type" content="website"/> <meta property="og:site_name" content="Locus"/> <meta property="og:title" content="Manifesto - Locus"/> <meta property="og:description" content="You saved these things on purpose. The platforms buried them. Locus gives them back as a library you own."/> <meta property="og:image" content="https://studiolocus.app/og.png"/> <meta property="og:url" content="https://studiolocus.app/manifesto"/> <meta name="twitter:card" content="summary_large_image"/><!----><title>Manifesto - Locus</title> 16 <link href="./_app/immutable/assets/0.BZVh43xN.css" rel="stylesheet"> 17 <link href="./_app/immutable/assets/5.BXPR0Uei.css" rel="stylesheet"> 18 </head> 19 <body data-sveltekit-preload-data="hover"> 20 <div style="display: contents"><!--[--><!--[0--><!--[--><a class="skip-link svelte-12qhfyh" href="#main">Skip to content</a> <header class="site-header svelte-12qhfyh"><div class="container header-row svelte-12qhfyh"><a class="wordmark svelte-12qhfyh" href="/">Locus</a> <nav class="site-nav svelte-12qhfyh" aria-label="Primary"><a href="/how-it-works" class="svelte-12qhfyh">How it works</a> <a href="/pricing" class="svelte-12qhfyh">Pricing</a> <a href="/manifesto" class="svelte-12qhfyh">Manifesto</a></nav> <a class="app-link svelte-12qhfyh" href="https://my.studiolocus.app">Open the web app</a> <a class="btn btn-primary header-cta svelte-12qhfyh" href="/get-started">Get started</a></div></header> <main id="main" class="svelte-12qhfyh"><!--[--><!----> <section class="page-head svelte-1biftg1"><div class="container-text"><p class="eyebrow">Manifesto</p> <h1>You saved it on purpose.</h1> <p class="lede">Every save had a reason: a concept you wanted to understand, a project you 21 meant to start, a place, a recipe, a way of living you were working 22 toward. What happened to those reasons afterwards is why Locus exists.</p></div></section> <section class="articles svelte-1biftg1"><div class="container-text"><ol class="thesis svelte-1biftg1"><li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">I</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">A save has a reason.</h2> <p class="svelte-1biftg1">Nobody saves by accident. Behind every save is something you 23 wanted: a concept to understand better, a project to take on, 24 inspiration for an interest, a resource for the person you are 25 trying to become. Cooking is one corner of it. Kept over years, 26 those saves are an honest record of what you actually care about.</p></div></li> <li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">II</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">Platforms profit from scrolling.</h2> <p class="svelte-1biftg1">Say it plainly: platforms make money when you keep scrolling. They 27 make nothing when you retrieve, organize, or use what you saved, 28 so they never built the tools for it. Technically you could do it 29 yourself: write the book recommendation down, spend five minutes 30 hunting for the recipe post you half remember, give it a format you 31 can use. You don't, and neither does anyone else, because there is 32 just enough friction to never start.</p></div></li> <li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">III</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">A save button should mean something.</h2> <p class="svelte-1biftg1">For years the save button led to a graveyard: tapped, and never 33 seen again. It only starts to mean something when what you 34 saved can be browsed, found, and used. Locus makes the save worth 35 pressing again.</p></div></li> <li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">IV</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">One big bucket is not a library.</h2> <p class="svelte-1biftg1">There have only ever been two options: throw everything into one 36 bucket, where a recipe, a workout, and a hotel all look the same, 37 or build a system of buckets yourself and maintain it, which nobody 38 keeps up. Cataloging fixes both. When a save is filed by what it 39 is, you can browse it and know what you are looking at.</p></div></li> <li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">V</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">The areas should fit you.</h2> <p class="svelte-1biftg1">Locus files into general areas, recipes and workouts and places 40 among them, and the specific lanes inside each one emerge from
41 what you actually save. An area with a few posts stays broad so it 42 is worth opening; an area that fills up splits into lanes so it 43 stays legible. The structure adapts to your interests instead of 44 asking you to design it. And the filing is visible: labels you can 45 read, in a library you can search, sort, and correct.</p></div></li> <li class="svelte-1biftg1"><span class="numeral svelte-1biftg1" aria-hidden="true">VI</span> <div class="article-body svelte-1biftg1"><h2 class="svelte-1biftg1">Old saves should resurface.</h2> <p class="svelte-1biftg1">Each time you open Locus, the groups in every area are reshuffled 46 and different posts lead. A save from three years ago comes back 47 around next to one from last week. Your library percolates instead 48 of sinking.</p></div></li></ol></div></section> <section class="pullquote svelte-1biftg1"><div class="container"><p class="quote svelte-1biftg1">A library you own,<br/>not a feed you rent.</p></div></section> <section class="close svelte-1biftg1"><div class="container-text"><p class="eyebrow svelte-1biftg1">The work</p> <h2>What we are doing about it.</h2> <p class="svelte-1biftg1">Locus syncs the posts you saved, files them so they can be found, and 49 turns them into things you can act on: cook mode, saved places on a map, 50 head-to-head rankings. Your saves, given back.</p> <div class="close-actions svelte-1biftg1"><a class="btn btn-primary" href="/get-started">Set up Locus</a> <a class="btn btn-ghost" href="/how-it-works">See how it works</a></div></div></section><!--]--><!----></main> <footer class="site-footer svelte-12qhfyh"><div class="container footer-grid svelte-12qhfyh"><div class="footer-brand svelte-12qhfyh"><a class="wordmark svelte-12qhfyh" href="/">Locus</a> <p class="footer-tag svelte-12qhfyh">Everything you saved, filed and ready.</p></div> <nav class="footer-col svelte-12qhfyh" aria-label="Product"><h2 class="footer-heading svelte-12qhfyh">Product</h2> <a href="/how-it-works" class="svelte-12qhfyh">How it works</a> <a href="/pricing" class="svelte-12qhfyh">Pricing</a> <a href="/get-started" class="svelte-12qhfyh">Get started</a></nav> <nav class="footer-col svelte-12qhfyh" aria-label="Trust"><h2 class="footer-heading svelte-12qhfyh">Trust</h2> <a href="/manifesto" class="svelte-12qhfyh">Manifesto</a> <a href="/privacy" class="svelte-12qhfyh">Privacy</a> <a href="/security" class="svelte-12qhfyh">Security</a> <a href="/support" class="svelte-12qhfyh">Support</a></nav></div> <div class="container footer-legal svelte-12qhfyh"><p class="svelte-12qhfyh">Studio Locus, 2026. Built for people who save things on purpose.</p></div></footer><!--]--><!--]--> <!--[-1--><!--]--><!--]--></div> 51 </body> 52</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.