Design
The login view mirrors the same layout as the create user page but just asks for the username or email and the password. There is also a "forgot password" link for recovery. A small sign-up link for users who do not have an account takes users to the sign-up page. On sign-in, it takes the user to the Project Dashboard.
This screen lets new users create an account with a simple, centered form using a dark theme and a blue action button. The fields are Full name, username, email, password, and confirm password. This is followed by a terms checkbox and the sign-up button. After submission, the user is taken to the login screen.
Project Dash opens a repository view for the projects you have, where you can view recent commit data, quick controls for conflicts, total commits, and new files. The main table lists folders and files with each item's last commit message and time. The README panel provides the project overview and notes created by the user. Clicking an item opens it; the commit chip leads to the timeline.
The commit detail screen presents a clear header with title, author, date, and a short hash, followed by a "Files Changed" list that shows paths. You can also see modified or added changes to the project. From here, users can review changes and compare changes or revert before navigating back to the project.
This page page provides a centralized view of all user actions and contributions across a Blender project. It tracks commits, object locks/unlocks, and merges in real time, ensuring that team members remain informed about ongoing work. Users can filter activities by person, project, or activity type for streamlined navigation. On the right side, a visual chart shows the breakdown of contributions per user over a chosen time frame, making it easy to monitor workload distribution and collaboration patterns within the team.
This page allows users to resolve conflicts that arise when multiple changes are made to the same Blender object or file. It provides a side-by-side comparison of the user’s version and the incoming version, offering a clear visualization of conflicting changes. Resolution actions enable the user to either accept their own version or apply the incoming one, after which the merge can be finalized with a single commit. This page simplifies conflict resolution, ensuring smooth collaboration and version control in Blender projects.
This screen allows users to manage their account details, notifications, security, and integrations. The Profile section includes editable fields for name, email, and password, along with an “Update Profile” button. In the Notifications section, users can toggle email alerts for project updates, in-app notifications for comments, and a weekly summary option which essentially summarizes weekly updates for you. The Security section provides a toggle to enable two-factor authentication for account protection. The Integrations area offers an option to connect the account to other services with a “Connect” button. The page uses a dark theme with blue accents for actions.
This screen provides users with tools to manage version history and current changes in a project. On the left, the Commit Actions section includes a field to enter a commit message and buttons for Commit, Push, and Pull actions. Below, the Current Changes list displays files flagged as modified, new, or deleted (e.g., Object_A, Object_B, Material_X), allowing users to select specific items to include in the commit. On the right, the Commit History shows a chronological log of previous commits with messages, author names, and timestamps. This helps users track updates like lighting changes, character additions, and texture fixes. The UI uses a dark theme with a modular, panel-based layout for clarity.