-
-
Notifications
You must be signed in to change notification settings - Fork 724
Design tools
Figma is a design software to create mockups, prototypes and collaboration boards. We currently have a professional plan for our "team".
The owner of the Figma organisation is the account connected to [email protected]. Please reach out to AU OFN folks if you need access to it.
In Figma, a team is a group of registered users. Each user might have different permissions for team management and file viewing/editing.
This plan charges you based on how many people have permissions to edit files. There are 2 different tools within the software, Figma (for digital design) and Figjam (for collaborative boards, workshops and similar). Permissions apply to each individual tool. You can see below each row is a member of the team, and which permissions end up being charged.
Figma applies a pretty shady approach to add members to the team. If, for example, I create a design file that I want people to edit, as soon as they open it, and if they have a Figma account, they will be automatically added as a team member, and that seat will be charged at the end of the month.
Given the above, I would recommend to:
- give editing access to designers only, unless there's a specific reason to allow others to edit
- use Mural for workshops, and not Figjam, since Figjam would start charging per seat as soon as people join the board
- for every Figma file that needs to be shared for feedback, allow everyone TO VIEW ONLY. this will avoid any risks of creating new members that we need to pay for
At the moment there are quite a few people with admin role, who can assign editing permissions to accounts. Either Rachel or someone in the AU team with access to the [email protected] account can grant editing permissions.
Development environment setup
- Pipeline development process
- Bug severity
- Feature template (epic)
- Internationalisation (i18n)
- Dependency updates
Development
- Developer Guidelines
- The process of review, test, merge and deploy
- Making a great commit
- Making a great pull request
- Code Conventions
- Database migrations
- Testing and Rspec Tips
- Automated Testing Gotchas
- Rubocop
- Angular and OFN
- Feature toggles
- Stimulus and Turbo
Testing
- Testing process
- OFN Testing Documentation (Handbooks)
- Continuous Integration
- Parallelized test suite with knapsack
- Karma
Releasing
Specific features
Data and APIs
Instance-specific configuration
External services
Design