Freegle Affiliated Group Name and Logo Guidelines - Revision history

RevampBot: Wiki revamp: restructure & modernise

2026-07-17T12:00:00Z

Wiki revamp: restructure & modernise

← Older revision		Revision as of 12:00, 17 July 2026
Line 4:		Line 4:
	*More than one way of describing a location should be avoided where possible.		*More than one way of describing a location should be avoided where possible.
	*Local acronyms, that are meaningless to most people, should be avoided.		*Local acronyms, that are meaningless to most people, should be avoided.
	*Acronyms should be checked carefully before naming and avoided, e.g. Freegle Friendly Support (F.F.S)		*Acronyms should be checked carefully before naming and avoided, e.g. Freegle Friendly Support (F.F.S).

	===Best practice examples for community names===		===Best practice examples for community names===
	Example area/town name = Blue River~~<br>~~		Example area/town name = Blue River
	~~Example Community Name = Freegle<br>~~

	When existing communities move to Freegle, the community name may be something else already e.g. GreenCycle. New communities to Freegle, though, must be named Freegle as this helps to raise our public profile everywhere.		Example Community Name = Freegle

			When existing communities move to Freegle, the community name may be something else already, e.g. GreenCycle. New communities to Freegle, though, must be named Freegle, as this helps to raise our public profile everywhere.

	====Freegle Direct====		====Freegle Direct====
	''Suggested format'': ~~“AreaNameGroupName” eg “BlueRiverFreegle” <br>~~		''Suggested format'': "AreaNameGroupName", e.g. "BlueRiverFreegle". Set up by NGT with a short name and avoiding hyphens wherever possible, e.g. BlueRiverFreegle.
	Set up by NGT with a short name and avoiding hyphens wherever possible ~~eg BlueRiverFreegle~~

	~~A longer descriptive name may be used for the website eg Blue River Freegle~~.
	~~<br>The Freegle Direct volunteer email address is automatically generated from the shortname~~. ~~In this case it would be~~ BlueRiverFreegle~~-volunteers@groups.ilovefreegle~~.~~org~~

	The actual name displayed alongside this on Freegle Direct would be Blue River Freegle		A longer descriptive name may be used for the website, e.g. Blue River Freegle.

			The Freegle Direct volunteer email address is automatically generated from the shortname. In this case it would be BlueRiverFreegle-volunteers@groups.ilovefreegle.org

			The actual name displayed alongside this on Freegle Direct would be Blue River Freegle.

	====Facebook (FB) Page Name and Facebook (FB) URL====		====Facebook (FB) Page Name and Facebook (FB) URL====
	A space between words is needed for the page name for FB search optimisation.~~<br>~~		A space between words is needed for the page name for FB search optimisation.
	''FB Page Name suggested format'': ~~“Area~~ Name Community ~~Name”~~ e.g~~: “Blue~~ River ~~Freegle”~~ - this what the FB page should be called when it is first set up.
	~~<br>~~Once the FB group has been ~~“liked”~~ 25 times a username can be chosen to give a better URL – this is good to have for publicity purposes and can be words with no spaces.		''FB Page Name suggested format'': "Area Name Community Name", e.g. "Blue River Freegle" - this is what the FB page should be called when it is first set up.
	~~<br>~~''FB Username (URL) suggested ~~forma~~''t: ~~“AreaNameGroupName”~~ e.g~~: “BlueRiverFreegle”~~ - the URL would be: www.facebook.com/BlueRiverFreegle [note: FB search will recognise ~~“BlueRiverFreegle”~~ if ~~it’s~~ typed in with or without the capitals]
			Once the FB group has been "liked" 25 times, a username can be chosen to give a better URL - this is good to have for publicity purposes and can be words with no spaces.

			''FB Username (URL) suggested format'': "AreaNameGroupName", e.g. "BlueRiverFreegle" - the URL would be www.facebook.com/BlueRiverFreegle (note: FB search will recognise "BlueRiverFreegle" if it's typed in with or without the capitals).

	====Twitter====		====Twitter====
	A space between words is needed for the profile name so that it is searchable on Twitter.~~<br>~~		A space between words is needed for the profile name so that it is searchable on Twitter.
	''Twitter profile name suggested format'': ~~“Area~~ Name Community ~~Name”~~ e.g~~: “Blue~~ River ~~Freegle”~~ (~~Profile~~ names are limited to 20 characters only).~~<br>~~
	Twitter handle/tag: these are limited to 15 characters and all one word – creativity may be needed! ~~eg “BluRiverFreegle”<br>~~		''Twitter profile name suggested format'': "Area Name Community Name", e.g. "Blue River Freegle" (profile names are limited to 20 characters only).
	The ~~“Area Name”~~ and ~~“Freegle”~~ (or other community name) should be put in the biography section of the profile.~~<br>~~
	The ilovefreegle URL should be used as the website link in that section of the profile.~~<br>~~		Twitter handle/tag: these are limited to 15 characters and all one word - creativity may be needed! E.g. "BluRiverFreegle".

			The "Area Name" and "Freegle" (or other community name) should be put in the biography section of the profile.

			The ilovefreegle URL should be used as the website link in that section of the profile.

	The logo designed by the media team should be used rather than the default picture as a photo.		The logo designed by the media team should be used rather than the default picture as a photo.

	====ilovefreegle Mapping====		====ilovefreegle Mapping====
	Map drawn at ~~communtiy~~ creation by NGT.~~<br>~~		Map drawn at community creation by NGT.
	''Suggested format:'' ~~“Region~~, Area Name Community ~~Name”~~ so that they show up in logical order ~~eg “S~~.East: Blue River Freegle
			''Suggested format:'' "Region, Area Name Community Name", so that they show up in logical order, e.g. "S.East: Blue River Freegle".

	====Email Addresses====		====Email Addresses====
	Freegle Direct will have same name format stemming from the community name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org)~~<br>~~		Freegle Direct will have the same name format stemming from the community name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org).
	If a different account is going to be used to create an address for a new community (eg. Gmail): ~~<br>~~''Suggested format'' : ~~“AreaNameGroupName~~@’ e.g: BlueRiverFreegle@gmail.com
			If a different account is going to be used to create an address for a new community (e.g. Gmail): ''Suggested format'': "AreaNameGroupName@", e.g. BlueRiverFreegle@gmail.com

	====Freegle Shortlink====		====Freegle Shortlink====
	''Suggested format'': Freegle.in/AreaName, Freegle.it/AreaName e.g. Freegle.in/BlueRiver, Freegle.it/BlueRiver		''Suggested format'': Freegle.in/AreaName, Freegle.it/AreaName, e.g. Freegle.in/BlueRiver, Freegle.it/BlueRiver

	===Logos===		===Logos===
	The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start up of communities.~~<br>~~		The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start-up of communities.

	''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Standard Communities====		====Standard Communities====
	''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom.~~<br>~~		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom.

	Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Specialist Groups====		====Specialist Groups====
	''Suggested format'': the format used for the Sussex Disability Aids Community can be used for other communities: ~~“freegle~~ disability ~~aids”~~ inside the heart and ~~“AreaName”~~ underneath.		''Suggested format'': the format used for the Sussex Disability Aids Community can be used for other communities: "freegle disability aids" inside the heart and "AreaName" underneath.



	These guidelines were adopted by the Board at their meeting of 29th October 2014 and subsequently amended in January 2018 as part of the 'ditching Yahoo' review of procedure. There was also one amendment following a proposal at the AGM in November 2019.		These guidelines were adopted by the Board at their meeting of 29th October 2014 and subsequently amended in January 2018 as part of the 'ditching Yahoo' review of procedure. There was also one amendment following a proposal at the AGM in November 2019.

	===Links===		===Links===
	*Previous Freegle UK document - Group Affiliation Team - Naming New Groups		*Previous Freegle UK document - Group Affiliation Team - Naming New Groups
	* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]		*AGM 2019 Proposal: [https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]
	*[[Changing community name]]		*[[Changing community name]]
	*[[New Groups Team - NGT]]		*[[New Groups Team - NGT]]
