Elite Dangerous Field Manual:Adding an Image - Revision history

Sythan: Neutralize wording around generated/synthetic image guidance

2026-08-22T02:38:10Z

Neutralize wording around generated/synthetic image guidance

← Older revision		Revision as of 02:38, 22 August 2026
Line 1:		Line 1:
	~~How to add a screenshot or original image to an EDFM article.~~

	~~== Current access ==~~
	Uploads are enabled for all registered accounts (PNG/JPEG/WebP, up to 30 MB — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the full rules). Create an account (see [[Special:CreateAccount]]) and use [[Special:Upload]] directly.

	~~== Before uploading ==~~
	Read [[Elite Dangerous Field Manual:Image Use Policy]] in full — in short: only your own original screenshots or diagrams (nothing copied from Fandom, Reddit, Discord, YouTube, other wikis, or "found on Google"), no third-party UI overlays or other players' identifying information without consent, and no AI-generated images presented as real captures.

	~~== Uploading an image ==~~
	~~Go to <code>Special:Upload</code>. EDFM's upload form asks for what it can't safely work out on its own, and generates the rest of the file page automatically:~~

	~~# '''Choose the file.'''~~
	~~# '''Destination filename''' — a clear, descriptive name (it becomes the page title in the File namespace).~~
	# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.
	# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.
	# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "Ship Engineer" vs "Odyssey Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.
	# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.
	~~# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.~~
	~~# '''Additional notes''' — optional freeform field for anything else worth recording.~~

	~~On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl\|EDFM image information}}:~~
	* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an Odyssey Engineer.").
	* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.
	* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.
	* '''captured_by''' — your account name, filled in automatically; you never need to type your own name.
	* '''capture_date''' — included '''only''' if the uploaded file's own metadata contains a genuine capture date. EDFM never substitutes the upload date, and never guesses.
	* '''modifications''' / '''notes''' — only included if you actually filled those optional fields in.
	* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").

	The relevant categories (for example [[:Category:Engineer images]] and [[:Category:Odyssey Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl\|License-ED screenshot}}) are added automatically as well.

	You should not need to write or edit <code>{{tl\|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly\|below]].

	'''Uploading a new version of an existing file''' (replacing the image itself) does not regenerate or overwrite the existing file page's description — your original metadata is left exactly as it was.

	Once uploaded, reference the image on the article as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).

	~~== Advanced: editing a file page directly ==~~
	File pages are ordinary wiki pages. An experienced editor can open a file page and edit its {{tl\|EDFM image information}} fields directly at any time — for example to add a <code>capture_date</code> EDFM couldn't detect, correct a <code>subject_type</code>, or expand on <code>notes</code>. See {{tl\|EDFM image information}}'s own documentation for the full field list.

	~~== Captioning ==~~
	Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|EDFM image information}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.

	~~{{Related articles\|[[Elite Dangerous Field Manual:Image Use Policy]] [[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}~~

EDFM Site Maintenance: Audit remediation: correct stale Frontier OAuth/CAPI status and other outdated wording: uploads are open to all registered accounts, registration is open

2026-08-18T01:06:25Z

Audit remediation: correct stale Frontier OAuth/CAPI status and other outdated wording: uploads are open to all registered accounts, registration is open

← Older revision		Revision as of 01:06, 18 August 2026
Line 2:		Line 2:

	== Current access ==		== Current access ==
	Uploads are ~~technically~~ enabled ~~on EDFM~~ (PNG/JPEG/WebP, up to 30 MB — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the full rules)~~, but the upload right is currently restricted to administrator accounts while public~~ account ~~creation is still closed —~~ see [[~~Elite Dangerous Field Manual~~:~~Current Project Status~~]]. This is not the same as uploads being switched off; it's a temporary access restriction that will lift alongside public registration. If you have content you'd like added, flag it via the article's talk page for now rather than assuming you can upload it yourself.		Uploads are enabled for all registered accounts (PNG/JPEG/WebP, up to 30 MB — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the full rules). Create an account (see [[Special:CreateAccount]]) and use [[Special:Upload]] directly.

	== Before uploading ==		== Before uploading ==

EDFM Maintenance: Restore Ship/Odyssey Engineer image subtype guidance

2026-08-11T03:06:35Z

Restore Ship/Odyssey Engineer image subtype guidance

Maintenance script: Normalize Engineer image metadata wording

2026-08-11T02:50:03Z

Normalize Engineer image metadata wording

← Older revision		Revision as of 02:50, 11 August 2026
Line 28:		Line 28:
	* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").		* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").

	The relevant categories (~~e.g.~~ [[:Category:~~Engineer images]], [[:Category:Odyssey~~ Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl\|License-ED screenshot}}) are added automatically as well.		The relevant categories (for example [[:Category:Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl\|License-ED screenshot}}) are added automatically as well.

	You should not need to write or edit <code>{{tl\|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly\|below]].		You should not need to write or edit <code>{{tl\|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly\|below]].

Maintenance script: Normalize Engineer image metadata wording

2026-08-11T02:49:23Z

Normalize Engineer image metadata wording

← Older revision		Revision as of 02:49, 11 August 2026
Line 14:		Line 14:
	# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.		# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.
	# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.		# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.
	# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "~~Ship Engineer" vs "Odyssey~~ Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.		# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.
	# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.		# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.
	# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.		# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.
Line 20:		Line 20:

	On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl\|EDFM image information}}:		On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl\|EDFM image information}}:
	* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an ~~Odyssey~~ Engineer ~~in Elite Dangerous~~.").		* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an Engineer.").
	* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.		* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.
	* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.		* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.

