1. 先要懂Region。
2. 然后规划网站的布局，即Prototype / 网站原型Axure
3. 然后是Content Entity（内容实体）
Here is a table of some common content entity types:
|
ENTITY TYPE |
ENTITY SUB-TYPE |
DEFINING MODULE |
MAIN USES |
|
Content item |
Content type |
Node module |
Content intended to be the main page area for pages on the site |
|
|
Example: In the farmers market site example, you might have content types for basic pages, vendor pages, and recipe pages. |
||
|
Comment |
Comment type |
Comment module |
Commentary added to content entities (typically to Content item entities) |
|
|
Example: On a blog site, blog posts might have comments. They are not needed in the farmers market site example. |
||
|
User profile |
(none) |
User module |
Data related to a person with a user account (login access) on the site |
|
|
Example: Every site has at least basic user profiles with user names and email addresses; social networking sites may have more complex user profiles with more information. |
||
|
Custom block |
Block type |
Custom Block module |
Text and images in smaller chunks, often displayed in the site header, footer, or sidebar |
|
|
Example: In the farmers market site example, you might put the hours and location in a sidebar block. |
||
|
Taxonomy term |
Vocabulary |
Taxonomy module |
Used to classify other types of content |
|
|
Example: In the farmers market site example, you might classify Recipe content with an Ingredients taxonomy vocabulary, with taxonomy terms like Carrots and Tomatoes. In a blogging site, blog posts might be classified using a Tags vocabulary, and perhaps also a Categories vocabulary. |
||
|
File |
(none) |
File module |
An image or attachment file that is tracked and managed by the site, often attached to other types of content |
|
|
Example: In the farmers market site example, both Recipe and Vendor pages might have image attachments, which would (behind the scenes) be managed as File entities by the site. |
||
|
Contact form |
Form type |
Contact module |
A form that lets site visitors contact site owners |
|
|
Example: A contact form is needed in the farmers market site example. |
||
4. 还没完，然后是Fields： Within entity items, the data is stored in individual fields, each of which holds one type of data, such as formatted or plain text, images or other files, or dates. Field types can be defined by the core software or by modules.
* 注意：学会“调用”的思想。因为数据存储在数据库，就不要直接去单独编辑整个页面，而要学会反复使用content modular.
5. 规划网站结构。例如：
Here’s an example of the resulting content structure for the farmers market scenario example site:
|
ENTITY TYPE |
ENTITY SUB-TYPE |
EXAMPLES |
FIELDS |
|
Content item |
Basic page |
Home page, about page |
Title, page body |
|
Content item |
Vendor |
A page for each vendor at the market |
Vendor name, page body, image, URL |
|
Content item |
Recipe |
A page for each submitted recipe |
Recipe name, page body, image, reference to Vendor who submitted it, Ingredients taxonomy |
|
Custom block |
(generic) |
Copyright notice for footer, Hours and location for sidebar |
No special fields |
|
Taxonomy term |
Ingredients |
Carrots, tomatoes, and other recipe ingredients |
No special fields |
|
Contact form |
(generic) |
Generic contact form |
Name, email, subject, message |
|
User profile |
(none) |
Will not be displayed on site |
No special fields |
And here are the listings the site needs:
|
PAGE OR PAGE AREA |
ENTITY TYPE AND SUB-TYPE |
FILTER/SORT/PAGINATION |
FIELDS DISPLAYED |
|
Vendors page |
Vendor content items |
All vendors, alphabetical, paged |
Image, vendor name, trimmed body |
|
Recipes page |
Recipe content items |
Filter by ingredients, alphabetical, paged |
Image, recipe name |
|
Recent recipes sidebar |
Recipe content items |
List 5 most recent |
Image, recipe name |
*注意： 基于角色的”编辑工作流“概念。
An editorial workflow is the process organizations follow to create, review, edit, and publish content. Multiple people in different roles in the organization can be part of the process.
这些工作流常见的：published / unpublished status; revision tracking; workflows； block placement.
6. 翻译（略）