It's Different with Drupal

Editor's Notes

• #2: Going to talk about the software package Drupal and what the OSC has done with it.
• #3: Going to talk about the software package Drupal and what the OSC has done with it.
• #4: 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.
• #5: 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.
• #6: 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.
• #7: 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.
• #8: 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.
• #9: 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.
• #10: 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.
• #11: 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.
• #12: 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.
• #13: 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.
• #14: 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.
• #15: 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.
• #16: 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.
• #17: 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.
• #18: 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.
• #19: 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.
• #20: 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.
• #21: 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.
• #22: 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.
• #23: 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.
• #24: 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.
• #25: 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.
• #26: 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.
• #27: 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.
• #28: 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.
• #29: 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.
• #30: 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.
• #31: 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.
• #32: 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.
• #33: 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.
• #34: 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.
• #35: 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.
• #36: 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.
• #37: 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.
• #38: 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.
• #39: 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.
• #40: 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.
• #41: 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.
• #42: 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.
• #43: 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.
• #44: 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.
• #45: 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.
• #46: 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.
• #47: 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.
• #48: Themes. Go to Drupal themegarden.
• #49: Themes. Go to Drupal themegarden.