The Wiki In Notion: My Thoughts
Pros and Cons
As I edit my new YouTube series on how to make a Wiki from scratch, I’ve accumulated a pros and cons list for using the program to store and display a large number of database entries. My family wiki has over 1000 entries of which I’ve been adding to for over a year. It took some serious finessing to get the final product I can live with in Notion. Which leads me to the first negative:
Negative: System Building
How can system building be a negative for a system? Simple. If you’re not already knowledgeable with systems, it’s going to take a lot of trial and error to achieve your vision. This is, of course, time consuming.
Positive: Relation Building
The ability to relate items in multiple databases in a multitude of ways is a huge benefit. I can pick and choose how and in what directions my data goes. In addition, I can describe those relationships with ease. The benefits of a clean UI and straightforward database structure!
Negative: In-line Search
Okay, don’t rely on this one too heavily. If you want to connect your pages, use the database framework. I know, it’s annoying. I’ll be the first to tell you but Notion’s in-line search, albeit snappier than in the past, is still not up to par for larger projects. It is still quite laggy. As well, the back linking for in-line links are very minimal and will not show page context.
Positive: Ease of Import
When a system in Notion is built right, the ease of use skyrockets. If you’re doing a lot of research that needs a steady flow of data to multiple databases, the linked database and smart filters Notion provides will get the job done in one page. Very convenient!
Speaking of smart filters, Notion allows the user to use something called referential linked databases. What this function does is call any connected databases into the body of a Notion page via a database template. Again, convenient for importing AND for visualizing relationships. In addition, the impressive filters and grouping options on their own are extremely useful for breaking down big data into small chunks; something I recommend doing.
Positive: Rollups, Rollups, Rollups
In a large wiki of information, you’ll want to of course, analyze the data. For example, in my family tree wiki, in the members database, there is a formula to calculate the approximate age the member died. Let’s say this person’s name is John Smith. Inside the Smith family page this member is connected to, I am able to calculate the the average age of death for all Smith family members using a rollup property.
What I Published
New series soon all about how to create a complex wiki from scratch, then back to the normal schedule. See you then!
Great work, I am impress with the diagram, what tool did you use for the diagram?