Skip to content

doc: add preferences auth concept page #2056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

ebenezerdon
Copy link
Contributor

@ebenezerdon ebenezerdon commented May 29, 2025

What does this PR do?

Adds new auth concept page, preferences

Test Plan

  • /docs/products/auth/preferences

Related PRs and Issues

DRL-1430

@ebenezerdon ebenezerdon marked this pull request as ready for review May 30, 2025 22:11
});

// Get team preferences
const promise = teams.get('<TEAM_ID>');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we should be consistent and use teams.getPrefs('<TEAM_ID>')?

Comment on lines 39 to 42
{
label: 'Preferences',
href: '/docs/products/auth/preferences'
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the docs were first designed/structured, Concepts were used to explain aspects in Appwrite while Journeys talked more about use cases. See our style guide:

image

Given that, I would recommend splitting up the content so that this new Preferences content goes under Journeys.

If we want Preferences more discoverable, we should move the Preferences in Accounts into its own page and add a section on Team Preferences.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done @stnguyen90 Please check out the update

| **Schema Validation** | No | No | No | Yes |
| **Offline Access** | Yes | No | No | No** |
| **Syncing Required** | Yes | Automatic | Automatic | Manual |
| **Query Capabilities** | Basic | Basic | Basic | Advanced |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When I hear query, I think of being able to fetch for a certain value or filter, but you can't really query user/team preferences 🧐

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense. I'll change to "no, no, no, yes"

| **Complexity** | Simple | Simple | Simple | Complex |
| **Schema Validation** | No | No | No | Yes |
| **Offline Access** | Yes | No | No | No** |
| **Syncing Required** | Yes | Automatic | Automatic | Manual |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is user/team preferences automatic but databases manual?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The idea was that with user/team preferences, Appwrite does most of the setup work. But with Databases, how it functions depends on the user. Maybe I should change Databases to automatic

- Persists across all user devices
- Stored as a JSON object
- Limited to 64kB of data
- Automatically synced when the user logs in
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by this? where is it synced to?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Syncs from the cloud to their device. Is there another way we could pass this, or is the line not necessary?

@ebenezerdon ebenezerdon requested a review from stnguyen90 June 20, 2025 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants