Skip to content

Commit 3ec8e9d

Browse files
committed
Tidy designing.md
1 parent ca037d9 commit 3ec8e9d

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

plone.app.dexterity/designing.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
myst:
33
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"
88
---
99

1010
# Designing with content types
@@ -16,7 +16,7 @@ Plone uses the ZODB, an object database, instead of a relational database as its
1616
The ZODB is well suited to heterogeneous, loosely structured content such as web pages.
1717

1818
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.
2020

2121
Each type has a schema, which is a set of fields with related properties, such as a title, default value, constraints, and so on.
2222
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
2626
For the purpose of this tutorial, we'll build a simple set of types to help conference organizers.
2727
We want to manage a program consisting of multiple sessions.
2828
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.
3030

3131
There are many ways to approach this, but here is one possible design:
3232

33-
- A content type Presenter is used to represent presenter bios.
33+
- A content type Presenter is used to represent presenter biographies.
3434
Fields include name, description, and professional experience.
3535
- A content type Program represents a given conference program.
3636
Besides some basic metadata, it will list the available tracks.

0 commit comments

Comments
 (0)