I am currently reading the GTD book whenever I got time and head space to read a non-fictional book. It is so insightful and he has so many incredible tips like the 2-minute rule and such to really get things going.
One way to make your pages a bit more mobile friendly is at the top of every page do a regular toggle, I call mine “Quick Links”. Open the toggle and type /toc for table of contents, then you get a nice list of all your headings on each page and you just have to tap the header instead of scrolling all the way down. I also try to keep the content for each page in Notion just long enough to fit my screen so I don’t have to scroll on my computer. You can zoom out to get more content on the page as long as your eyes can tolerate it. I keep mine on 75%-80% typically and I’m old. 😉
For a long time I struggle to see the difference between "one catch all database" vs multiple databases. I started with one database and multiple views. I'm sure certain cases require multiple databases. Can you explain the benefits and drawbacks of these approaches?
How you started (using one database that you filter to see different views) is definitely the preferred way as it helps keep things tidy when you start adding Relations and Rollups to your databases. If you have too many databases that require the same Relation, then you just create excess work to make sure everything is connected in both places. The only time I would consider two databases for a high-level grouping of items is if you were working with two different brands or created a TON of properties that weren't necessarily relevant to some of the information you keep in that database. For example, I created a separate content database for my travel brand rather than use the same content database as my personal brand due to team members who only need access to ONE of those databases. Plus, there were many properties that only applied to one brand and not the other. I don't like when databases have 30-40 properties to fit every single scenario because that's a lot to sort through. I also created two "People" databases in my Christmas Planner. The Recipient database and an All Contacts database. It would make more sense to have them all in one, but in the case of Recipients, you generally buy individual gifts for everyone so you create one person per database page. But with All Contacts, I was primarily using them to know how many guests you would invite to a holiday party or dinner or to send Christmas cards. I wanted users to add one family per page, which wouldn't be helpful in keeping track of budgets and gifts for each individual in the family. I hope that makes some sense! It's so hard to respond on UA-cam where you can't share any screenshots or other visuals.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
you explain things so clearly and simply especially for beginners like myself new to notion but loving it so far
I'm so glad you're able to find my videos helpful! Thanks for being here. :)
I am currently reading the GTD book whenever I got time and head space to read a non-fictional book. It is so insightful and he has so many incredible tips like the 2-minute rule and such to really get things going.
Notions’s mobile app could use some attention for sure!
Definitely!
Thank you so much for explaining everything in layman's term!! You rock!
I'm so glad it was helpful!
You explain things so good! Really looking forward to future content!
I appreciate your kind words and I'm glad you'll be sticking around! We have some great, new things coming up!
I just became a fan of your content
Glad to have you here!
Notion anatomy class is fantastic!
Thank you so much!
One way to make your pages a bit more mobile friendly is at the top of every page do a regular toggle, I call mine “Quick Links”. Open the toggle and type /toc for table of contents, then you get a nice list of all your headings on each page and you just have to tap the header instead of scrolling all the way down.
I also try to keep the content for each page in Notion just long enough to fit my screen so I don’t have to scroll on my computer. You can zoom out to get more content on the page as long as your eyes can tolerate it. I keep mine on 75%-80% typically and I’m old. 😉
Both of those are great tips-I'll have to implement those on my most referenced pages! Thanks for watching (and sharing!)
Perfect! This is just what I needed... Thanks!
So glad to hear it!
Great job! Thank you very much, your videos help me a lot.
I'm so glad to hear it! Thank you for being here. :)
Very helpful video!
Glad it was helpful! 👏
Thanks it was helpfull
Glad to hear that!
Thank you this was super helpful. However when I go to add the widget my only choice is my work space. No page option. Has anyone else had this issue?
Hmmm, I'm not sure about that. Maybe this page will help? www.notion.com/help/mobile-widgets
For a long time I struggle to see the difference between "one catch all database" vs multiple databases. I started with one database and multiple views. I'm sure certain cases require multiple databases. Can you explain the benefits and drawbacks of these approaches?
How you started (using one database that you filter to see different views) is definitely the preferred way as it helps keep things tidy when you start adding Relations and Rollups to your databases. If you have too many databases that require the same Relation, then you just create excess work to make sure everything is connected in both places.
The only time I would consider two databases for a high-level grouping of items is if you were working with two different brands or created a TON of properties that weren't necessarily relevant to some of the information you keep in that database.
For example, I created a separate content database for my travel brand rather than use the same content database as my personal brand due to team members who only need access to ONE of those databases. Plus, there were many properties that only applied to one brand and not the other. I don't like when databases have 30-40 properties to fit every single scenario because that's a lot to sort through.
I also created two "People" databases in my Christmas Planner. The Recipient database and an All Contacts database. It would make more sense to have them all in one, but in the case of Recipients, you generally buy individual gifts for everyone so you create one person per database page. But with All Contacts, I was primarily using them to know how many guests you would invite to a holiday party or dinner or to send Christmas cards. I wanted users to add one family per page, which wouldn't be helpful in keeping track of budgets and gifts for each individual in the family.
I hope that makes some sense! It's so hard to respond on UA-cam where you can't share any screenshots or other visuals.