Sythan: Rewrite for the automated upload workflow: describes the new Media purpose/Subject/Licensing form fields and what EDFM generates automatically, instead of manual template-editing instructions

2026-08-08T15:59:12Z

Rewrite for the automated upload workflow: describes the new Media purpose/Subject/Licensing form fields and what EDFM generates automatically, instead of manual template-editing instructions

@@ Line 7: / Line 7: @@
 Read [[Elite Dangerous Field Manual:Image Use Policy]] in full — in short: only your own original screenshots or diagrams (nothing copied from Fandom, Reddit, Discord, YouTube, other wikis, or "found on Google"), no third-party UI overlays or other players' identifying information without consent, and no AI-generated images presented as real captures.
-== Uploading and using an image ==
+== Uploading an image ==
-# Go to <code>Special:Upload</code>. The description box is pre-filled with an empty {{tl|EDFM image information}} skeleton — fill in the fields that apply and delete any that don't.
+Go to <code>Special:Upload</code>. EDFM's upload form asks for what it can't safely work out on its own, and generates the rest of the file page automatically:
-For anything that isn't an ordinary gameplay screenshot (an original diagram, official Frontier media, something used with permission), pick the matching Licensing option instead, and set <code>media_type</code>/<code>source</code>/<code>copyright_holder</code> accordingly — see [[Elite Dangerous Field Manual:Image Use Policy]] for what each option means.
+# '''Choose the file.'''
 == Captioning ==

Sythan: Update for the new EDFM image information template and upload-form preload

2026-08-08T15:01:24Z

Update for the new EDFM image information template and upload-form preload

