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
{{ message }}
Repository navigation
Commit 4518645
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: faqs/textpattern-semantic-model.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,12 +3,12 @@ layout: document
3
3
category: FAQs
4
4
published: true
5
5
title: "The Textpattern semantic model"
6
-
description: The system's six primary building blocks that make it possible to create and manage your site's structure, content and presentation.
6
+
description: The system's primary building blocks that make it possible to create and manage your site's structure, content and presentation.
7
7
---
8
8
9
9
# The Textpattern semantic model
10
10
11
-
When we talk about Textpattern's semantic model, we're talking about the system's six primary building blocks that make it possible to create and manage your site's structure, content and presentation easily. All it takes is getting familiar with the blocks, and how they are associated to one another, which is what this page overviews.
11
+
When we talk about Textpattern's semantic model, we're talking about the system's primary building blocks that make it possible to create and manage your site's structure, content and presentation easily. All it takes is getting familiar with the blocks, and how they are associated to one another, which is what this page overviews.
12
12
13
13
## Semantic model building blocks
14
14
@@ -22,26 +22,30 @@ Pages and Styles (described next) are associated to Sections to provide an HTML
22
22
23
23
### Pages
24
24
25
-
[Pages](/administration/pages-panel) are essentially HTML templates to which all content is added, usually as a combination of standard HTML and Textpattern Tags. As mentioned, Pages must be assigned to Sections, which is how a given section of your website receives the web template it will use.
25
+
[Pages](/administration/pages-panel) are essentially HTML templates to which all content is added, usually as standard HTML (for the static framework) into which [Textpattern Tags](/tags/) are used to insert dynamic content from the database. Pages must be assigned to Sections, which is how a given section of your website receives the web template it will use.
26
26
27
27
### Styles
28
28
29
-
[Styles](/administration/styles-panel) are the CSS style sheets that define the presentational layer of your web content. Like Pages, Styles are associated to Sections. A single Style can be associated to all Sections you create, or each Section can have it's own Style, depending on your website design objectives.
29
+
[Styles](/administration/styles-panel) are the CSS style sheets that define the presentational layer of your web content. Like Pages, Styles are associated to Sections. A single Style can be associated to all Sections you create, or each Section can have its own Style, depending on your website design objectives.
30
30
31
31
**Note:** Like all building blocks described on this page, Textpattern manages Styles in the database by default, not as files on the web server. However, you are not forced to manage your style sheets this way. e.g. you could still link your flat CSS files in the @<head>@ of a Page template in the standard way.
32
32
33
33
### Forms
34
34
35
-
[Forms](/administration/forms-panel), conceptually speaking, are like PHP includes or any other kind of code insertion process you may be aware of that enables you to create a predefined chunk of content once and reuse it in multiple places. In fact, Forms can be used in a variety of ways, including nesting Form templates within each other.
35
+
[Forms](/administration/forms-panel)are like 'includes' or 'snippets' of content. They enable you to create a predefined chunk of content once, and reuse it in multiple places, to ease the maintenance overhead of your website, and to facilitate easier future changes. Forms can be used in a variety of ways, including nesting Form templates within each other.
36
36
37
37
### Tags
38
38
39
-
[Tags](/tags/) are Textpattern's own type of markup syntax that work interchangeably with HTML. There is a variety of Tag types, all of which provide a seemingly infinite number of ways to construct website architecture and content publishing behaviour. Not the least of which, Tags are the means for positioning and inserting Form content into your various Page template locations. The more you learn about Textpattern's Tags, the more adept at using Textpattern you will become.
39
+
[Tags](/tags/) are Textpattern's own type of markup syntax that work interchangeably with HTML. Tags provide many ways to construct website architecture and govern content publishing behaviour. Their primary use is for positioning and inserting Form content into your various Page template locations. The more you learn about Textpattern's Tags, the more adept at using Textpattern you will become.
40
40
41
41
### Categories
42
42
43
43
[Categories](/administration/categories-panel) are a method of organizing content (articles, images, files, links) by particular topics to which the content relates. The category associations with content can then be used to create various content outputs in the website.
44
44
45
+
### Themes
46
+
47
+
[Themes(/build/themes-creating-using-and-sharing)] are a combination of Pages, Styles and Forms (and optional other files), bundled into a shareable zip file that other users can install. They are also the primary mechanism by which you can seamlessly update your live site's look and feel in safety. You can clone your current theme into a _development lane_, work on it and refine it (only you can see the changes when logged in), then publish it to the _live lane_ when you're happy.
48
+
45
49
## Theoretical example for example.org
46
50
47
51
Let's walkthrough the creation and assembly of the building blocks for a hypothetical website called 'Example Organization' (`example.org`)…
0 commit comments