Notion Wiki Feature Review: Testing and Summary

A quick summary of Notion's new Wiki feature — here are my hands-on findings and takeaways after testing it out.

---

April 24 Update

1. Wiki is a fusion of Page and Database. In the Home view, it offers the layout flexibility of a Page; in other views, it provides the structured organization of a Database.

2. Wiki fields are positioned differently, and two new field properties have been added — namely Verification, which only the Owner can edit. Verification helps us confirm the timeliness of page information or set up periodic page update reminders. For example, in work (collaboration) scenarios with documents like:

• Customer information, partner details, sales data reports
• Competitive analysis, industry reports, key business reports
• Workflows, execution standards, training materials

3. A dedicated search box has been added in the upper right corner, with the filter automatically scoped to the current Wiki, making information search faster and more precise.

4. Wiki limitations:

• Views other than Home cannot display page hierarchy in Sub-items format
• Creating Sub-items in any view other than Home places the new page at the bottom of the Home view
• When sharing an individual page within a Wiki, public visitors cannot see the Verification field — only sharing the top-level Home view gives public visitors the full feature experience (unclear if this is a bug)

---

April 12 Update

1. The Wiki feature is ideal for scenarios where a single page contains multiple sub-pages
2. In the Home view, the page retains its column layout; in other views, all pages within it are consolidated into a Database, allowing you to manage them using Database tools
3. The All Page view can traverse all sub-pages within a Page
4. It gives every page within the parent the ability to be tagged with Property labels, then uses Database features to manage and categorize these Property tags — enabling the creation of different themed collections
5. Previously, if you wanted to tag a Page with Last Edited time (or other properties), you had to create that page inside a Database. This caused two issues: the page's Breadcrumb would uniformly point to that Database, and the top of the page would show row after row of Database Property fields, which looked cluttered. Now this problem can be avoided
6. The Verification property provides periodic page review reminders — previously this required @Remind or a Database-based reminder setup
7. The Owner property serves to mark page ownership in team collaboration scenarios