Line 69:		Line 80:
	*[[Glossary]]		*[[Glossary]]

	[[~~category~~:~~Policies, Procedures, Remits~~]][[~~category~~:New Groups Team]]		[[Category:Organisation & Governance]]
			[[Category:New Groups Team]]
			[[Category:Policies, Procedures, Remits]]

Jacky: /* Links */

2025-07-06T12:03:55Z

Links

← Older revision		Revision as of 12:03, 6 July 2025
Line 64:		Line 64:
	*Previous Freegle UK document - Group Affiliation Team - Naming New Groups		*Previous Freegle UK document - Group Affiliation Team - Naming New Groups
	* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]		* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]
			*[[Changing community name]]
	*[[New Groups Team - NGT]]		*[[New Groups Team - NGT]]
	*[[Document Approval Policy]]		*[[Document Approval Policy]]

Neville Reid: Protected "Freegle Affiliated Group Name and Logo Guidelines": Board-approved page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2024-11-14T17:44:08Z

Protected "Freegle Affiliated Group Name and Logo Guidelines": Board-approved page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 17:44, 14 November 2024
(No difference)

Jacky at 14:12, 22 November 2021

2021-11-22T14:12:14Z

Jacky: /* Links */

2019-12-07T08:52:27Z

Links

← Older revision		Revision as of 08:52, 7 December 2019
Line 68:		Line 68:
	*[[Glossary]]		*[[Glossary]]

	[[category:Policies, Procedures, Remits]][[category:~~Group Affiliation~~ Team]]		[[category:Policies, Procedures, Remits]][[category:New Groups Team]]

