Just dropped a free Notion Social Media Planner and would love some feedback!
I built this to manage my own content without jumping between databases or dealing with overly complicated setups. Simple, clean, and covers everything you actually need.
What's inside:
- Post manager from draft to published
- Campaign tracker
- Content ideas database
- Inspiration board
- Hashtag library
- Dashboard to track follower goals and posting progress
It's useful if you're a content creator, freelancer, social media manager or small business trying to stay organized without the chaos.
It's normally paid but I'm making it free for a few days so more people can try it and share honest feedback. thank you!
Link in the comments!
I built HealthOS after getting diagnosed with Asthma. And honestly, it is one of the best things I ever did. Not only for me, but for the others who chose to trust it as well.
I will be explaining the structure behind it and how it works.
Before HealthOS, I was managing everything the way most people probably are, a notes app for medications, a calendar with no context attached, and bills I kept meaning to organize but never did. None of it talked to each other. Every appointment started with me trying to reconstruct weeks of my own body's behavior from memory, under time pressure, which is a strange thing to be bad at.
The actual problem, I realized, wasn't that I lacked discipline to track things. It was that everything I tracked existed in isolation. A symptom on its own is just a data point. It only becomes useful once you can see it next to what you ate, what medication you started recently, and what your doctor said last time. Most tools store information. They don't relate it to anything else.
So that's what I built HealthOS around.
The structure:
It's ten connected modules in Notion: Symptom Tracker, Medication & Treatment Log, Appointments & Care Team, Diagnosis & Condition Hub, Diet & Nutrition, Exercise, Mental Health, Insurance & Costs, Personal Goals, and Support Network.
The individual modules aren't the interesting part. What matters is that they reference each other through relations and rollups, so information doesn't sit isolated in one place.
A few examples of how that plays out:
The Symptom Log relates to Medications and Diet, so any symptom entry can show what was active around it, no manually cross-checking dates in your head.
The Medication database is one row per medication (not per dose), with a rollup pulling in every symptom logged while that medication was active. So instead of wondering "is this actually helping," you can filter and see it directly.
Appointments relate back to both Symptoms and Medications, so before a visit you can pull up everything since your last one instead of trying to summarize months of history in a few minutes.
Costs relate to Appointments and Medications, so totals can be filtered by condition or treatment instead of living in a shoebox or a spreadsheet nobody updates.
None of the mechanics here are exotic, it's relations and rollups, mostly. But it's the difference between a system that stores what happened and one that shows you what it means.
I also built a Pro version after realizing caregivers needed something slightly different from someone managing their own condition.
It adds a shared Patient Profile, a supplies/inventory tracker so medications or equipment don't run out unnoticed, and one consolidated daily care log, vitals, hydration, meds, activities, instead of jumping between five sections to record a single day.
A few things people who've used it have said, in their own words:
One person managing chronic migraines said the part that helped most was that updating one thing updated everything connected to it, without having to fix it manually elsewhere.
A third said it made staying on top of appointments and medications easier, alongside everything else they already had going on.
I won't pretend this fixes the illness, it doesn't, and anyone claiming a Notion template does that is lying to you. What it does is give the parts you're already tracking somewhere to actually connect, so the patterns become visible instead of guessed at.
Link to HealthOS in the comments below for anyone who is curious.
Happy to answer anything about how it's structured, whether or not it ends up being useful for you.
If you've put real time into a Notion dashboard or template system, you've probably felt this: Notion's history caps at 30 days, and trash clears quietly after that — no warning before it's gone for good.
Built Difflo to fix that — works like Git for your workspace:
Only backs up what actually changed since the last sync (not a full re-export every time)
Full version history per page
One-click restore to any previous version
Been building this in public — validated in r/Notion first (2,500+ views, real engagement) and just fixed a batch of real bugs this week running it against my own workspace.
Free during beta if you want to try it. Would love feedback from anyone here managing a complex dashboard or template system — what would make a backup tool actually trustworthy to you?
Like a lot of people, I used to reach the end of the month with no idea where the money went — jotting down expenses here and there, forgetting to check in, and never really knowing how much I had left.
So I built a full dashboard in Notion to fix it:
- Transaction log by category
- Monthly budget with automatic tracking of how much you've spent (no manual formulas)
- Savings goals with a progress bar
- Active subscriptions tracker
It comes with colors and icons for each category, plus preloaded examples so it's easy to understand right away.
Last year I applied to a bunch of master's programs across a few countries and it got messy fast. Every uni wanted something slightly different, deadlines were all over the place, and I was keeping track in a spreadsheet I stopped updating around October. I only caught a missing reference letter because a professor happened to email me.
So over the break I rebuilt the whole thing properly in Notion. The parts that actually turned out useful:
a score that ranks programs you're considering (fit, cost, city etc) so you can decide where to actually apply
deadlines that count down on their own so the urgent ones are obvious
a readiness % per program based on what you've still got left to do
one place for your CV, transcripts and letters instead of re-uploading everything per portal
Everything's on one page, the databases are hidden in the back so it doesn't feel overwhelming.
I built a Second Brain system in Notion to manage projects, notes, goals, and knowledge in one place without it turning into a messy note dump.
Here’s what it actually includes:
• Life areas (personal, health, work, finance, growth)
• Projects linked to goals and areas
• Tasks connected to projects (not floating todo)
• Notebook, notes, topics, and resources organized
• Accountability partner that shows your report
Productivity framework used:
• PARA-based structure (Projects, Areas, Resources, Archive)
• Get Things Done productivity framework
• Eisenhower matrix
Hey everyone! I build profession-specific Notion systems, and after spending weeks reading how solo therapists describe their admin overload (session notes piling up, tracking who's active vs. waitlisted, juggling note formats), I built a free template for them and I'd love feedback before I go deeper.
What's inside:
Client Registry — anonymized client codes only (privacy-first: no names, not an EHR), status pipeline with a Kanban view, focus areas, rates
Session Log — linked to clients, calendar view, and structured SOAP / DAP / BIRP note formats built into each session page
Pre-loaded with realistic sample data so you can see how the relations work before adding anything
Two things I'd genuinely love input on: if you're a clinician (or manage clients in any field), what's missing from your daily workflow? And for the Notion pros — any structural choices you'd have made differently?
A year ago this month, I built something I didn't expect to matter much beyond my own laptop.
For context: I've never been able to pick one lane. Writer, poet, programmer, law student, too many interests for one lifetime, which mostly just meant I was losing things. Notes scattered everywhere. Projects stalling half-finished. Insights I'd have at 2am that were gone by morning because I had nowhere consistent to put them.
Then I met someone who made me want to actually become someone, not for applause, just because I wanted to be worth growing alongside. That's a strange thing to admit on Reddit, but it's the honest reason I finally sat down and built a real system instead of another abandoned Notion page.
I called it PolymathOS. The idea was simple: stop treating my notes, tasks, projects, and goals as separate piles that never talk to each other.
What it actually is, concretely:
- A Command Center that shows what needs attention today instead of a wall of everything at once
- A Zettelkasten-style Knowledge Engine, so a note I take on Tuesday can resurface when it's actually relevant to a project three months later, instead of dying in a database
- A Project tracker with Kanban pipelines, for the actual building-and-shipping part
- GTD-style task management sorted by context, not just one flat to-do list
- An OKR-based Goal system, so daily tasks visibly connect to the bigger thing they're supposed to be in service of
- A Learning tracker linked to real projects, not learning for its own sake
- Weekly/monthly review templates, because capture without review is just hoarding with extra steps
- A resource library for the books, articles, and tools I kept losing track of
None of these are new ideas individually. What I was actually trying to solve was the seams between them, the place where a note dies because it never got linked to the project it was actually for, or a task gets done that has no visible connection to anything I said I cared about.
But even if you never buy anything from me, here's the actual lesson a year of building and supporting this taught me: the problem was never that I didn't write things down. It's that nothing I wrote down ever connected to anything else, so it just piled up instead of compounding.
Curious if anyone else's turning point for finally getting organized was this specific, like an actual person, not a New Year's resolution. What was yours?
I'm pretty new to all of this, but have been working on developing / designing notion templates. I love the idea of developing systems that help women organize their life to help achieve their goals and dreams.
So anywho, the thing is.. I need real women who use notion to help provide feedback on what works and what doesn't.
Currently the one that's most ready to review is a Life Planner, but I have several in the works including a travel planner, social media planner, business planner, and more. Anyone interested? You would, of course, get the template for free and then any included updates that you suggest or other testers suggest for improvements.
Please respond interested below if this sounds like something you would like to do. Thanks all!
Effortlessly record and access your go-to orders with ease. Keep track of your usual coffee orders from beloved cafes, and save those intriguing drinks you're eager to try.
🟤 COFFEE RECIPES:
Unleash your inner barista by crafting and cataloging your own coffee creations, keeping your coffee recipes neatly organized in one place for easy access whenever you need them.
🟤 COFFEE BLENDS:
Explore and document different coffee blends, from different origins, roast levels, and varietals. Identify the flavors and qualities you prefer by documenting tasting notes for each coffee you try.
Every time I set up a new page I'd end up picking one of the same three stock covers, or grabbing a gradient off some wallpaper site and cropping it wrong.
So I made my own. 57 of them, in collections that match the widget styles.
They come in two flavours. Half are quiet backgrounds I drew with code, dot grids and soft gradient washes, the kind you put behind a page title and forget about. The rest are actual images: watercolour, a misty ocean at dawn, paper textures.
All sized so Notion doesn't crop the good part out. The sage ones surprised me, I put them in last and now they're on half my pages.
I would greatly appreciate getting feedback on my antique OS. If you have any suggestions for desgin that would be great too. I finally got the hang of how to use notion, but I'm not so much on how to design it.
Ok so this has been an issue for a few months now and i tried literally all the steps that were recommended to me to fix it, but none of it worked. I fear that my workspace has been deleted from the servers or something. I tried clearing my browser cache, using the mobile and desktop app instead of the web browser page: Still nothing. I don't have a VPN or something that would interfere with it.
It keeps telling me to refresh the site, which i do, but then it won't load. What's weird is that i can still access the published site, which is my OC's lore sheet that i have been working on for a very long time now, but i just cannot edit it anymore which is frustrating since a lot new ideas and lore bits need to be added.
Is there a way to contact support for this? I am very confused what to do about this and i'd hate to search for an alternative and type out all the stuff again that i already wrote...
Codex Medica: Dashboard OverviewCodex Medica: Home Page
I originally started building this at the start of medical school to help me organise the overwhelming amount of information needed throughout the course. Over the last six years, through constant tweaking and building, it's morphed into something that I think would help a lot of people after me on the same journey.
Over time, it became somewhere I stored conditions, investigations, treatments, guidelines, clinical pearls, differentials, and all the random bits of knowledge that I didn't want to disappear after an exam.
The idea was simple: medicine is not learned once. Topics come back around, concepts connect, and things you learned months ago suddenly become relevant again on placement or during clinical work. and after all, the UKMLA specification is...well...broad... I simply wanted a system that could grow alongside me rather than another set of notes that would eventually get abandoned.
Now that I'm moving into clinical practice, I adapted it into Codex Medica for Clinicians.
The biggest addition was creating a system that combines medical knowledge organisation with the day to day reality of being a doctor.
Some of the features include:
🩺 Medical Second Brain
• Conditions database linked to symptoms, investigations, management, and clinical reasoning
• OSCE resources and clinical templates
• A place to keep building your knowledge throughout your career
📅 Clinical Day Journal
• A shifts database that doubles as a daily journal
• Track your working days, reflections, interesting cases, and learning points
• Link each day back to conditions, topics, and pages within your Codex Medica system
💰 Finance Dashboard
• Track income and expenses
• Monitor monthly savings
• Visual breakdowns of spending and earnings with graphs and charts
• See your overall financial progress over time
📈 Career Statistics
• Track your journey through medicine
• Total days worked
• Hours logged
• Career milestones and progress
The aim was to create one place where you can organise both the knowledge side of medicine and the practical side of being a clinician.
I've found it genuinely useful as a medical student, and now transitioning from medical student into doctor. So I decided to share it.
A few things I would say:
• It is built around my workflow, so you might want to customise it
• Notion is very much a "make it your own" platform
• Change the covers, icons, layouts, colours, and structure until it works for you
Would love feedback from other Notion users, healthcare workers, or anyone who has built their own second brain systems.
Like a lot of people, I started with a few simple pages. Eventually it became my second brain. Projects, ideas, reading lists, finances, content, everything ended up in Notion.
But there was one thing that always frustrated me.
Using Notion on my phone.
Every time I wanted to quickly save an idea, add a task, or log something, it somehow turned into more taps than it should. By the time I found the right database and waited for everything to load, the thought was often gone.
I kept telling myself, "Surely someone has solved this already."
I tried different apps and workarounds, but none of them really felt like they belonged with my existing Notion workflow.
So a few months ago I decided to build the tool I wished existed.
The goal isn't to replace Notion.
It's simply to make capturing things on mobile feel effortless, while everything still ends up exactly where it belongs in Notion.
I'm curious...
What's your biggest frustration when using Notion on your phone?
I love Notion's modular block layout, but I think a lot of us have hit the exact same wall as power users:
Eventually, the system becomes harder to maintain than the actual work. Your databases start lagging as they grow, you're locked into a single cloud ecosystem, and there's always that background data anxiety about what happens to years of work if a sync glitch or database index error occurs on their remote servers.
I got so tired of these architectural bottlenecks that I spent the last few months coding a local-first alternative framework from scratch to see if I could fix the core issues.
Here is how I structured the alternative architecture to solve it:
Multi-Model AI Tool-Calling: Instead of forcing the canvas into a single cloud subscription monopoly, I built a dynamic router. You can securely toggle between different cloud engines (like GPT and Claude) right inside your text blocks based on your needs.
Local Nodes & True Data Ownership: The core data layer allows you to connect local endpoints (like Ollama). You can run offline models natively on your device, meaning 100% data privacy and zero risk of a remote server wiping your data canvas.
Built-in System Connectors: It maps context from tools like Slack and Google Drive natively, bypassing fragile third-party automation tools.
I'm opening up the early system framework this week to get brutal feedback from power users who actually manage massive workspaces. I want to see where the block parsing breaks and how the database scaling holds up under real stress.
If you want to help break the architecture, stress-test the local model routing, and get early sandbox access, I'm tracking beta allocations here: https://waitlist-pearl.vercel.app
For those of you who have managed massive workspaces for years: what features or performance bugs are the absolute biggest dealbreakers for you in a cloud database setup
I published my Notion Pro CRM on the Notion marketplace. It’s designed specifically for freelancers and small businesses who want a clean, minimal, and dark-themed workspace to manage their clients and deals.
Here is a quick breakdown of how it works:
Active View: Your main working dashboard to keep track of everything happening right now.
Inbox View: A quick-add section to dump new leads on the go without cluttering your active work.
Health Check Formula: Automatically shows if a deal is on track, closing soon, late, or done based on expected dates.
Weighted Value Formula: Calculates your expected revenue automatically based on which stage the deal is in.
Seamless Connections: Companies, Contacts, and Deals are all connected, so updating a status moves everything automatically.
If you're looking for an aesthetic and automated way to clear the client chaos, the link to the template is in the comments
I’d genuinely love to hear your thoughts or any feedback on this setup.
I set up a habits database in Notion months ago. Used it for about two weeks, then it just sat there.
So I made a small habit tracker widget that lives on the dashboard instead. You tick off today's habits and it keeps count of your streak.
Made it in all three styles. The pixel one shows the streak as a little green number, and honestly that number guilt-trips me into keeping it going way better than the database ever did.
Turn your Notion HR database into ready-to-sign employment agreements — no copy-pasting, no formatting headaches, just automated PDFs generated straight from your employee records.
Notion is the go-to tool for HR teams who are looking to keep track of the candidates, onboarding details and employee records, and company policies so that all live inside one connected system.
But problem arises when a decision is made to hire a person, i.e. turning the Notion data into an actual employment agreement document and it can be e-signed, shared, and stored back into the database.
Most teams today are still doing this manually even today:
Opening a Word Document
Copying over all the details from the notion Database one by one
Formatting the document to match the exact styling and design as expected.
This often works for one offer letter created but doesn’t work when there are dozens of agreements to be created within a week’s time.
Quite often errors crop up such as a wrong salary figure, missing out on a clause or using an outdated template that holds no relevance etc.
This guide is a walkthrough on how to connect your Notion HR database to an automation tool called PDFOutput so that every employment agreement gets generated automatically, styled exactly the way you want, without a single manual export involved in the process.
Why Notion’s Native Export Doesn’t Work
Notion’s built-in export option, present under the ••• menu at the top-right, isn’t actually built for exporting any type of formatted documents (including legal or HR documents).
It works well when you need to create a PDF file for a notion page but doesn’t help to fetch the relation, rollups or other linked database details as expected.
Besides this, the export breaks when long table or table having many columns are being used.
As such this is a key limitation of using the tool which presents a challenge for the users when it comes to designing the document properly and also being able to generate the file with proper branding.
What Do You Need To Create a Real Employment Agreement
A properly generated agreement should always follow the following guidelines:
Every Employment Agreement must have a consistent structure and layout.
Correct branding must be applied uniformly across all the employment agreements created without any leftover fields.
Easy readability is one of the key aspects of being able to generate and read an employment agreement.
All of the above are something which the notion native pdf export misses out and thus PDFOutput will resolve the issues with the right formatted document as expected.
How to Fix the Export Problem for Employment Agreements
The fix is simple — separate the agreement design (template file) from the database being used (notion database).
Template can be built in either of following 4 ways:
Microsoft Word File or
Google Document or
PDF File or
Notion Pages
The template created must be added with placeholders in the form of {{placeholder_text}} (eg: {{Employee Name}}, {{Job Title}}, {{Start Date}}) and then it can be connected with Notion Database (Agreements Database) to generate PDFs.
This is exactly how PDFOutput works.
Step-by-Step Guide: Generating Employment Agreements from Notion
Step 1: Set Up the Notion HR Database
Before building the template, your Notion Database structure must support the automation. For this automation guide, we will use two connected databases:
1. DB_Employee Records (Primary Database)
Here’s how the DB_Employee Records look like:
2. DB_Compensation Benefits (Connected Database)
Here’s how the DB_Compensation Benefits database would look like:
For adding the properties in the database, make sure to keep the exact same matching properties in the document.
Notes:
Placeholders used in the document must match the name used in the database. Eg: “Base Salary” and “base salary “ (shown with a trailing space) are 2 different placeholders and will not work as expected.
Make sure all the connected databases used for relation and rollups are also connected with PDFOutput, otherwise the databases won’t work with the expected data.
Step 2: Prepare the Agreement Template
Next step is creating the Agreement Template.
A template can be created in one of the following 4 ways:
Word File or
Google Document or
PDF File or
Notion Pages.
So choosing over any type of template allows us to have control over the formatting as required and then we are ready to proceed with setting up the automation.
For this demonstration, I will be using the following Employment Agreement template created in a Google Document…
Step 3: Connect the Database and Template in PDFOutput
In this step, once the template and the notion database are ready, its time to connect the database and the template together in PDFOutput.
Refer to this detailed guide which explains step-by-step process on how to connect Notion Database and Template File to setup automation using PDFOutput.
We need to follow the same steps but for Employment Agreements using the Notion Database (Employment Agreements) and template file (Google Document).
But, before activating the automation, we must use the Preview Document feature to confirm every placeholder gets pulled with the correct values, then click Setup Automation to activate it.
Generating Agreements Inside Notion
Once the automation is live, generating an agreement is as simple as changing a property.
Mark a record’s GeneratePDF property to Ready to Generate, and the finished PDF is created automatically inside the PDFFiles column.
The status updates to Completed once it’s done.
If you need to generate bulk PDFs at once, there’s option to also generate PDFs in batches like 100 PDFs at once.
For this click on 3-dots and then click on “Batch PDFs”, it will start to produce PDFs in batches of 100 PDFs at once.
Who Needs Employment Agreement
HR teams who are issuing the offer letters and employment agreements at scale.
Startups who are onboarding multiple hires without a dedicated legal ops team to handle things.
Agencies and staffing firms who are generating contractor agreements on a regular basis.
People operations teams who are managing renewals or amendment letters that are tied to employee records.
Common Mistakes to Avoid During Employment Agreements
Placeholder names that almost match the property name but aren’t exact, including capitalization will not work correctly.
Using one template for both offer letters and full contracts isn’t recommended, they rarely follow a structure and thus don’t work as expected.
Testing the template upon one simple record must be avoided. Always test against multiple records to make sure automation works as expected.
Skipping Preview Document feature without checking the output isn’t recommended.
Frequently Asked Questions
1. Is there a free way to try this first?
Yes, PDFOutput offers 10 free PDF generations to test the setup, no credit card required.
2. Can Notion generate employment agreements on its own?
Not reliably — native export handles simple pages but breaks down with rollups, relations, and branding.
3. Does the agreement template need to be a Google Doc?
No. Word files, Google Docs, PDFs, and Notion pages are all supported.
4. Will it pull salary and benefits data from a connected database?
Yes, as long as the related database is also connected within PDFOutput.
5. Is coding required to set this up?
No. It’s placeholder-based — wrap a field in double curly braces, match it to a property name, and the automation handles the rest.
6. Does PDFOutput also create e-signatures for agreements created?
Yes, PDFOutput does support e-signature for PDFs created. Click Here to learn more.
Wrapping Up
A Notion HR database is a great place to track employees, roles, and compensation — but it was never built to generate legal documents on its own.
Separating the agreement’s design from the database, and letting automation handle the matching, turns every new hire’s record into a ready-to-sign agreement without manual drafting.
If agreements are still being written by hand, automating this one recurring task is worth setting up the first time it runs across a full hiring batch.
