Cute Poetry Journal Notion

Building a Poetry Journal in Notion

I've been messing around with Notion databases for about three years now. The original setup I had was just a simple text page for poems, but that got unwieldy fast when I started collecting more than fifty pieces. So I rebuilt it from scratch using linked databases and proper relations instead of tags. Here's how I actually did it. The core idea is separating your poems into their own database, then linking them to themes, moods, and publication status through relation properties. I learned this the hard way when I tried to use a single database with checkboxes for everything. You end up with this massive wall of data where every row is doing triple duty, and filtering becomes impossible after a while.

Setting Up Cute Poetry Journal Notion

Start by creating three separate databases. The first one is your poems database with properties like title, date written, draft status, and the actual poem text in a toggle or full paragraph block. The second database tracks themes or motifs across your work — words like grief, nature, memory, that kind of thing. The third handles publication tracking: where each poem has been submitted, rejection letters, acceptances, and any revision notes. Link them all together with relations. When you write a new poem, you tag it with relevant themes using a multi-select, then use the relation property to connect it to your themes database. This lets you see every poem you've written about, say, loss, without having to manually sort through hundreds of entries. The publication database works the same way — link each poem to its submission history, and you can see at a glance which venues are taking the longest to respond. I ran into a specific problem when I first set this up: Notion's relation property doesn't let you filter by multiple criteria across different databases in a single view. So if you wanted to see all poems about water written in 2023 that haven't been published anywhere, you can't just do that. What I ended up doing was creating a filtered view in the poems database with the theme as a relation, then using the date range as a native filter. It's clunky, but it works. You lose some granularity, but gaining the ability to search across decades of work outweighs it.

For the actual journal formatting, I use a gallery view for browsing poems visually, then switch to a board view grouped by draft status when I'm actively editing. The toggle blocks for the poem text itself keep everything clean — you click to expand, read, click to collapse. Takes up less screen real estate than full paragraphs, especially on smaller monitors. One thing nobody tells you about Notion databases is that the search function is basically useless once you hit a few hundred entries. I learned this when I tried to find a specific line from a poem I wrote in 2019. The search returned nothing relevant, so I ended up using the browser's find function on the page instead. If you're serious about this, consider exporting your database to CSV regularly as a backup, or at least keeping a separate local archive. The Cute Poetry Journal Notion setup I described here runs on the free tier, but you'll hit limitations quickly if you need advanced filtering or want to share it with other poets. Notion's sharing features are decent, but collaborative editing on databases gets messy fast when multiple people are adding entries. I ended up switching to a simpler shared spreadsheet for the submission tracking portion, then keeping the main journal in Notion for my personal work.

If you're just starting out, don't overcomplicate it. A single database with basic properties will get you through your first hundred poems. Add the linked databases later when you actually feel the pain of not having them. Trust me on that one — I wasted three weeks perfecting a system I didn't need yet.