A body of work, with room for the thinking behind it.
A portfolio can contain many projects and still leave a visitor unsure what connects them. Software, AI, infrastructure, and product thinking each bring their own language. Presenting them as a list risks asking the reader to assemble the story that the website should make easier to understand.
Endrare is my personal archive of products, case studies, and field notes. It brings together technical work and experiences that changed how I build, including restaurant operations in Sweden. The challenge is to communicate a direction quickly while keeping enough depth available for someone who wants the evidence.
The site gives selected work an accessible entry point and connects it to product pages, essays, and notes. Visitors can follow a project, explore the thinking archive, or take a guided route through the work. Contact remains a direct conversation rather than a complex intake process.
A shared typographic language keeps the studio recognisable. Color gives each product room to be itself. Explore a few of the materials behind this site.
Lilac / Quiet possibility
Start with selected projects and the central description of the practice. The first view provides orientation: what I build, how I approach problems, and where a visitor can go next. It is an invitation to explore a direction rather than absorb everything at once.
Open a product page, case study, or field note to see the problem and the decisions behind the work. Related material connects practical examples to broader ideas, such as cognitive load, trust, operational pressure, and the role of infrastructure in an experience.
Continue through the archive or use the conversation page to make contact. The email address is available directly and can be copied. The website’s final job is to make a relevant next action easy after the visitor has found enough context.
Selected work establishes the direction; detail pages and the journal provide depth. That sequence reflects the idea that a visitor should not have to inspect every project before understanding the connection between them.
The archive gives product thinking a substantive place. Case studies and field notes explain experiences and trade-offs that a project image cannot, allowing the site to represent a developing practice through more than visual summaries.
Shared product and article metadata supports navigation, canonical routes, and search metadata. The architecture keeps the public archive connected as its content grows, with standalone articles retaining the depth and reading interactions they need.
Endrare is a live personal website and an ongoing body of work. The projects it documents have different statuses, from bachelor and thesis work to personal automation and active concepts. Their presence in the same archive should not imply the same level of release, validation, or availability.
As more work is added, which paths will help readers find relevant connections without making navigation heavier? What deserves a full case study, and what is better as a short field note? Those editorial questions should guide the next additions as much as the visual design.
Shared moments. Simply settled.