← Older revision		Revision as of 15:01, 8 August 2026
Line 8:		Line 8:

	== Uploading and using an image ==		== Uploading and using an image ==
	# Go to <code>Special:Upload</code>.		# Go to <code>Special:Upload</code>. The description box is pre-filled with an empty {{tl\|EDFM image information}} skeleton — fill in the fields that apply and delete any that don't.
	# Give the file a clear, descriptive name (it becomes the page title in the File namespace).		# Give the file a clear, descriptive name (it becomes the page title in the File namespace).
	# Pick a '''Licensing''' option — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options.		# Pick a '''Licensing''' option — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. This is what generates the page's <code>== Licensing ==</code> section automatically — separate from the Summary/metadata below.
	# In the ~~description box, add~~ {{tl\|~~Elite Dangerous screenshot~~}} ~~with the details filled in~~ — for example, a Professor Palin headshot:		# Fill in the preloaded {{tl\|EDFM image information}} — for example, a Professor Palin headshot:
	<pre>		<pre>
	{{~~Elite Dangerous screenshot~~		{{EDFM image information
	\|description = Professor Palin ~~portrait/headshot~~		\|description = In-game portrait of Professor Palin, a Ship Engineer in Elite Dangerous.
	\|subject = Professor Palin		\|subject = [[Professor Palin]]
			\|subject_type = Ship Engineer
			\|source = Elite Dangerous
			\|media_type = Cropped in-game screenshot
	\|captured_by = Your commander name		\|captured_by = Your commander name
	\|~~capture_date~~ = ~~2026-08-08~~		\|modifications = Cropped to portrait framing
	\|~~game_version~~ = ~~Live~~		\|intended_use = Identification and illustration on the Professor Palin article.
	\|~~location~~ = ~~Abel Laboratory, Arque~~		\|copyright_holder = Frontier Developments plc
	}}		}}
	</pre>		</pre>
	This records the useful metadata and ~~automatically includes~~ the ~~Frontier attribution wording~~ — ~~you never need to type out copyright/legal boilerplate by hand~~. Always fill in <code>captured_by</code>; leaving it out visibly flags the file as missing source information rather than defaulting to something generic.		This records the useful provenance/description metadata as its own <code>== Summary ==</code> section — kept deliberately separate from licensing, and separate from the subject's own article (this describes the '''picture''', not the Engineer/ship/place pictured — see [[Elite Dangerous Field Manual:Image Use Policy]]). Always fill in <code>captured_by</code>; leaving it out visibly flags the file as missing source information rather than defaulting to something generic. Only state <code>capture_date</code> or <code>modifications</code> if actually known — leave them out rather than guess.
	# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).		# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).

	For anything that isn't an ordinary gameplay screenshot (an original diagram, official Frontier media, something used with permission), pick the matching Licensing option instead — see [[Elite Dangerous Field Manual:Image Use Policy]] for what each ~~one~~ means.		For anything that isn't an ordinary gameplay screenshot (an original diagram, official Frontier media, something used with permission), pick the matching Licensing option instead, and set <code>media_type</code>/<code>source</code>/<code>copyright_holder</code> accordingly — see [[Elite Dangerous Field Manual:Image Use Policy]] for what each option means.

	== Captioning ==		== Captioning ==
	Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|~~Elite Dangerous screenshot~~}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.		Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|EDFM image information}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.

	{{Related articles\|[[Elite Dangerous Field Manual:Image Use Policy]] [[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}		{{Related articles\|[[Elite Dangerous Field Manual:Image Use Policy]] [[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}

Sythan: Rewrite upload walkthrough for the new Licensing dropdown + Elite Dangerous screenshot template

2026-08-07T23:58:20Z

Rewrite upload walkthrough for the new Licensing dropdown + Elite Dangerous screenshot template

← Older revision		Revision as of 23:58, 7 August 2026
Line 5:		Line 5:

	== Before uploading ==		== Before uploading ==
	Read [[Elite Dangerous Field Manual:~~Screenshot~~ Policy]] in full — in short: only your own original screenshots or diagrams (nothing copied from Fandom or ~~other sites~~), no third-party UI overlays or other players' identifying information without consent.		Read [[Elite Dangerous Field Manual:Image Use Policy]] in full — in short: only your own original screenshots or diagrams (nothing copied from Fandom, Reddit, Discord, YouTube, other wikis, or "found on Google"), no third-party UI overlays or other players' identifying information without consent, and no AI-generated images presented as real captures.

	== Uploading and using an image ==		== Uploading and using an image ==
	# Go to <code>Special:Upload</code>.		# Go to <code>Special:Upload</code>.
	# Give the file a clear, descriptive name (it becomes the page title in the File namespace).		# Give the file a clear, descriptive name (it becomes the page title in the File namespace).
	# In the description box, add {{tl\|~~Screenshot license~~\|captured_by=Your commander name ~~or handle~~}} ~~— this stamps~~ the ~~file page with~~ the ~~standard source/contributor/game~~/~~assets attribution block~~. Always fill in <code>captured_by</code> ~~with the actual uploader's name~~; leaving it out visibly flags the ~~credit~~ as missing rather than defaulting to something generic.		# Pick a '''Licensing''' option — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options.
			# In the description box, add {{tl\|Elite Dangerous screenshot}} with the details filled in — for example, a Professor Palin headshot:
			<pre>
			{{Elite Dangerous screenshot
			\|description = Professor Palin portrait/headshot
			\|subject = Professor Palin
			\|captured_by = Your commander name
			\|capture_date = 2026-08-08
			\|game_version = Live
			\|location = Abel Laboratory, Arque
			}}
			</pre>
			This records the useful metadata and automatically includes the Frontier attribution wording — you never need to type out copyright/legal boilerplate by hand. Always fill in <code>captured_by</code>; leaving it out visibly flags the file as missing source information rather than defaulting to something generic.
	# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).		# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).

			For anything that isn't an ordinary gameplay screenshot (an original diagram, official Frontier media, something used with permission), pick the matching Licensing option instead — see [[Elite Dangerous Field Manual:Image Use Policy]] for what each one means.

	== Captioning ==		== Captioning ==
	Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|~~Screenshot license~~}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.		Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|Elite Dangerous screenshot}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.

	{{Related articles\|[[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}		{{Related articles\|[[Elite Dangerous Field Manual:Image Use Policy]] [[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}

Sythan: Clarify captured_by must be filled in with the real uploader name, not left to default

2026-08-07T23:49:14Z

Clarify captured_by must be filled in with the real uploader name, not left to default

← Older revision		Revision as of 23:49, 7 August 2026
Line 10:		Line 10:
	# Go to <code>Special:Upload</code>.		# Go to <code>Special:Upload</code>.
	# Give the file a clear, descriptive name (it becomes the page title in the File namespace).		# Give the file a clear, descriptive name (it becomes the page title in the File namespace).
	# In the description box, add {{tl\|Screenshot license}} — this stamps the file page with the standard source/contributor/game/assets attribution block~~, so~~ it ~~doesn't need~~ to ~~be typed out by hand each time~~.		# In the description box, add {{tl\|Screenshot license\|captured_by=Your commander name or handle}} — this stamps the file page with the standard source/contributor/game/assets attribution block. Always fill in <code>captured_by</code> with the actual uploader's name; leaving it out visibly flags the credit as missing rather than defaulting to something generic.
	# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).		# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).

Sythan: Add Screenshot license step to the upload walkthrough

2026-08-07T23:46:29Z

Add Screenshot license step to the upload walkthrough

← Older revision		Revision as of 23:46, 7 August 2026
Line 10:		Line 10:
	# Go to <code>Special:Upload</code>.		# Go to <code>Special:Upload</code>.
	# Give the file a clear, descriptive name (it becomes the page title in the File namespace).		# Give the file a clear, descriptive name (it becomes the page title in the File namespace).
	# ~~Add a short~~ description ~~of what's shown~~, ~~when~~, ~~and in what game mode~~.		# In the description box, add {{tl\|Screenshot license}} — this stamps the file page with the standard source/contributor/game/assets attribution block, so it doesn't need to be typed out by hand each time.
	# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).		# On the article, reference it as <code><nowiki>[[File:Name.png\|thumb\|caption]]</nowiki></code>, or pass it as <code>\|image=Name.png</code> to an infobox that supports one (e.g. {{tl\|Engineer infobox}}).

	== Captioning ==		== Captioning ==
	Use {{tl\|Screenshot caption}} for the visible caption text so credit/context is shown consistently rather than as plain prose ~~under~~ the ~~image~~.		Use {{tl\|Screenshot caption}} for the visible caption text under the image on the article page, so credit/context is shown consistently rather than as plain prose. This is separate from {{tl\|Screenshot license}} on the file page itself — see [[Elite Dangerous Field Manual:Screenshot Policy]] for the distinction.

	{{Related articles\|[[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}		{{Related articles\|[[Elite Dangerous Field Manual:Screenshot Policy]] [[Elite Dangerous Field Manual:Contributing]]}}

← Older revision		Revision as of 03:06, 11 August 2026
Line 14:		Line 14:
	# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.		# '''Media purpose''' — what kind of image this is: Engineer portrait, character portrait, ship image, module/equipment image, station/settlement/planet/system image, UI screenshot, gameplay screenshot, diagram/infographic, EDFM-created graphic, or other. This drives the description and categories EDFM generates below.
	# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.		# '''Subject''' — the EDFM article this image is of, typed as plain text (e.g. <code>Hero Ferrari</code>, not <code><nowiki>[[Hero Ferrari]]</nowiki></code>) — start typing and existing page titles will autocomplete. Required for media purposes that have an obvious subject (a portrait, a ship, a specific location); optional for general gameplay screenshots, UI screenshots, and diagrams. If the subject doesn't yet have an EDFM article, it's still recorded, just as plain text rather than a link.
	# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.		# '''Subject type override''' — optional, and normally not needed. For an Engineer portrait, EDFM automatically works out "Ship Engineer" vs "Odyssey Engineer" from the subject's own article (its Engineering-type category) — only use this field if that inference is wrong or the subject's article doesn't exist yet.
	# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.		# '''Licensing''' — for an ordinary gameplay screenshot this is almost always "Elite Dangerous in-game screenshot." See the guidance on the upload page itself, or [[Elite Dangerous Field Manual:Image Use Policy]], for the other options. Your choice here also determines the <code>source</code>, <code>media_type</code>, and (where the license makes it clear) <code>copyright_holder</code> fields below — you don't need to re-enter information the license already establishes.
	# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.		# '''Image modifications''' — optional. Only state something here if you actually know the file has been altered (e.g. "Cropped to portrait framing"); leave it blank rather than guess.
Line 20:		Line 20:

	On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl\|EDFM image information}}:		On submission, EDFM builds the file page's <code>== Summary ==</code> section automatically, using {{tl\|EDFM image information}}:
	* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an Engineer.").		* '''description''' — a short factual sentence built from the media purpose and subject (e.g. "In-game portrait of [[Hero Ferrari]], an Odyssey Engineer.").
	* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.		* '''subject''' / '''subject_type''' — the article you named, linked if it exists, plus its inferred or overridden type.
	* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.		* '''source''' / '''media_type''' / '''copyright_holder''' — derived from your Licensing choice (e.g. "Elite Dangerous, captured in-game" / "In-game screenshot" / "Frontier Developments plc" for an ordinary screenshot). For original work you made yourself, copyright is attributed to you as the creator, not to EDFM.
Line 28:		Line 28:
	* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").		* '''intended_use''' — a short standard sentence built from the media purpose and subject (e.g. "Identification and illustration on the [[Hero Ferrari]] article and related Engineering pages.").

	The relevant categories (for example [[:Category:Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl\|License-ED screenshot}}) are added automatically as well.		The relevant categories (for example [[:Category:Engineer images]] and [[:Category:Odyssey Engineer images]]) and the <code>== Licensing ==</code> section (from your Licensing choice, e.g. {{tl\|License-ED screenshot}}) are added automatically as well.

	You should not need to write or edit <code>{{tl\|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly\|below]].		You should not need to write or edit <code>{{tl\|EDFM image information}}</code> syntax by hand for a normal upload. If something EDFM generated needs correcting, or you want to add detail beyond what the form covers, you can always edit the file page afterwards like any other page on this wiki — see [[#Advanced: editing a file page directly\|below]].