# notion Published articles for notion. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A Day of Sensemaking After Starting a New Job DevFeed: [A Day of Sensemaking After Starting a New Job]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-09-11T02:16:25Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [Notion](), [context](), [Tool]() Tags: [context](), [notion](), [product](), [workflows]() ### AI overview The author describes a day spent understanding a new product, its workflows, history, people, artifacts, and accumulated context. They use a subway-map metaphor and Notion tables to organize journeys, handoffs, data sources, and other materials, while questioning which information remains valid. ### Source excerpt I recently started a new job, which means I'm spending a lot of my time trying to figure out how everything works: the product, the workflows, the history, the people, the artifacts, and all the context that everyone else has accumulated over time. ## πŸŽ™ How I AI: How this PM uses Claude to handle 70% to 80% of his workday DevFeed: [πŸŽ™ How I AI: How this PM uses Claude to handle 70% to 80% of his workday]() Original publisher: [Read original article]() Author: Lenny Rachitsky Published: 2026-08-31T15:01:58Z Content type: article Language: en Sources: [Lenny's Newsletter]() Topics: [Claude](), [Artificial Intelligence](), [Notion](), [Slack](), [email]() Tags: [ai](), [claude](), [email](), [notion](), [podcast](), [slack]() ### AI overview A podcast episode explains how Melio product manager Daniel Blum built a self-improving AI system around Claude and Cowork. The system manages parts of his Notion workflow, prepares weekly and daily briefs, scans Slack and email for relevant context, asks questions about missing knowledge, and learns from his edits. Blum says it eventually handles 70% to 80% of his workday, while emphasizing that system architecture and continuously maintained context matter more than choosing a particular AI platform. ### Source excerpt Your weekly listens from How I AI, part of the Lenny's Podcast Network ## How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio) DevFeed: [How I turned Claude into a self-improving PM assistant | Daniel Blum (PM, Melio)]() Original publisher: [Read original article]() Author: Claire Vo Published: 2026-08-31T12:04:18Z Content type: article Language: en Sources: [Lenny's Newsletter]() Topics: [Claude](), [Notion](), [Slack](), [email](), [Artificial Intelligence](), [Automation](), [AI Infrastructure](), [User experience (UX)]() Tags: [agent-orchestration](), [automation](), [claude](), [email](), [notion](), [slack](), [ux]() ### AI overview A podcast episode in which Daniel Blum explains how he uses Claude and Cowork to manage Notion, Slack, and email workflows, automate weekly preparation, learn internal terminology, and identify improvements to his system. He also discusses scaling the setup to Melio's PM team and the remaining limitations. ### Source excerpt Listen now | πŸŽ™ PM Daniel Blum walks through the exact Cowork and Claude setup that manages his Notion, tracks his tasks across Slack and email, and self-improves every week without him lifting a finger ## Refactoring internal documentation in Notion DevFeed: [Refactoring internal documentation in Notion]() Original publisher: [Read original article]() Published: 2026-02-05T14:00:00Z Content type: article Language: en Sources: [Will Larson - Irrational Exuberance]() Topics: [Notion](), [Refactoring](), [code productivity](), [Documentation](), [API]() Tags: [ai](), [api](), [content](), [developer-productivity](), [documentation](), [git](), [notion](), [refactoring](), [survey]() ### AI overview A writeup of efforts to improve an organization's internal documentation after a migration from Confluence to Notion. It examines stale and duplicated pages, unclear ownership, Notion AI usage, and API limitations, then describes policies focused on reducing duplication and stale content and optimizing documentation for Notion AI. ### Source excerpt In our latest developer productivity survey, our documentation was the area with the second most comments. This is a writeup of the concrete steps I took to see how much progress one person could make on improving the organization's documentation while holding myself to a high standard for making changes that actually worked instead of optically sounding impressive. Diagnosis There were a handful of issues we were running into: We migrated from Confluence to Notion in January, 2025, which had left around a bunch of old pages that were "obviously wrong." These files created a bad smell around our other docs, as folks felt like things weren't well maintained. We had inconsistent approach to what we documented in Git-managed files versus managing in Notion. This led to duplication. Duplication meant that it felt safer to create an N+1th version, rather than debugging why N versions already existed. We've had a bunch of new folks join over the past year, who weren't sure if they were empowered to update documentation or if someone else was managing any given file We started using Notion AI as the primary mechanism for exposing content, which meant that hierarchical organization was less important, and that having inaccurate snippets was harmful even if they were tucked away into a quiet corner This was combined with a handful of interesting limitations in Notion itself: You cannot tell if a non-wiki page is verified or not via API. You can tell if a wiki page is verified via API, but no one uses wiki pages You cannot retrieve all pages in a Notion Teamspace via API, you instead have to manually take list of the top-level pages in that Teamspace, and find the children from those pages There is no "archive" functionality in Notion that allows you to exclude a document from search results There is no programmatic visibility into views or usage of a page via API except for how recently it was edited Policy The policy we adopted for addressing the above diagnosis was: Optimi ## How Dust uses Temporal to run real-time AI agents across workplace tools DevFeed: [How Dust uses Temporal to run real-time AI agents across workplace tools]() Original publisher: [Read original article]() Author: Clair Byrd Published: 2025-05-29T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [real-time](), [GitHub](), [Slack](), [engineering-culture]() Tags: [agentic-ai](), [ai](), [community](), [engineering-culture](), [github](), [notion](), [real-time](), [slack]() ### AI overview The article describes how Dust embeds AI agents in tools such as Slack, GitHub, Notion, Confluence, and Salesforce. It explains that Temporal provides the orchestration backbone for running these event-triggered workflows at scale and with reliability. ### Source excerpt Dust uses Temporal to power real-time AI agents that work inside Slack, GitHub, Notion, and more; scaling to 10M+ Activities/day with ease. ## Fibery vs. Notion 2025: not Better, Different DevFeed: [Fibery vs. Notion 2025: not Better, Different]() Original publisher: [Read original article]() Author: Michael Dubakov Published: 2025-04-11T07:52:12Z Content type: comparison Language: en Sources: [Stories by Michael Dubakov on Medium]() Topics: [Notion](), [knowledge-management](), [Product Management](), [Wiki](), [Low-Code / Internal Tools]() Tags: [2025](), [automation](), [notion](), [permissions](), [processes](), [product-management](), [productivity](), [saas-tools](), [tools-for-thought](), [visualization](), [vs](), [wiki]() ### AI overview A founder-authored comparison explains that Fibery and Notion serve different use cases rather than one being universally better. It presents Notion as well suited to personal knowledge management, company wikis, knowledge bases, and simple processes, while describing Fibery as better suited to complex processes with deeper hierarchies, relations, permissions, formulas, automations, and advanced visualizations. ### Source excerpt Disclaimer: This post is written by Fibery Founder, so it is inevitably biased (but I tried to be as objective as I can). You came here to find out how πŸ‰ Fibery is better than 🐼 Notion. Well, it is not. Fibery is different. Notion is a great tool and it works exceptionally well for some use cases, but it fails for others. Let me just quickly answer your main question and then feel free to dig into details later. 🐼 What Notion is great for? Personal knowledge management (PKM) Company wiki and knowledge base Simple (not complex) processes: basic project management, basic CRM, basic candidates tracking, etc. "I've been using Notion for the past few years. It's undoubtedly the most flexible note-taking app on the market. Offering both simplicity and complexity, it caters to a variety of users. Its recent integration with AI and automation further elevates the note-taking experience. Imagine having your own personal Wikipedia, comprehensive databases, calendar, tasks, calculator, and more, all within a single app. This truly makes Notion the best of the best." -- Notion userπŸ‰ What Fibery is great for? Company wiki and knowledge base Complex processes: product management, feedback management, portfolio management, OKR, HR, Vacation tracking, etc. "We use Fibery to manage all our startup processes, from customer discovery over HR until CRM, Project management and documentation. We could replace 27 of our 36 internal tools: Fibery is a rocket for managing all sorts of processes and lets us the freedom to create our own templates and spaces aka processes, if needed." -- Fibery user It can be illustrated like this: Notion and Fibery areas of best applicability Fibery will help you when Notion is just not enough. When you need deep hierarchies and relations, advanced access and permissions control, formulas and automations across these hierarchies, visualization of information in hierarchical timelines and table views, complex charts. In general, Fibery is harder to "get" and ma ## Announcing: Hackathon at Replay DevFeed: [Announcing: Hackathon at Replay]() Original publisher: [Read original article]() Author: Jessica West Published: 2023-08-15T06:00:00Z Content type: news Language: en Sources: [Temporal Blog]() Topics: [Hackathon](), [GitHub](), [Python](), [Notion]() Tags: [announcement](), [announcements](), [conference](), [github](), [hackathon](), [notion](), [python](), [seattle](), [temporal]() ### AI overview Temporal announces a Seattle hackathon held alongside the Replay conference. Participants will build sample applications using Temporal, with team formation supported through a private Slack channel and a schedule that includes virtual and onsite activities. ### Source excerpt Hackathon announcement and instructions for Replay, a conference hosted by Temporal in Seattle, Washington. ## Sync GitHub repos to Notion with Temporal Schedules DevFeed: [Sync GitHub repos to Notion with Temporal Schedules]() Original publisher: [Read original article]() Author: Loren Sands-Ramshaw Published: 2023-06-06T04:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [GitHub](), [Notion](), [Databases](), [API](), [TypeScript](), [Back end](), [client library]() Tags: [api](), [database](), [github](), [library](), [notion](), [reliability](), [temporal-concepts](), [typescript]() ### AI overview This tutorial explains an internal tool that synchronizes a GitHub organization's repositories, members, and contributor data into a Notion database. It describes the TypeScript implementation using the GitHub API and Notion client library, and shows how Temporal Schedules runs the sync daily with durable-function retries and continuation after machine failure. ### Source excerpt For a company hackathon, I built an internal tool that syncs your GitHub org's list of repositories to a Notion database. Here's how it works and how I implemented it. ## First time with Tailwind CSS: showing off my books! DevFeed: [First time with Tailwind CSS: showing off my books!]() Original publisher: [Read original article]() Published: 2022-06-21T00:00:00Z Content type: article Language: en Sources: [Mutt0-ds Notes]() Topics: [Tailwind CSS](), [CSS Framework](), [Angular](), [Front end](), [dataset](), [Command-line interface](), [CSV](), [dashboards](), [Notion](), [TypeScript]() Tags: [angular](), [cli](), [css](), [csv](), [dashboard](), [frontend](), [library](), [notion](), [tailwind]() ### AI overview A personal developer post describes building a book-reading dashboard with Tailwind CSS, Angular, a Notion-exported dataset, and a small tilting-effect library. It discusses the project structure, data preparation, and the author's experience using Tailwind's utility-class approach. ### Source excerpt I'm back with another post, this time exploring a new CSS framework, Tailwind CSS! In the previous months I started using Angular and...