This document discusses using semantic data in TYPO3. It begins by defining semantic data and explaining why the presenter focuses on this topic based on his experience. The document then looks at approaches to semantic data in the past in TYPO3 and what can now be done to improve it, such as defining content types and customizing elements. It outlines a wish list for further enhancing semantic data in the future. In the end, it emphasizes giving all data meaning, leveraging TYPO3's existing capabilities, and focusing on reuse and optimization.
Presentation on how to chat with PDF using ChatGPT code interpreter
Semantic data in TYPO3 - T3CON18EU
1. THERE IS MORE THAN PAGES,
CONTENT AND RECORDS IN THE
WORLD.
SEMANTIC DATA IN TYPO3
SEBASTIAN HELZLE - T3CON 2018
2. SEMANTIC DATA IN TYPO3 - INTRODUCTION
ABOUT ME
▸Consultant for web development & agile
▸Many years of TYPO3, Neos CMS, Scrum experience
▸Neos core team member
▸@home in
Karlsruhe & Cambodia
▸Hiker & baker
▸@sebobo
3. SEMANTIC DATA IN TYPO3 - INTRODUCTION
AGENDA
▸Target audience for this talk
▸Why do I talk about this
▸A look into the past & present
▸What you can do now
▸Wishlist for the future
▸Summary
▸Time for questions
10. SEMANTIC DATA IN TYPO3 - WHY DO I TALK ABOUT THIS TOPIC
„It is a conceptual data model in which
semantic information is included. This
means that the model describes the
meaning of its instances.“
https://en.wikipedia.org/wiki/Semantic_data_model
11. SEMANTIC DATA IN TYPO3 - WHY DO I TALK ABOUT THIS TOPIC
https://en.wikipedia.org/wiki/Semantic_data_model
„It is a conceptual data model that
includes the capability to express
information that enables other parties to
interpret meaning (semantics) from the
instances, without the need to know the
meta-model.“
29. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Create a content architecture.
Text & Image
Employee
Quote
Banner
Form
Blogpost
Productpage
30. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Optimize overlapping
definitions and connections.
A
B
31. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Define a user specific
vocabulary with the customer.
32. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
USER SPECIFIC VOCABULARY EXAMPLES
▸„Banner“ OR „Carousel“ OR „Slider“
▸„Teaser“ OR „Related Content“
▸„Landingpage“ OR „Subhomepage“ OR „Divison Homepage“
33. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Adapt labels according to
the projects vocabulary:
„Header“ OR „Title“ OR „Leadtext“?
34. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Create the content elements you need
and disable the rest.
35. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Use schema.org when thinking about
internal field names and their necessity.
36. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Example:
Quotation content
37. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Render microdata and make search
engines happy:
https://developers.google.com/search/docs/guides/search-gallery
38. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Reuse microdata in Javascript to create
interactivity.
39. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
If something
behaves like a page,
it should be a page.
40. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Pages get URLs for
free and appear
in sitemaps.
41. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Pages are part
of the page tree
and can be
easily found.
42. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Pages can be
edited like a page!
🤯
43. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
But also in
list mode.
44. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Page types (or Doctypes)
can be customized
according to the
projects needs.
45. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Page types can be
easily identified in
the database and
loaded via
repositories.
46. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Pages can be
rendered without
plugins.
47. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Permissions can be
fine tuned for
different page types.
48. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Search results for
pages can be rendered
depending on the
their type.
49. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Pages can have
meaningful icons.
50. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Use category folders
instead of long lists.
51. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Disable
everything that’s
not necessary.
52. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Adapt the position and grouping of properties
according to the desired workflow.
53. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Example:
Combine fields that are needed 95%
of the time into one tab.
54. SEMANTIC DATA IN TYPO3 - WHAT YOU CAN DO NOW
Example:
Editor uses copy & paste from word
→ order fields according to their documents
* Do long-term support for a project
* simplify their own future work
* easier onboarding for other devs
* Help editors
Who wonder if their work in TYPO3 could be easier
Who work in teams and have to onboard others
Who enjoy better usability
Who are unhappy with the technical debts of older projects
Who want to learn more about the capabilities of TYPO3
Who want to create customer centric solutions with great usability
* Depends
Low overall satisfaction
Might cost you the next project
Bad for community
Great customer feedback
Less support needed
Developers appreciated advantages of those ideas after initial doubts
And the editors didn’t have to change anything
Not possible to easily see for an editor
Hard to debug
* Not much fun with SEO adjustments, caching, search, url generation -> needs lot of glue code
First it’s fast and then it’s a pain
7 years ago it felt smart, now it’s hard to separate it again with thousands of records
* More like a coincidence than semantics
This will break apart
Wouldn’t it be nice if the structure, naming & meaning already give you enough hints?
Each type of content is defined with the customer and the team
Focus on the minimum
Discuss & document use cases
If two similar types of author elements come up, maybe only one is needed.
When in doubt -> still remove or disable
Create glossary if needed
Also for localization!
Prevent multiple meanings!
Enforce vocabulary in ticket system too!
Reduces onboarding time for new editors
Reduces confusion during discussions
Technical: prefer flexforms to using real fields -> more flexibility, database doesn’t care, support in TS getting better, not as good for querying
No need for many default elements
It’s reusable later
List views, selectors, etc…
Simplifies SEO, Metadata, Backend handling,
No matter whether from Realurl or TYPO3 9 LTS
Simple records can not be edited like a page
Customers want to customize their record based articles -> sorry complicated
Much easier to understand what your looking at and find wrong documents
Gives additional semantic data later on for category selectors etc…
Could have even more levels depending on amount of pages and subcategories like year or month
Categories can be hidden in the url or behave as aggregations or redirect to a filter page with a preset
When in doubt -> still remove or disable
Regularly check with the customer in a workshop or via screen sharing what is used and in which way
Reduces onboarding time for new editors
Reduces number of clicks and time needed for new content
* Often content types are reused with different meanings because of high cost of implementation
No adding to multiple array to support SOLR etc…
No defining of numbered IDs in range of 255 -> makes it hard to create extensions with doctypes
Hard to identify as one entity via the database or other methods
Combine the text into one semantic container and give it meaning