Skip to content
Snippets Groups Projects
Commit 2df9cd91 authored by Tim Wagner's avatar Tim Wagner
Browse files

[TASK] Move always-included property to end of job schema

This ensures the schema is always valid. Otherwise, it could end with a
comma which is seen as invalid schema.
parent 65c21629
No related branches found
No related tags found
1 merge request!20[FEATURE] Extended TCAs for Structured Data (SEO)
......@@ -19,12 +19,6 @@
"validThrough": "{f:format.date(date: job.validThrough, format: 'Y-m-d')}",
</f:if>
"hiringOrganization": {leftBrace}
"@type": "Organization",
"name": "{job.company.name}",
"sameAs": "<f:uri.page pageUid="1" absolute="TRUE"/>",
"logo": "<f:uri.image src="EXT:project_theme/Resources/Public/Images/logo-inverted.svg" absolute="TRUE"/>"
{rightBrace},
<f:if condition="{job.telecommutePossible}">
"jobLocationType": "TELECOMMUTE",
......@@ -42,6 +36,16 @@
{rightBrace},
</f:if>
<f:comment><!--
We need a property that is certainly included to make sure the last property never ends with a comma.
//TODO Use logo and rootPage flexibly so the correct one is always used.
--></f:comment>
"hiringOrganization": {leftBrace}
"@type": "Organization",
"name": "{job.company.name}",
"sameAs": "<f:uri.page pageUid="1" absolute="TRUE"/>",
"logo": "<f:uri.image src="EXT:project_theme/Resources/Public/Images/logo-inverted.svg" absolute="TRUE"/>"
{rightBrace}
{rightBrace}
</script>
</f:alias>
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment