You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: plone.app.dexterity/designing.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
2
myst:
3
3
html_meta:
4
-
"description": ""
5
-
"property=og:description": ""
6
-
"property=og:title": ""
7
-
"keywords": ""
4
+
"description": "Designing with content types in Plone"
5
+
"property=og:description": "Designing with content types in Plone"
6
+
"property=og:title": "Designing with content types in Plone"
7
+
"keywords": "Plone, designing, content types"
8
8
---
9
9
10
10
# Designing with content types
@@ -16,7 +16,7 @@ Plone uses the ZODB, an object database, instead of a relational database as its
16
16
The ZODB is well suited to heterogeneous, loosely structured content such as web pages.
17
17
18
18
Types in Plone are either containers or items (this distinction is sometimes called folderish versus non-folderish).
19
-
A one-to-many type relationship is typically modelled as a container (the "one") containing many items (the "many"), although it is also possible to use references across the content hierarchy.
19
+
A one-to-many type relationship is typically modeled as a container (the "one") containing many items (the "many"), although it is also possible to use references across the content hierarchy.
20
20
21
21
Each type has a schema, which is a set of fields with related properties, such as a title, default value, constraints, and so on.
22
22
The schema is used to generate forms and describe instances of the type.
@@ -26,11 +26,11 @@ When we attempt to solve a particular content management problem with Plone, we
26
26
For the purpose of this tutorial, we'll build a simple set of types to help conference organizers.
27
27
We want to manage a program consisting of multiple sessions.
28
28
Each session should be listed against a track, and have a time slot, a title, a description, and a presenter.
29
-
We also want to manage bios for presenters.
29
+
We also want to manage biographies for presenters.
30
30
31
31
There are many ways to approach this, but here is one possible design:
32
32
33
-
- A content type Presenter is used to represent presenter bios.
33
+
- A content type Presenter is used to represent presenter biographies.
34
34
Fields include name, description, and professional experience.
35
35
- A content type Program represents a given conference program.
36
36
Besides some basic metadata, it will list the available tracks.
0 commit comments