It's Different with Drupal
•Download as KEY, PDF•
0 likes•569 views
Presentation to Tisch Library introducing Drupal as a content management system.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to It's Different with Drupal
Similar to It's Different with Drupal (20)
Recently uploaded
Recently uploaded (20)
It's Different with Drupal
- 2. It’s Different with Drupal
- 3. It’s Different with Drupal Making the Most of Your Web-Based CMS
- 13. The HTML Way Web Server (Apache) Browser Find Page
- 14. The HTML Way Web Server (Apache) Browser Find Page HTML Page
- 15. The HTML Way Web Server (Apache) Load Text Files Load Graphic Files (e.g., CSS) Browser Find Page HTML Page
- 16. The HTML Way Web Server (Apache) Load Text Files Load Graphic Files (e.g., CSS) Browser Find Page HTML Page
- 17. The Drupal Way Server Web Server (Apache) Browser Find Page
- 18. The Drupal Way Server Web Server (Apache) Browser Find Page PHP Programs
- 19. The Drupal Way Server Web Server (Apache) Browser Find Page PHP Programs Graphic & CSS Files
- 20. The Drupal Way Server MySQL Database Web Server (Apache) Browser Find Page PHP Programs Graphic & CSS Files
- 21. The Drupal Way Server MySQL Database Web Server (Apache) Browser Find Page PHP Programs Process PHP Graphic & CSS Files
- 22. The Drupal Way Server MySQL Database Web Server (Apache) Browser Find Page PHP Programs Build HTML Process PHP Page Graphic & CSS Files
- 23. The Drupal Way Server MySQL Database Web Server (Apache) Browser Find Page PHP Programs Build HTML Process PHP Page Graphic & CSS Files
- 24. Research Guide (HTML Page) Research Guide (HTML Page)
- 26. Resource A Resource B Resource C Resource D Resource A Resource B Resource C Resource D
- 27. Resource A Resource B Resource C Resource D Resource A Resource B Resource C Resource D
- 28. Resource A Resource B Resource C Resource D Resource A Resource B Research Guide Research Guide Research Guide (Drupal Node) (Drupal Node) (Drupal Node) Resource C Resource D
- 29. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Research Guide Research Guide Research Guide (Drupal Node) (Drupal Node) (Drupal Node) Resource C Resource D
- 30. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource B Research Guide Research Guide Research Guide (Drupal Node) (Drupal Node) (Drupal Node) Resource C Resource D
- 31. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource B Resource C Resource D
- 32. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource A Resource B Resource B Resource C Resource C Resource D Resource D
- 33. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource A Resource B Resource B Resource C Resource C Resource D Resource D
- 34. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource A Resource B Resource B Resource C Resource C Resource C Resource D Resource D
- 35. MySQL Resource A Database Resource B Resource C Resource D Resource A Resource B Resource C Resource D Resource A Resource A Resource B Resource B Resource C Resource C Resource C Resource C Resource D Resource D
- 36. Drupal Page Region Region Region Region
- 38. Header Region
- 39. Header Region Navbar Region
- 40. Header Region Navbar Region Footer Region
- 41. Header Region Navbar Region Main Content Region Footer Region
- 42. Header Region Navbar Region Left Sidebar Main Content Region Region Footer Region
- 43. Header Region Search Box Navbar Region Left Sidebar Main Content Region Region Footer Region
- 44. Header Region Search Box Navbar Region Left Sidebar Highlights Main Content Region Region Footer Region
- 45. Header Region Search Box Navbar Region Left Sidebar Highlights Main Content Region Region Social Networking Icons Footer Region
- 46. Drupal Page
- 47. Drupal Page block block block block
- 48. Drupal Page block block node block block
- 49. Drupal Page block block Field (e.g., Title) node block block
- 50. Drupal Page block block Field (e.g., Title) Field (e.g., Date) node block block
- 51. Drupal Page block block Field (e.g., Title) Field (e.g., Date) node block Field (e.g., Body) block
- 52. Drupal Page block block Field (e.g., Title) Field (e.g., Date) node block node Field (e.g., Body) block
- 53. Drupal Page block block Field (e.g., Title) Field (e.g., Date) node Field Field block node Field (e.g., Body) Field block
- 55. Expanding Drupal 6 Themes allow you to change the look and feel of your site without modifying the content.
- 56. Expanding Drupal 6 Themes allow you to change the look and feel of your site without modifying the content. Modules extend, enhance, or add new functionality to your site.
- 58. Must-Have Modules CCK. Allows you to create new fields for content.
- 59. Must-Have Modules CCK. Allows you to create new fields for content. Views. Allows you to create displays of selected fields or entire nodes that you can place in regions.
- 61. CCK + Views
- 62. CCK + Views = Awesome
- 63. CCK + Views = Awesome
- 64. Other Key Modules WYSIWYG. A “what you see is what you get” text editor. IMCE. An image/file uploader and browser; also allows you to resize images. Date. A set of tools for dates and calendar functions. Administration Menu. Provides an easier-to-use menu for administrators.
- 65. Beyond the Basics Search Optimization RSS Feeds for Social Networking, Blogging, Podcasting, and more. Webforms OPACs
- 67. Thomas Dodson Coordinator Harvard University Library Office for Scholarly Communication (617) 495 - 4089
Editor's Notes
- Going to talk about the software package Drupal and what the OSC has done with it.
- Going to talk about the software package Drupal and what the OSC has done with it.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Public Website Front-end for our DSPACE open access repository. Internal Wiki (security) Collaborative environment for collection managers and training resource for our student workers. Provides secure webforms for submitting articles, requesting waivers of the policy, applying for funds. Project Management Timesheets for student workers.
- Drupal is a web-based application but functions a little differently than an HTML webpage. HTML Page vs. Drupal Page In a static HTML page, the content is in the actual page: “Welcome to our site,” data is actually in the HTML code of the page. Also, each page was built by a human writing code or using an HTML Editor.
- Drupal is a web-based application but functions a little differently than an HTML webpage. HTML Page vs. Drupal Page In a static HTML page, the content is in the actual page: “Welcome to our site,” data is actually in the HTML code of the page. Also, each page was built by a human writing code or using an HTML Editor.
- Drupal is a web-based application but functions a little differently than an HTML webpage. HTML Page vs. Drupal Page In a static HTML page, the content is in the actual page: “Welcome to our site,” data is actually in the HTML code of the page. Also, each page was built by a human writing code or using an HTML Editor.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- It’s Different with Drupal. PHP Code provides a blueprint, a set of instructions about how to build an HTML page--display the title, then display the date, then the body text, etc. Form w/out Content. PHP is the architect. Content lives in a database as fielded data. PHP has a set of rules about pulling in graphics, which stylesheets to use for this kind of page, what data to grab from the database and how to display it. Web-server is the builder--it follows the instructions given to it by the PHP, the blueprints, and uses the content from MySQL database, the building materials, displays it as an HTML page and sends THAT back to the browser.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- Clearly the drupal structure is more complicated, so why bother? Imagine a research guide built as a static html page. Each of the resources (e.g., a database) have been entered into the individual guide. A new guide listing the same resource requires that information about the resource be duplicated (probably cut and pasted in). Also if, say the name of the resource or the URL or the description of it needs to change you have to find every research guide that has that resource and make the change manually. It’s different with Drupal. Information about each resource is stored as fielded data in a MySQL database. The drupal page looks the same to the user, but since the data about an information resource lives in a database rather than on a page, drupal can re-use the same data on multiple pages. (Resource C). Also, if any of the information needs to be changed, like the URL, that change only needs to be made once and all the pages on which the resource appears will be automatically updated.
- PHP provides a blueprint for building the page: In Drupal, the blueprints involve dividing up each HTML page into regions. You don’t have to use every region, but it offers a lot of flexibility in terms of layout.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- Let’s take a look at the OSC Public Page. Divided into a set of regions, which act as containers or bins into which we can put different kinds of content. Notice how one of these regions, the left sidebar contains different kinds of things--a search box, a couple of new highlights, and social networking icons. These regions are just containers, and what they contain are BLOCKS. More than one Block in the same region.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- One of the terms your going to hear a lot when your talking with drupalers is the word NODE. A Node is the basic unit of content in a drupal site. It’s essentially a collection of fields with content from the database, displayed in a certain way. A node could be the text of an about us page, a blog post, a news article. --Real flexibility of drupal is the ability to make lots of different pages, with different arrangements of blocks and nodes, from the same content. --Show Blocks & Moving Blocks --Show configuring Block. --Content Management --Don’t interface with the database directly (example: About the OSC). Different types of nodes. Highlight vs. Page. (Date vs. No Date). Decide what fields, etc. Nodes can be created, edited, deleted. Same content can be re-used many times, on different pages. Working with Content Types List content, what kind of content Roles--some people can make blog posts, but not main pages. See things or not.
- Themes. Go to Drupal themegarden.
- Themes. Go to Drupal themegarden.