Jacky at 01:33, 3 December 2019

2019-12-03T01:33:19Z

← Older revision		Revision as of 01:33, 3 December 2019
Line 62:		Line 62:

	===Links===		===Links===
	*Previous Freegle UK document - [[Group Affiliation Team - Naming New Groups]]		*Previous Freegle UK document - Group Affiliation Team - Naming New Groups
	* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]		* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]
	*[[Group Affiliation Team - GAT]]		*Group Affiliation Team - GAT
	*[[Document Approval Policy]]		*[[Document Approval Policy]]
	*[[Glossary]]		*[[Glossary]]

	[[category:Policies, Procedures, Remits]][[category:Group Affiliation Team]]		[[category:Policies, Procedures, Remits]][[category:Group Affiliation Team]]

Chriscant: Changes due to AGM 2019 vote

2019-11-23T11:44:34Z

Changes due to AGM 2019 vote

← Older revision		Revision as of 11:44, 23 November 2019
Line 1:		Line 1:
	~~These guidelines were adopted by the Board at their meeting of 29th October 2014 and subsequently amended in January 2018 as part of the 'ditching Yahoo' review of procedure.~~


	===General things to consider when 'naming' a group===		===General things to consider when 'naming' a group===
	*Group names should be consistent to avoid confusion for members of the public. They should ideally have the same format across all platforms (Freegle Direct, Facebook, Twitter, etc).		*Group names should be consistent to avoid confusion for members of the public. They should ideally have the same format across all platforms (Freegle Direct, Facebook, Twitter, etc).
Line 12:		Line 9:
	Example area/town name = Blue River<br>		Example area/town name = Blue River<br>
	Example Group Name = Freegle<br>		Example Group Name = Freegle<br>
	(When existing groups move to Freegle, the group name may be something else already e.g. GreenCycle. ~~It is preferable though for new~~ groups to be named Freegle as this helps to raise our public profile everywhere)
			When existing groups move to Freegle, the group name may be something else already e.g. GreenCycle. New groups to Freegle, though, must be named Freegle as this helps to raise our public profile everywhere.

	====Freegle Direct====		====Freegle Direct====
Line 61:		Line 59:


			These guidelines were adopted by the Board at their meeting of 29th October 2014 and subsequently amended in January 2018 as part of the 'ditching Yahoo' review of procedure. There was also one amendment following a proposal at the AGM in November 2019.

	===Links===		===Links===
	*Previous Freegle UK document - [[Group Affiliation Team - Naming New Groups]]		*Previous Freegle UK document - [[Group Affiliation Team - Naming New Groups]]
			* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]
	*[[Group Affiliation Team - GAT]]		*[[Group Affiliation Team - GAT]]
	*[[Document Approval Policy]]		*[[Document Approval Policy]]

Jacky at 13:04, 24 January 2018

2018-01-24T13:04:59Z

Jacky at 16:35, 23 January 2018

2018-01-23T16:35:22Z

Show changes

Jacky: /* 2. Specialist groups */

2015-07-24T19:53:55Z

2. Specialist groups

← Older revision		Revision as of 19:53, 24 July 2015
Line 110:		Line 110:

	Links:		Links:
	*Previous Freegle UK document - [[Group Affiliation Team -~~_Naming_New_Groups~~]]		*Previous Freegle UK document - [[Group Affiliation Team - Naming New Groups]]
	*~~Amendments : in line with~~ [[Document Approval Policy]]		*[[Group Affiliation Team - GAT]]
	*Glossary		* [[Document Approval Policy]]
			*[[Glossary]]

	[[category:Policies, Procedures, Remits]]		[[category:Policies, Procedures, Remits]][[category:Group Affiliation Team]]

