Added metadata using schema.org to contacts

[ResendeTech]

User description

#489 contacts done

---

PR Type

enhancement, documentation

---

Description

• Added JSON-LD structured data using schema.org to improve SEO for contact pages.
• Implemented conditional logic to handle different page types such as Person and Meeting.
• Enhanced metadata with additional fields like address, events, and members for better search engine understanding.
• Improved HTML formatting for consistency and readability.

---

Changes walkthrough 📝

	Relevant files
Enhancement	contact.html Add schema.org JSON-LD structured data for SEO enhancement contact/templates/contact/contact.html Added JSON-LD structured data using schema.org for SEO. Improved HTML formatting and consistency. Included conditional logic for different page types (Person, Meeting). Enhanced metadata with additional fields like address and events. +88/-45

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 Security concerns Potential XSS vulnerability: The JSON-LD script block (lines 195-259) directly inserts data from the database into the HTML without visible sanitization. If this data is user-generated or comes from an untrusted source, it could potentially be used for cross-site scripting (XSS) attacks. It's crucial to ensure that all data being inserted into the HTML is properly escaped or sanitized, especially when dealing with user-generated content.

⚡ Key issues to review Potential XSS Vulnerability The use of the |safe filter or mark_safe() function is not visible in the provided code, which is good. However, there's still a risk of XSS if the data from the database is not properly sanitized before being inserted into the HTML. Performance Concern The template is making multiple database queries within loops (e.g., for articles, books, library items). This could lead to the N+1 query problem and slow down page load times for contacts with many related items.

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

PR Code Suggestions ✨

Category	Suggestion	Score
Best practice	Apply the 'escape' filter to the description field in JSON-LD to prevent parsing errors Consider using the escape filter for the description field in the JSON-LD script to ensure proper escaping of special characters and prevent potential JSON parsing errors. contact/templates/contact/contact.html [210] -"description": "{{ page.specific.description|striptags }}", +"description": "{{ page.specific.description|striptags|escape }}", Apply this suggestion Suggestion importance[1-10]: 9 Why: Using the 'escape' filter ensures that special characters are properly escaped, preventing potential JSON parsing errors and enhancing data integrity.	9
Possible issue	Add a conditional check for the existence of an image before rendering it Consider adding a conditional check for the existence of book.image before rendering it to prevent potential errors if the image is not available. contact/templates/contact/contact.html [148] -{% image book.image max - 150 x150 class='float-left me-2' %} +{% if book.image %} + {% image book.image max-150x150 class='float-left me-2' %} +{% endif %} Apply this suggestion Suggestion importance[1-10]: 8 Why: Adding a conditional check for the existence of an image before rendering it is a good practice to prevent errors if the image is not available, improving code robustness.	8
Enhancement	Use a character-based truncation filter for more precise text length control Consider using the truncatechars_html filter instead of truncatewords_html for more precise control over the length of the truncated text. contact/templates/contact/contact.html [165] -{{ book.description|richtext|truncatewords_html:30 }} +{{ book.description|richtext|truncatechars_html:200 }} Apply this suggestion Suggestion importance[1-10]: 7 Why: Using 'truncatechars_html' provides more precise control over text length than 'truncatewords_html', which can enhance the presentation of truncated text.	7

💡 Need additional feedback ? start a PR chat