Merge pull request #2 from jonathan2384/1
Adding a section for helping Notion users switch to and understand Anytype
BIN
.gitbook/assets/anytypeaddingblocks.mp4
Normal file
BIN
.gitbook/assets/anytypeblocks.png
Normal file
After Width: | Height: | Size: 96 KiB |
BIN
.gitbook/assets/anytyperelations.png
Normal file
After Width: | Height: | Size: 410 KiB |
BIN
.gitbook/assets/basicstep1.png
Normal file
After Width: | Height: | Size: 148 KiB |
BIN
.gitbook/assets/basicstep2.png
Normal file
After Width: | Height: | Size: 198 KiB |
BIN
.gitbook/assets/basicstep3.png
Normal file
After Width: | Height: | Size: 287 KiB |
BIN
.gitbook/assets/blockoptions.png
Normal file
After Width: | Height: | Size: 61 KiB |
BIN
.gitbook/assets/movingblocks.mp4
Normal file
BIN
.gitbook/assets/notionblocks.png
Normal file
After Width: | Height: | Size: 69 KiB |
BIN
.gitbook/assets/notiondb.png
Normal file
After Width: | Height: | Size: 231 KiB |
BIN
.gitbook/assets/notionfs.mp4
Normal file
BIN
.gitbook/assets/notioninline.png
Normal file
After Width: | Height: | Size: 125 KiB |
BIN
.gitbook/assets/notionrelations.png
Normal file
After Width: | Height: | Size: 197 KiB |
BIN
.gitbook/assets/notionsharingpane.png
Normal file
After Width: | Height: | Size: 150 KiB |
BIN
.gitbook/assets/notionworkspaces.png
Normal file
After Width: | Height: | Size: 254 KiB |
BIN
.gitbook/assets/setdemo.png
Normal file
After Width: | Height: | Size: 2.4 MiB |
BIN
.gitbook/assets/slashmenu.png
Normal file
After Width: | Height: | Size: 684 KiB |
BIN
.gitbook/assets/threedotmenuobject.png
Normal file
After Width: | Height: | Size: 140 KiB |
|
@ -23,6 +23,11 @@
|
|||
* [Creating a Reading List](use-cases-and-tutorials/creating-a-reading-list.md)
|
||||
* [Creating a place for Studies](use-cases-and-tutorials/creating-a-place-for-studies.md)
|
||||
|
||||
## Migrating from other platforms
|
||||
- [From Notion](migrating/notion/start.md)
|
||||
- [Read this first! - Missing Features](migrating/notion/missingfeatures.md)
|
||||
- [Architecture and Fundamentals](migrating/notion/fundamentaldifferences.md)
|
||||
|
||||
## Features
|
||||
|
||||
* [Library](features/library.md)
|
||||
|
|
124
migrating/notion/fundamentaldifferences.md
Normal file
|
@ -0,0 +1,124 @@
|
|||
# Architecture and Fundamentals
|
||||
Are you now ready to move your workflow over to Anytype? Sounds great... but there are a few things that you'll need to understand first.
|
||||
|
||||
Notion and Anytype operate based on two different architectures. This might sound just a bit unnerving, but once you grasp it, you'll be able to use Anytype just like you use Notion right now in no time. Read on to find out more.
|
||||
|
||||
# The Page Canvas and Blocks
|
||||
If you've used Notion and its Pages and Blocks, you'll have no difficulty in understanding Anytype's equivalent, which is its Object Canvas and Blocks.
|
||||
Each object has a canvas, and blocks can be placed within it.
|
||||
## Create a Block
|
||||
Notion's command pallete works almost exactly like Anytype's. Use the forward slash `/` to open the command pallete. Type to search, use the arrow keys to navigate up and down, or scroll through the list with your mouse. Press Enter, or click on the block type that you want, in order to create the desired block. By default, when you start typing on an Anytype object canvas, the block type will be plain text.
|
||||
|
||||

