Thus, it does not make sense to me to say that aliases can “have their own contents”.
I’m not saying that aliases pages must have their own contents, but there’re situations that could be resulted in. E.g. when you have a page alias called A and now you need to refer to other people’ pages (those could be from a team’s repo) and there’s a page A too. The blocks of both pages will be listed in the page “A”, I’m using this a lot with several of my friends, because we can share our opinions on some topics, but we don’t have to use the same words or have to use the same language.
If you have two pages with different content, e.g. one in English and one in Chinese, then those are different pages. They should not automatically redirect to each other and links to one should not automatically link to the other.
I can’t agree on this, for example, the Chinese word for “apple” is “苹果”, I definitely want all the blocks which referenced “apple” to be listed on the page “苹果”, people can use aliases in their own way, you don’t have to add “苹果” as an alias to “apple”, but we keep the flexibility if it’s needed.
If two pages have different content, then there is no “source page”. Each page is its own source.
It depends on how the user add the aliases, if the user adds “苹果” as an alias on “apple”, then “apple” is the source page, but if the user adds “apple” as an alias on “苹果”, then “苹果” is the source page.
Link the English page and the Chinese page with regular links, create a page that embeds the two source pages, or run a query. But there is no other no other convenient way I know to link to the same content with different names other than aliases as I described them.
Yeah, I agree on this. But it’s cumbersome to create a united page every time, it’s really a pain for people whose native language is not English.
Logseq is a tool, it’s great to follow some best practices, but we don’t want to be that rigid like you shouldn’t use the aliases for something.