Is your feature request related to a problem? Please describe.
Huly is incredibly flexible and powerful for building custom workflows, databases, and spaces. However, the hardcoded UI terminology (specifically the use of "Employee") is rigidly corporate. When using Huly for community projects, tabletop RPG management (which your own docs use as an example!), or family organization, being forced to label group members, players, or spouses as "Employees" creates a jarring, un-customizable friction point that limits the platform's universal appeal.
Describe the solution you'd like
A simple way to alias core system terms based on the workspace's intent. This could be implemented in two ways:
Easy implementation:
A "Workspace Type" dropdown in the main settings (e.g., Corporate, Community, Personal) that simply changes the word "Employee" to "Member," "User," or "Person" across the frontend UI.
Advanced implementation:
A small dictionary in Workspace Settings where an Admin can type in a custom alias for "Employee" (e.g., "Player," "Resident," "Contributor").
Describe alternatives you've considered
Currently, the only alternative is self-hosting and changing the codebase, or forcing all users to install client-side browser extensions to run text-replacement scripts, neither of which is viable for a standard cloud user.
Additional context
Huly's core strength is its adaptability. By allowing the top-level directory terminology to be as flexible as the custom Space Types and Cards already are, Huly could easily capture the massive Notion/Obsidian market of personal and community organizers who currently feel alienated by the strictly corporate labeling.
Is your feature request related to a problem? Please describe.
Huly is incredibly flexible and powerful for building custom workflows, databases, and spaces. However, the hardcoded UI terminology (specifically the use of "Employee") is rigidly corporate. When using Huly for community projects, tabletop RPG management (which your own docs use as an example!), or family organization, being forced to label group members, players, or spouses as "Employees" creates a jarring, un-customizable friction point that limits the platform's universal appeal.
Describe the solution you'd like
A simple way to alias core system terms based on the workspace's intent. This could be implemented in two ways:
Easy implementation:
A "Workspace Type" dropdown in the main settings (e.g., Corporate, Community, Personal) that simply changes the word "Employee" to "Member," "User," or "Person" across the frontend UI.
Advanced implementation:
A small dictionary in Workspace Settings where an Admin can type in a custom alias for "Employee" (e.g., "Player," "Resident," "Contributor").
Describe alternatives you've considered
Currently, the only alternative is self-hosting and changing the codebase, or forcing all users to install client-side browser extensions to run text-replacement scripts, neither of which is viable for a standard cloud user.
Additional context
Huly's core strength is its adaptability. By allowing the top-level directory terminology to be as flexible as the custom Space Types and Cards already are, Huly could easily capture the massive Notion/Obsidian market of personal and community organizers who currently feel alienated by the strictly corporate labeling.