ohhhhhhhh my lawd did you just say that we’ll be able to change all objects at the same time via type settings?!!!??
Christmas coming early!! 
Self-descriptive formats! I think this is a very good approach to counter the initial confusion when starting with Anytype. Coming from Notion and Coda, I experienced this myself in the beginning, it took me quite a while to understand the functions of the elements of Anytype ( i.e. what are collections, what are sets?).
The terms “Lists” and “Smart Lists” make it much easier to understand their function.
I wrote it already often in other threads, but I argue once more against the term “List”.
The team should name the thing “Listbox”.
“A Listbox shows a list.”
- That sentence makes sense.
But: “A List shows a list.”
- That sentence looks strange.
Also the side menu shows a list of entries.
Not to be confused with a List that also shows a list …
PLEASE dear team, use only unique names for Objects!
“Listbox” would be such a unique and also precise name.
It’s impossible to become confused with something else.
And once again I mention the problems to translate all the terms in other languages.
There wouldn’t be any need to translate a name like “Listbox”.
But for “List” the translators are forced to hallucinate a completely new name that would work in the other language.
“Ich habe eine List, die …”
– That simply doesn’t work in German. The thing needs a name that can not become confused with something else.
Personally, I like List. Simple, straightforward. I even think that “A List shows a list” is very logical. Listbox sounds long and convoluted to me. In French, a List is une Liste. Simple, clair.
It says what it does, it does what it says 
Just a personal opinion.
+1 for list here
“Ich habe eine List, die …”
– That simply doesn’t work in German. The thing needs a name that can not become confused with something else.
I am German but I would never think of the German word what you mean here when the rest of the application is in English.
In German it will be “Liste” of course. Your argument is very strange I have to say 
List"box" feels like a technical term and the word box doesn’t add anything to it what the thing in question actually does.
I agree with @JuanToronDoe here.
But the rest of the application is not in English after translating everything into German.
But the Object itself is not a “Liste” in German. The Object SHOWS a “Liste”, but it isn’t one.
It is a Listbox.
A milkbottle is not “milk”.
If we speak about the bottle, because we want to do something with it (put it in the dish washer for example) you wouldn’t say: “Put milk into the dish washer!”
You would clearly say: “Put the milkbottle into the dish washer”.
Oh, and by the way:
A dish washer is called a dish washer. It is not called a “dish”.
Yeah, it is a technical term, because the Object is a technical thing.
It shouldn’t be confused with its content or anything else.
Listbox is a similar term like Combobox - a standard GUI element in programming languages.
+1 for „List“ as well. Its just straight forward, even my wife (as non tech person) understands it very well.
A list is simply a list… nothing else. If you are speaking about the collection of lists then you can use the plural form of list which is “Lists”… who would have thought.
Unfortunately there’s no plural for milk (neither in English nor in German) that’s why you put it into a bottle. 
So this can’t be compared directly with “List” and “Lists”.
So let it be “List” or “Liste” in German for a simple List and all the Objects of Type “List” are called “Lists” (or “Listen” in German).
Love “lists”!
It might be a question of mother tongue. In French, it is very common to designate the content by the container (it’s a metonymy). We say literally “to drink a glass” in the sense of “to drink a glass of water”. So a List for “an object than contains a list” sounds normal.
Edit: same goes for cigars. I would say “give me the cigars”, meaning “give me the box of cigars”. Another metonymy.
What?
There is no “Collection of lists”.
What a Collection shows in its Grid is for me a list (of entries).
And if we now call a Collection “List” then it becomes weird in my perception.
Then does the “List” show a list in its Grid.
Then can the “List” either show a list (I mean in its Grid) or the other List (this time with a big first letter), or a Kanban, Calendar, Gallery, Graph.
The “List” then has a Gallery View as well as a List View. And shows a list (with little first letter) in its Grid … and everything is mixed up, especially if someone is new here and/or writes everything in lower case letters.
It’s no longer distinguishable what he means. That provokes misunderstandings as well as unneccessary question/answers.
OK, another example …
Replace the milk bottle with a cigar box and the milk with cigars.
If someone means the box, he wouldn’t say “cigars”.
Because he wants to do something with the the container, he isn’t interested in its normal content.
He has some screws and he wants to put them in the cigar box (the container). He would never call the thing “cigar” if he actually means the box.
ROTFL! And at the same time also 
Don’t you see the confusion yourself?
right, this is actually my point - when it’s called “Liste” in German, also the confusion doesn’t become reality (what you meant with the German word “List”) because it is properly translated.
Why can’t it becalled this way? If this object doesn’t do anything else than showing a list, it actually is the list itself.
Don’t we talk about collections and sets here? Those are Anytype’s inventions and are just tables of content, one is dynamic, the other static. There is no need to call it either Collection, Set or List"box". It is just a list, a statuc or a dynamic one.
When I go to my mom and tell her about Listboxes, Comboboxes or input[type=“checkbox”] or Radiobuttons, she wouldn’t even have a clue what’s meant by that. And this is what it’s about. Make the concept clear with simple words and reduce the confusion for new users. Streamline the UX.
No, the confusion doesn’t fully stop. Because the “Liste” (the new named Set/Collection) then shows a “Liste” (the content, I mean the Objects that a Collection or Set shows) …
Further more, also the side menu shows a “Liste” of Objects.
Also a numbered list:
- blah
- blubb
- lala
Or a dot list (is is called so?):
- blah
- blubb
- lala
… are lists (or in German: Listen). - Lists of listed points in this case.
That’s the problem (or one of them): the term is not unique. It can become confused with a bunch other things.
Also a day in the Callendar can have a list of entries.
Or I have a shopping list. But in this case I mean a Page with listed items to buy.
If a television doesn’t do anything else then showing a film, it actually is the film itself?
– Really?
After explaining your mom ONCE that the thing is called a “Listbox” she would understand it and I doubt she would ever forget it.
The term is clear in itself.
But if you call it a “List” and the thing shows sometimes a “List” but sometimes a Kanban, Gallery, Grid … she will be confused.
I’m with you if you write:
" Make the concept clear with simple words and reduce the confusion for new users. Streamline the UX."
“Listbox” is clear and simple. And it is unique, it can not be confused with anything else.
“Listbox” is also three chars shorter then “Collection”.
(Yes, and longer then “Set”, that’s true, but “Set” was always a bad choice.)
If you are a German then I wonder why you don’t get it?
German is in general more precise then English. Our words are mostly unique. And we are used to have longer words, even much longer words.
The “Donaudampfschifffahrtsgesellschaftskapitän” subscribes that.
“Collection” is for me already a short word.
“Listbox” is even shorter.
No need at all to make any shorter, while paying the price that it becomes less clear and can be confused.
Nothing costs more time then misunderstandings and after that long words to clear that.
It’s so easy to avoid: Take three letters more (still three less then “Collection”) and call the thing “Listbox”.
.
But I think we can end the discussion here.
It looks like I’m outvoted.
I’ve everything said. Useless to hold on, don’t want to be perceived as stubborn.
Those are “Pages” now. In a technical term “List-Elements”.
This is already called a “Numbered List”
This is already called a “Unsorted List”
- A paper with a shopping list is -tada- just a shopping list, a list.
- you would never say “give me the paper with the list on it that contains shopping items”, would you? you would just say “Gimme that shopping list”.
- My Todoist list is a list, not a “Todoist box that contains a list with entries”. It still is just a list.
No this is not how things work in the normal word. When people don’t live in worlds where specific terms exist, they forget it. It’s like learning a language once and never utilizing them during the day. They will forget the most basic terms very fast.
And this is also -the point- not having the -need- to explain basic things in the first place. And when they don’t get the concept easily and fast they move on.
And I, as born and raised in Germany, wonder why Germans always need to make things more complicated than they have to be.
Indeed
Since this discussion has arisen after a quote from my post, I dare to add this:
In my linguistic understanding, a “Listbox” would be a container that contains lists.
In the case of Collections and Sets, however, this is not the case. They contain objects (pages, notes etc).
A “List” contains list items.
In case of a Collection or a Set this is the case, the list items are objects (pages, notes etc).
This is why in my opinion “List” makes more sense than “Listbox”.
If Anytype would be already FOSS some probably would fork it and create a Listbox-Version
I’d like to remind everyone that many of us are not born english-speakers, and this fact should be sufficient for taking a step back and try to understand the other without malice.
I would also be very happy if we could all write in English, while there are no language-specific comunities. So we can understand what the hell you’re all talking about 
@Code-Jack @krst This was not the right time nor place to discuss these things. Please refrain from going off-topic in the future. I’ve moved your discussion to a separate topic.
I love the terms collection and set. They have mathematical foundation, making them robust.
The term Database would also make sense since they are well studied. But still, sets and collections may be more elegant for anytype.
Listbox, List or anything similar seems nonsensical to me. They would lead to reinventing the wheel, wasting a lot of time and effort.