Create a Figma project - Revision history

Olibouban: /* Configure the Key Generation */

2025-11-07T17:48:47Z

Configure the Key Generation

← Older revision		Revision as of 17:48, 7 November 2025
Line 43:		Line 43:
	= Configure the Key Generation =		= Configure the Key Generation =
	From a Figma project, resource files used by an application can be generated. Examples of resource file types are .properties, JSON, XML, iOS strings.xml, Android Localizable.strings, etc. These resource files need a key so that the application knows which string to display on the UI. Keys are generated on the Figma side so they can be viewed in the Figma design, letting developers know what key to use for what string on the design.		From a Figma project, resource files used by an application can be generated. Examples of resource file types are .properties, JSON, XML, iOS strings.xml, Android Localizable.strings, etc. These resource files need a key so that the application knows which string to display on the UI. Keys are generated on the Figma side so they can be viewed in the Figma design, letting developers know what key to use for what string on the design.

			See: [[Create_a_Localyzer_only_project#Figma_to_Dev]]

	[[File:FKEY.png\|center\|600px]]		[[File:FKEY.png\|center\|600px]]

Olibouban: /* Configure the Key Generation */

2025-11-07T17:47:22Z

Configure the Key Generation

← Older revision		Revision as of 17:47, 7 November 2025
Line 52:		Line 52:

	For example, if the design string is <code>Welcome</code>, the generated key could be <code>FKEY_Welcome_17</code> based on the configuration shown in the screen shot above.		For example, if the design string is <code>Welcome</code>, the generated key could be <code>FKEY_Welcome_17</code> based on the configuration shown in the screen shot above.

			'''Note''': If on the Developer's repository, the same file will have strings generated from different Figma Localyzer projects, then the Prefix should be different in each Figma Localyzer projects. For instance, if one Figma design is targeting an Admin screen and another, separate, Figma design is targeting a User screen, and they are on-boarded with two different Localyzer projects, one could have an ADM prefix, the other a USR project, so that two strings both named 'Home' would have unique keys in the same generated Developers project, say ADM_Home_1 and USR_Home_1.

	= Advanced Settings =		= Advanced Settings =

Olibouban: /* Project Name */

2025-11-03T20:38:49Z

Project Name

← Older revision		Revision as of 20:38, 3 November 2025
Line 25:		Line 25:
	# Set the '''Module Name'''. This is defaulted to the branch that the project is using.		# Set the '''Module Name'''. This is defaulted to the branch that the project is using.
	# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.		# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.

			In the module name above, 4.0.41 would not be accepted, the dots (.) would have to be replaced by, say underscores (_).

	= Accessors =		= Accessors =

Olibouban: /* Data Source Settings */

2025-11-03T20:37:24Z

Data Source Settings

← Older revision		Revision as of 20:37, 3 November 2025
Line 3:		Line 3:
	Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:		Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:
	* figma/locales/<locale>/translation.json		* figma/locales/<locale>/translation.json


	~~[[File:FDSSelection.png\|center\|600px]]~~

	If the source locale is, say 'en', then a JSON file must exist in order for the process to complete successfully:		If the source locale is, say 'en', then a JSON file must exist in order for the process to complete successfully:
Line 14:		Line 11:
	{		{
	}		}


			[[File:FDSSelection.png\|center\|600px]]

	= Project Name =		= Project Name =

Olibouban: /* Data Source Settings */

2025-11-03T20:36:28Z

Data Source Settings

← Older revision		Revision as of 20:36, 3 November 2025
Line 2:		Line 2:

	Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:		Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:
	* ~~Figma~~/locales/<locale>/translation.json		* figma/locales/<locale>/translation.json


	[[File:FDSSelection.png\|center\|600px]]		[[File:FDSSelection.png\|center\|600px]]

			If the source locale is, say 'en', then a JSON file must exist in order for the process to complete successfully:
			* figma/locales/en/translation.json

			The translation.json file can be as simple as:

			{
			}

	= Project Name =		= Project Name =

Olibouban: /* Pick a Translation System and Locales */

2025-10-29T14:55:07Z

Pick a Translation System and Locales

← Older revision		Revision as of 14:55, 29 October 2025
Line 24:		Line 24:
	[[File:FAccessors.png\|center\|600px]]		[[File:FAccessors.png\|center\|600px]]

	= ~~Pick a~~ Translation ~~System~~ and Locales =		= Translation Connections and Locales =
	Select a Machine Translation, an LLM, or a Translation Management System that will be translating the resource files. These need to have been created before attempting to create a Localyzer project.		Select a Machine Translation, an LLM, or a Translation Management System that will be translating the resource files. These need to have been created before attempting to create a Localyzer project.

Olibouban: /* Grant API, User, and Team Access */

2025-10-29T14:54:48Z

Grant API, User, and Team Access

← Older revision		Revision as of 14:54, 29 October 2025
Line 18:		Line 18:
	# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.		# '''Tags''' - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.

	= ~~Grant API, User, and Team Access~~ =		= Accessors =
	Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.		Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.
	The Lingoport Figma Plugin is configured with an API User and token for a Figma project in Command Center. A Command Center Figma project must have an assigned API User.		The Lingoport Figma Plugin is configured with an API User and token for a Figma project in Command Center. A Command Center Figma project must have an assigned API User.

Olibouban: /* Name the project */

2025-10-29T14:54:31Z

Name the project

← Older revision		Revision as of 14:54, 29 October 2025
Line 7:		Line 7:
	[[File:FDSSelection.png\|center\|600px]]		[[File:FDSSelection.png\|center\|600px]]

	= Name ~~the project~~ =		= Project Name =

	The values on this page are initially filled in based on the repository, but can be changed at creation or later while editing.		The values on this page are initially filled in based on the repository, but can be changed at creation or later while editing.

Olibouban: /* Data Source Settings */

2025-10-29T14:41:41Z

Data Source Settings

← Older revision		Revision as of 14:41, 29 October 2025
Line 3:		Line 3:
	Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:		Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:
	* Figma/locales/<locale>/translation.json		* Figma/locales/<locale>/translation.json


	[[File:FDSSelection.png\|center\|600px]]		[[File:FDSSelection.png\|center\|600px]]

Olibouban: /* Credentials and Repository */

2025-10-29T14:41:30Z

Credentials and Repository

← Older revision		Revision as of 14:41, 29 October 2025
Line 1:		Line 1:
	= ~~Credentials and Repository~~=		= Data Source Settings =

	~~When Manager users are created, Data Source Credentials are assigned. If~~ the ~~Manager does not have any Data Source Credentials assigned~~, ~~the process will fail with the error~~: '''Must have access to at least one credential before creating a project'''. Contact an Administrator to get credential access. Administrator users have access to all Data Source Credentials in the system.		Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:
			* Figma/locales/<locale>/translation.json

	[[File:FDSSelection.png\|center\|600px]]		[[File:FDSSelection.png\|center\|600px]]

	~~Figma projects use a repository to store the strings coming from the Lingoport Figma Plugin, in a file following this pattern:~~
	* Figma/locales/<locale>/translation.json

	= Name the project =		= Name the project =