← Older revision		Revision as of 14:12, 22 November 2021
Line 1:		Line 1:
	===General things to consider when 'naming' a ~~group~~===		===General things to consider when 'naming' a community===
	*~~Group~~ names should be consistent to avoid confusion for members of the public. They should ideally have the same format across all platforms (Freegle Direct, Facebook, Twitter, etc).		*Community names should be consistent to avoid confusion for members of the public. They should ideally have the same format across all platforms (Freegle Direct, Facebook, Twitter, etc).
	*~~Group~~ names based on a town rather than area tend to do better.		*Community names based on a town rather than area tend to do better.
	*More than one way of describing a location should be avoided where possible.		*More than one way of describing a location should be avoided where possible.
	*Local acronyms, that are meaningless to most people, should be avoided.		*Local acronyms, that are meaningless to most people, should be avoided.
	*Acronyms should be checked carefully before naming and avoided, e.g. Freegle Friendly Support (F.F.S)		*Acronyms should be checked carefully before naming and avoided, e.g. Freegle Friendly Support (F.F.S)

	===Best practice examples for ~~group~~ names===		===Best practice examples for community names===
	Example area/town name = Blue River<br>		Example area/town name = Blue River<br>
	Example ~~Group~~ Name = Freegle<br>		Example Community Name = Freegle<br>

	When existing ~~groups~~ move to Freegle, the ~~group~~ name may be something else already e.g. GreenCycle. New ~~groups~~ to Freegle, though, must be named Freegle as this helps to raise our public profile everywhere.		When existing communities move to Freegle, the community name may be something else already e.g. GreenCycle. New communities to Freegle, though, must be named Freegle as this helps to raise our public profile everywhere.

	====Freegle Direct====		====Freegle Direct====
	''Suggested format'': “AreaNameGroupName” eg “BlueRiverFreegle” <br>		''Suggested format'': “AreaNameGroupName” eg “BlueRiverFreegle” <br>
	Set up by ~~the Newgroups Team~~ with a short name and avoiding hyphens wherever possible eg BlueRiverFreegle		Set up by NGT with a short name and avoiding hyphens wherever possible eg BlueRiverFreegle

	A longer descriptive name may be used for the website eg Blue River Freegle.		A longer descriptive name may be used for the website eg Blue River Freegle.
Line 23:		Line 23:
	====Facebook (FB) Page Name and Facebook (FB) URL====		====Facebook (FB) Page Name and Facebook (FB) URL====
	A space between words is needed for the page name for FB search optimisation.<br>		A space between words is needed for the page name for FB search optimisation.<br>
	''FB Page Name suggested format'': “Area Name ~~Group~~ Name” e.g: “Blue River Freegle” - this what the FB page should be called when it is first set up.		''FB Page Name suggested format'': “Area Name Community Name” e.g: “Blue River Freegle” - this what the FB page should be called when it is first set up.
	<br>Once the FB group has been “liked” 25 times a username can be chosen to give a better URL – this is good to have for publicity purposes and can be words with no spaces.		<br>Once the FB group has been “liked” 25 times a username can be chosen to give a better URL – this is good to have for publicity purposes and can be words with no spaces.
	<br>''FB Username (URL) suggested forma''t: “AreaNameGroupName” e.g: “BlueRiverFreegle” - the URL would be: www.facebook.com/BlueRiverFreegle [note: FB search will recognise “BlueRiverFreegle” if it’s typed in with or without the capitals]		<br>''FB Username (URL) suggested forma''t: “AreaNameGroupName” e.g: “BlueRiverFreegle” - the URL would be: www.facebook.com/BlueRiverFreegle [note: FB search will recognise “BlueRiverFreegle” if it’s typed in with or without the capitals]