|
||||
|
||||
*To see a list of all available blocks, please refer to the Documentation page.*
|
||||
Want to create a block between, below, or even above another block? With Notion, you'd have used the `+` button to only create a block below the current block.
|
||||

|
||||
|
||||
Anytype's system is more flexible. Hover over the block dragger (shaped like a pill with three dots inside it), and a `+` button will pop out to your left.
|
||||

|
||||
|
||||
Move your mouse over to the `+` button that just appeared, and you'll see a yellow line appear. This line indicates where your new block will be inserted. Click the `+` button, and a new block will be created where the line is located.
|
||||
|
||||
[Screen Recording 2021-11-14 at 10.20.41 AM.mov](<../../.gitbook/assets/anytypeaddingblocks.mp4>)
|
||||
|
||||
With this, you can create a block below or between preexisting blocks, but unlike Notion, you can also create a block above another block.
|
||||
|
||||
To see options available for a block, such as deletion and duplication, click on the block dragger.
|
||||

|
||||
|
||||
## Moving Blocks
|
||||
Blocks can be moved around freely around a Notion page. Similarly, blocks can also be moved freely around an Anytype page. They can go below, above, inside or even next to other blocks!
|
||||
|
||||
To move blocks around an Anytype page, use the three-dotted dragger that appears once you hover over a block to click, then drag the block around a page - just like how'd you use the dragger in Notion. You can also select or command-click to manipulate multiple objects at once!
|
||||
|
||||
[Moving blocks around an Anytype page](<../../.gitbook/assets/movingblocks.mp4>)
|
||||
|
||||
There are some differences, however. You can also indent blocks within other blocks by directly dragging a block over another block in Anytype.
|
||||
|
||||
# Hierarchy, Page Linking, and Backlinks
|
||||
|
||||
Notion's pages operate in a **hierarchical** manner, like your computer's file system.
|
||||
|
||||
In your computer's file browser, folders **store** other folders and files. You can create shortcuts (or symbolic links) to refer to these files outside of the hierarchy. If you delete a folder, all the folders and files contained within it will be deleted, and shortcuts to those files will be broken.
|
||||
|
||||
Similarly, in Notion, pages **store** other pages. You can also create backlinks to refer to pages outside of the hierarchy. Therefore, if you delete a page, all the pages contained within it will be deleted, along with backlinks referring to that page.
|
||||
|
||||
[Notion's hierarchical system](<../../.gitbook/assets/notionfs.mp4>)
|
||||
|
||||
Anytype operates in a fundamentally different manner. Rather than working like your computer's file system, it operates like the World Wide Web.
|
||||
|
||||
Any website from the World Wide Web can **link** to another website. Every link is a shortcut, as links don't **store** other webpages; they just refer to them.
|
||||
|
||||
If you delete a webpage or a link, the webpages that it linked to won't be affected or deleted. Other shortcuts will continue to work.
|
||||
|
||||
Similarly, in Anytype, other objects (pages in Notion's lingo) can link to another object. This is how you organize other objects within your current object. If you delete links within an object or the object itself, the objects that it linked to won't be deleted, and other links to that object in other objects will continue to function.
|
||||
|
||||
> To see which objects your current object links to, click on the Navigation button. Alternatively, click on the Graph button to see a full-featured graph showing all the links between your objects.
|
||||
|
||||
That's also why backlinks in Notion are not a separate link type in Anytype - every link is a backlink.
|
||||
|
||||
Relations also link objects together with another. You'll learn more about this in later sections.
|
||||
|
||||
### **What does this mean for me?**
|
||||
Anytype's object linking architecture is more flexible than Notion's. You may be offput by the different architecture, but coming from a user who switched his entire workflow over from Notion to Anytype, you'll come to understand the benefits in no time.
|
||||
|
||||
Having objects (or pages, if that's what you prefer) not be locked inside a hierarchical silo, but instead linked together in a knowledge graph brings numerous advantages. You no longer need to think about \*where\* an object belongs in your tree or where to place it, you simply link it. This allows for a much more natural flow of information compared to storing data inside a hierarchical note system.
|
||||
|
||||
|
||||
If you want to read further about the advantages and disadvantages a non-hierarchical architecture brings to Anytype, I highly recommend reading this article: [https://www.nayuki.io/page/designing-better-file-organization-around-tags-not-hierarchies ](https://www.nayuki.io/page/designing-better-file-organization-around-tags-not-hierarchies)and https://www.nateliason.com/blog/roam
|
||||
|
||||
|
||||
# Databases
|
||||
Notion's relational databases are an incredibly flexible tool to help you categorize, organize, and **store** database entries - each of which is a fully-functioning page. Anytype works differently, yet, you can achieve the same (and more) with Anytype's Sets, Types and Relations.
|
||||
|
||||
## Sets and Relations
|
||||

|
||||
*Here's a Notion database. Each database entry is a page, and has predefined **properties, such as Tags, URL, and Phone**.*
|
||||
|
||||
Anytype's equivalent to Notion's databases are Sets. Unlike Notion databases, Sets do not **store** objects. Instead, they **show**, not store, all objects which meet a specific criteria, kind of how search works. Currently, sets can only show objects with one specific Type relation. Don't know what a Relation is? We'll cover it shortly.
|
||||
|
||||
This makes Anytype much more flexible than Notion. With Notion, if you wanted to create a database, you are stuck with it. You cannot move pages outside of the database, nor can you bring pages inside of a database once they have already been created (without annoying workarounds and time-wasting steps.) Instead, with Anytype, you can bring **any** existing object in view with a Set.
|
||||
Learn more about Types and Sets here->
|
||||
|
||||
*Here's an Anytype set. Right now, it's configured to show all Objects with the relation `To-Do.`*
|
||||

|
||||
<details> Having trouble understanding Anytype's databases? Click here to see a simplified explanation.
|
||||
|
||||
- Think of an individual Notion database within Anytype as a Type.
|
||||
- To create a "database" in Anytype, first, create a Type, then create a new Set to show all objects of that Type.
|
||||
|
||||
</details>
|
||||
|
||||
## Relations
|
||||
In Notion's databases, you may be familliar with properties, which are attributes connected to each database entry to describe it.
|
||||
|
||||
In Anytype, relations (Anytype's equivalent of properties) are not only applied to individual database entries, but applied to **every single object**. Relations describe each Object. Many Notion properties are also applicable to Anytype's relations, such as tags, URL, phone number, last modified by, descriptions, checkboxes, and much more. Find out more about Relations in the documentation page.
|
||||
|
||||
Relations can be defined for a Type. This is the equivalent as using the `+` button in a Notion database to create a new property.
|
||||

|
||||
|
||||
|
||||

|
||||
You can configure a Set to show relations (properties in Notion's lingo). Furthermore, you can create different Views (like Notion) that have different filtering and sorting settings, based on the Relations of the object.
|
||||
|
||||
Filtering, sorting and creating views in a Set work in a very similar manner to Notion, so you shouldn't have much trouble getting things sorted out. Check out the documentation on Sets for more information.
|
||||
|
||||
<details> Having trouble understanding Relations in contrast to Notion's Databases? Click here for a simplified explanation.
|
||||
|
||||
- Consider Anytype's Relations to be Attributes within a Notion database.
|
||||
- When you add an attribute to a Notion database, you use the `+` button to the right of the column header.
|
||||

|
||||
- Instead, in Anytype, to add an attribute to a database, open the Library (square menu on the home screen) and click on the "Types" tab. Open the desired Type and add attributes - known as relations in Anytype's lingo.
|
||||

|
||||
- Click "Create", then select Set of object to create a database view.
|
||||
- Click the Options button to add the Relations (Attributes) to the database view.
|
||||

|
||||
|
||||
</details>
|
||||
|
||||
### What does this mean for me?
|
||||
Anytype's equivalent of Notion's databases may not seem quite as straightforward, but, once you understand exactly how they work, they may end up being a more powerful and flexible tool than Notion's databases.
|
||||
|
||||
# Templates
|
||||
In progress...
|
44
migrating/notion/missingfeatures.md
Normal file
|
@ -0,0 +1,44 @@
|
|||
# Missing Features
|
||||
|
||||
Anytype is currently in the alpha stage of development, while Notion is in production. Most of the important core functionality that you'll have used in Notion is in place within Anytype, but there are important features that are missing and currently in development.
|
||||
|
||||
Read on to find out which core features Anytype does not have in this stage of development compared to Notion. **You'll want to carefully review and understand this information before fully committing to switching your workflow over from Notion to Anytype**. Please note that only **major, core features** will be mentioned in this document.
|
||||
|
||||
Take a look at our [Community Forums](http://community.anytype.io) to check out our most voted for feature requests, and maybe even vote and submit requests yourself! We can't wait to hear your feedback and input that you have for Anytype.
|
||||
|
||||
---
|
||||
## Sharing, Publishing and Collaboration
|
||||
**Notion** allows users to share pages and workspaces with other Notion users. Alternatively, users can create a sharing link to allow users without a Notion account to access your shared content.
|
||||
|
||||

|
||||
|
||||
**Anytype** currently does not have the ability to share content with other Anytype users or to the web. However, this feature is planned and is on the roadmap. If you find yourself needing to share content with other users, please use the "Print" option, accessed by using your system's Print keyboard shortcut, or through the three-dot menu within an object canvas.
|
||||
|
||||

|
||||
|
||||
|
||||
## Workspaces
|
||||
Within **Notion**, users can create multiple workspaces. Workspaces are self-contained and can be shared with other users. Workspaces are useful for separating different aspects of your life within Notion, such as work, personal activities, and school.
|
||||
|
||||

|
||||
|
||||
Anytype currently does not support workspaces. You'll have to store all of your objects within one single Anytype account at this moment.
|
||||
|
||||
## API and Integrations
|
||||
[Notion's API](https://developers.notion.com/) allows developers and users to create integrations with Notion. Please note that Anytype does not currently have an API or plugins, but it is [on the roadmap](https://community.anytype.io/c/feature-requests/developers-plugins-open-source/12). Please look forward for its release!
|
||||
|
||||
## Inline databases (sets)
|
||||
With **Notion's** inline databases, you can embed a database within an already-existing page.
|
||||

|
||||
**Anytype** currently does not feature inline sets (or databases in Notion jargon). It's on the roadmap, and will be released with later versions of Anytype.
|
||||
|
||||
## More: Advanced Features
|
||||
Here's a list of advanced Notion features which are not currently available in Anytype.
|
||||
- Synced Blocks
|
||||
- Tree Navigation (Coming Soon)
|
||||
- Sidebar
|
||||
- Notifications
|
||||
|
||||
|
||||
## What does this mean for me?
|
||||
In its current state, Anytype is a powerful and freedom-respecting software, with many core features that Notion users may be familliar with. However, Anytype and Notion are two entirely different products in two different stages of development, so feature differences are to be expected. As more time and resources are placed in Anytype's development, you'll find many more features make the jump over to Anytype.
|
9
migrating/notion/start.md
Normal file
|
@ -0,0 +1,9 @@
|
|||
# Coming from Notion? Read this!
|
||||
Welcome! Are you coming to Anytype from Notion? Don't worry - many aspects of your workflow in Notion can be transferred to Anytype, and a large portion of our users already have done so.
|
||||
|
||||
Read on to learn about the differences between Anytype and Notion's architecture, and how to adapt to these differences so you can build out your workflow in Anytype. We're looking forward for you to start experimenting with Anytype!
|
||||
|
||||
|
||||
[Before you migrate: Missing Features](../../migrating/notion/missingfeatures.md)
|
||||
|
||||
[Architecture and Fundamentals](../../migrating/notion/missingfeatures.md)
|