Is denormalization recommended with Appwrite DBs?

When structuring data in Appwrite DBs, is it generally recommended to plan for normalization or denormalization?

As in, should I have a single source of truth for all entities and effectively join data when querying? Or should I add redundant copies of data where it makes sense and just reference the duplicated data in my UI?

TL;DR

User is asking for clarification on whether denormalization is recommended when working with Appwrite DBs. They refer to a documentation link and ask if the join capabilities are documented. Another user confirms that Appwrite uses a SQL database with join capabilities. The general consensus is that the decision to normalize or denormalize depends on individual needs and that Appwrite is a versatile tool. The user is seeking advice on whether to plan for normalization or denormalization when structuring data in Appwrite DBs, and asks for recommendations on whether to have a single source of truth and join data when querying or to duplicate data where necessary and reference it in