Line 29:		Line 29:
	====Twitter====		====Twitter====
	A space between words is needed for the profile name so that it is searchable on Twitter.<br>		A space between words is needed for the profile name so that it is searchable on Twitter.<br>
	''Twitter profile name suggested format'': “Area Name ~~Group~~ Name” e.g: “Blue River Freegle” (Profile names are limited to 20 characters only).<br>		''Twitter profile name suggested format'': “Area Name Community Name” e.g: “Blue River Freegle” (Profile names are limited to 20 characters only).<br>
	Twitter handle/tag: these are limited to 15 characters and all one word – creativity may be needed! eg “BluRiverFreegle”<br>		Twitter handle/tag: these are limited to 15 characters and all one word – creativity may be needed! eg “BluRiverFreegle”<br>
	The “Area Name” and “Freegle” (or other ~~group~~ name) should be put in the biography section of the profile.<br>		The “Area Name” and “Freegle” (or other community name) should be put in the biography section of the profile.<br>
	The ilovefreegle URL should be used as the website link in that section of the profile.<br>		The ilovefreegle URL should be used as the website link in that section of the profile.<br>
	The logo designed by the media team should be used rather than the default picture as a photo.		The logo designed by the media team should be used rather than the default picture as a photo.

	====ilovefreegle Mapping====		====ilovefreegle Mapping====
	Map drawn at ~~group~~ creation by ~~the Newgroups Team~~.<br>		Map drawn at communtiy creation by NGT.<br>
	''Suggested format:'' “Region, Area Name ~~Group~~ Name” so that they show up in logical order eg “S.East: Blue River Freegle		''Suggested format:'' “Region, Area Name Community Name” so that they show up in logical order eg “S.East: Blue River Freegle

	====Email Addresses====		====Email Addresses====
	Freegle Direct will have same name format stemming from the ~~group~~ name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org)<br>		Freegle Direct will have same name format stemming from the community name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org)<br>
	If a different account is going to be used to create an address for a new ~~group~~ (eg. Gmail): <br>''Suggested format'' : “AreaNameGroupName@’ e.g: BlueRiverFreegle@gmail.com		If a different account is going to be used to create an address for a new community (eg. Gmail): <br>''Suggested format'' : “AreaNameGroupName@’ e.g: BlueRiverFreegle@gmail.com

	====Freegle Shortlink====		====Freegle Shortlink====
Line 47:		Line 47:

	===Logos===		===Logos===
	The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start up of ~~groups~~.<br>		The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start up of communities.<br>
	''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, ~~group~~ name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Standard ~~Groups~~====		====Standard Communities====
	''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, ~~group~~ name at the bottom.<br>		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, community name at the bottom.<br>
	Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Specialist Groups====		====Specialist Groups====
	''Suggested format'': the format used for the Sussex Disability Aids ~~Group~~ can be used for other ~~groups~~: “freegle disability aids” inside the heart and “AreaName” underneath.		''Suggested format'': the format used for the Sussex Disability Aids Community can be used for other communities: “freegle disability aids” inside the heart and “AreaName” underneath.


Line 64:		Line 64:
	*Previous Freegle UK document - Group Affiliation Team - Naming New Groups		*Previous Freegle UK document - Group Affiliation Team - Naming New Groups
	* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]		* AGM 2019 Proposal [[https://discourse.ilovefreegle.org/t/agm-2019-agenda-item-7-group-names/683]
	*~~Group Affiliation~~ Team - ~~GAT~~		*[[New Groups Team - NGT]]
	*[[Document Approval Policy]]		*[[Document Approval Policy]]
	*[[Glossary]]		*[[Glossary]]

	[[category:Policies, Procedures, Remits]][[category:New Groups Team]]		[[category:Policies, Procedures, Remits]][[category:New Groups Team]]

← Older revision		Revision as of 13:04, 24 January 2018
Line 15:		Line 15:

	====Freegle Direct====		====Freegle Direct====
	Suggested format: “AreaNameGroupName” eg “BlueRiverFreegle” <br>		''Suggested format'': “AreaNameGroupName” eg “BlueRiverFreegle” <br>
	Set up by the Newgroups Team with a short name and avoiding hyphens wherever possible eg BlueRiverFreegle		Set up by the Newgroups Team with a short name and avoiding hyphens wherever possible eg BlueRiverFreegle

Line 21:		Line 21:
	<br>The Freegle Direct volunteer email address is automatically generated from the shortname. In this case it would be BlueRiverFreegle-volunteers@groups.ilovefreegle.org		<br>The Freegle Direct volunteer email address is automatically generated from the shortname. In this case it would be BlueRiverFreegle-volunteers@groups.ilovefreegle.org

	The actual name displayed alongside this on Freegle Direct would be Blue River Freegle		The actual name displayed alongside this on Freegle Direct would be Blue River Freegle

	====Facebook (FB) Page Name and Facebook (FB) URL====		====Facebook (FB) Page Name and Facebook (FB) URL====
	A space between words is needed for the page name for FB search optimisation.<br>		A space between words is needed for the page name for FB search optimisation.<br>
	FB Page Name suggested format: “Area Name Group Name” e.g: “Blue River Freegle” - this what the FB page should be called when it is first set up.		''FB Page Name suggested format'': “Area Name Group Name” e.g: “Blue River Freegle” - this what the FB page should be called when it is first set up.
	<br>Once the FB group has been “liked” 25 times a username can be chosen to give a better URL – this is good to have for publicity purposes and can be words with no spaces.		<br>Once the FB group has been “liked” 25 times a username can be chosen to give a better URL – this is good to have for publicity purposes and can be words with no spaces.
	<br>FB Username (URL) suggested ~~format~~: “AreaNameGroupName” e.g: “BlueRiverFreegle” - the URL would be: www.facebook.com/BlueRiverFreegle [note: FB search will recognise “BlueRiverFreegle” if it’s typed in with or without the capitals]		<br>''FB Username (URL) suggested forma''t: “AreaNameGroupName” e.g: “BlueRiverFreegle” - the URL would be: www.facebook.com/BlueRiverFreegle [note: FB search will recognise “BlueRiverFreegle” if it’s typed in with or without the capitals]

	====Twitter====		====Twitter====
	A space between words is needed for the profile name so that it is searchable on Twitter.<br>		A space between words is needed for the profile name so that it is searchable on Twitter.<br>
	Twitter profile name suggested format: “Area Name Group Name” e.g: “Blue River Freegle” (Profile names are limited to 20 characters only).<br>		''Twitter profile name suggested format'': “Area Name Group Name” e.g: “Blue River Freegle” (Profile names are limited to 20 characters only).<br>
	Twitter handle/tag: these are limited to 15 characters and all one word – creativity may be needed! eg “BluRiverFreegle”<br>		Twitter handle/tag: these are limited to 15 characters and all one word – creativity may be needed! eg “BluRiverFreegle”<br>
	The “Area Name” and “Freegle” (or other group name) should be put in the biography section of the profile.<br>		The “Area Name” and “Freegle” (or other group name) should be put in the biography section of the profile.<br>
Line 38:		Line 38:

	====ilovefreegle Mapping====		====ilovefreegle Mapping====
	Map drawn at group creation by the Newgroups Team. Suggested format “Region, Area Name Group Name” so that they show up in logical order eg “S.East: Blue River Freegle		Map drawn at group creation by the Newgroups Team.<br>
			''Suggested format:'' “Region, Area Name Group Name” so that they show up in logical order eg “S.East: Blue River Freegle

	====Email Addresses====		====Email Addresses====
	Freegle Direct will have same name format stemming from the group name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org)<br>		Freegle Direct will have same name format stemming from the group name (as above - BlueRiverFreegle-volunteers@groups.ilovefreegle.org)<br>
	If a different account is going to be used to create an address for a new group (eg. Gmail): Suggested format : “AreaNameGroupName@’ e.g: BlueRiverFreegle@gmail.com		If a different account is going to be used to create an address for a new group (eg. Gmail): <br>''Suggested format'' : “AreaNameGroupName@’ e.g: BlueRiverFreegle@gmail.com

	====Freegle Shortlink====		====Freegle Shortlink====
	Suggested format: Freegle.in/AreaName, Freegle.it/AreaName e.g. Freegle.in/BlueRiver, Freegle.it/BlueRiver		''Suggested format'': Freegle.in/AreaName, Freegle.it/AreaName e.g. Freegle.in/BlueRiver, Freegle.it/BlueRiver

	===Logos===		===Logos===
	The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start up of groups.<br>		The Graphics Team will provide a set of logos for use on Freegle Direct, Facebook, Twitter and promotional material at the start up of groups.<br>
	Suggested format: Text inside the Freegle Heart - Area Name or area name at the top, group name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, group name at the bottom. Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Standard Groups====		====Standard Groups====
	Suggested format: Text inside the Freegle Heart - Area Name or area name at the top, group name at the bottom.<br>		''Suggested format'': Text inside the Freegle Heart - Area Name or area name at the top, group name at the bottom.<br>
	Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.		Both capitalised and uncapitalised area names can be used, but freegle should always be lowercase for branding purposes.

	====Specialist Groups====		====Specialist Groups====
	Suggested format: the format used for the Sussex Disability Aids Group can be used for other groups: “freegle disability aids” inside the heart and “AreaName” underneath.		''Suggested format'': the format used for the Sussex Disability Aids Group can be used for other groups: “freegle disability aids” inside the heart and “AreaName” underneath.