Difference between revisions of "Week Five (MGDP2060)"

From Wiki @ Karl Jones dot com
Jump to: navigation, search
(Replaced content with "This article lists topics for '''Week Five''' of '''Web Design and Development III (MGDP2060)'''. Category:Web Design and Development III (MGDP2060)")
Line 1: Line 1:
 
This article lists topics for '''Week Five''' of '''[[Web Design and Development III (MGDP2060)]]'''.
 
This article lists topics for '''Week Five''' of '''[[Web Design and Development III (MGDP2060)]]'''.
 
* '''Topics''':  [[Chapter Five (WordPress: The Missing Manual)]]
 
* '''Exercises''': [[Week Five Exercises (MGDP2060)]]
 
* '''Reading''':
 
** For next week: [[Chapter Thirteen (WordPress: The Missing Manual)|Chapter 13 - Child Themes]]
 
** For week after: [[Chapter Fourteen (WordPress: The Missing Manual)|Chapter 14 - Custom Themes]]
 
 
== WordPress databases gone ==
 
 
WordPress databases from last week were wiped by DeepFreeze.
 
 
Instructor will have WordPress pre-installed on all workstations for next week.
 
 
== In the News ==
 
 
=== Copyright bots ===
 
 
* [http://boingboing.net/2015/09/08/inept-copyright-bot-sends-2600.html Inept copyright bot sends 2600 a legal threat over ink blotches] @ [[BoingBoing]]
 
 
See [[Bot|Bots]].
 
 
=== Bounty for iPhone Hacks ===
 
 
* [http://www.wired.com/2015/09/spy-agency-contractor-puts-1m-bounty-iphone-hack/ Spy Agency Contractor Puts Out a $1M Bounty for an iPhone Hack] @ Wired.com
 
 
== Fingerprints stolen ==
 
 
* [https://www.washingtonpost.com/news/the-switch/wp/2015/09/23/opm-now-says-more-than-five-million-fingerprints-compromised-in-breaches/ OPM says 5.6 million fingerprints stolen in cyberattack]
 
 
=== IPFS: replacement for HTTP ===
 
 
* [https://ipfs.io/ipfs/QmNhFJjGcMPqpuYfxL62VVB9528NXqDNMFXiqN5bgFYiZ1/its-time-for-the-permanent-web.html HTTP is obsolete. It's time for the distributed, permanent web] - "[[Neocities]] has collaborated with [[Protocol Labs]] to become the first major site to implement IPFS in production. Starting today, all Neocities web sites are available for viewing, archiving, and hosting by any IPFS node in the world. "
 
** See [https://ipfs.io/ ipfs.io]
 
 
Wikipedia:
 
 
* [https://en.wikipedia.org/wiki/InterPlanetary_File_System InterPlanetary File System]
 
** "InterPlanetary File System (IPFS), also called "The Permanent Web", is a hypermedia distribution protocol, addressed by content and identities. IPFS enables the creation of completely distributed applications. It aims to make the web faster, safer, and more open."
 
 
== Comic of the Week ==
 
 
Source: [http://xkcd.com/1579/ Tech Loops] @ [[xkcd]]
 
 
http://karljones.com/karljones.com/images/wiki/tech_loops.png
 
 
== Libraries ==
 
 
Note the multiple instances of "[[Library (computing)|Library]]".  This is a bad sign. 
 
 
Using libraries is like grinding fresh pepper on your food: a little tastes good, but a lot tastes bad.
 
 
== Solution stacks ==
 
 
[[Solution stack|Solution stacks]] can be part of problem, because a "stack" is made up two or more separate applications.
 
 
The purpose of the stack is to "bundle up" the separate applications into a single application, the stack.
 
 
Solution stacks are useful, powerful tools.
 
 
But they add [[complexity]] -- and where you have complexity, you have side-effects, synergies, unpredictability, vulnerability.
 
 
== LAMP architecture ==
 
 
In [[computer science]], ''architecture'' is a broad term for internal [[structure]].
 
 
For a diagram of the LAMP, which also represents the [[client-server model]], see [[LAMP_(software_bundle)#LAMP_architecture LAMP architecture]].
 
 
 
== Chapter Five: Themes and Templates ==
 
 
See [[Chapter Five (WordPress: The Missing Manual)]].
 
 
 
=== Theme files ===
 
 
Each theme must contain two specific files:
 
 
* <code>style.css</code> - the stylesheet for this Theme
 
* <code>index.php</code> - the primary Template file
 
 
== Theme Stylesheets ==
 
 
Each Theme requires a stylesheet named <code>style.css</code>.
 
 
<code>style.css</code> functions like any other stylesheet, providing [[Cascading Style Sheets|CSS] rules for the site.
 
 
But in addition, <code>style.css</code> contains information which WordPress uses to identify the stylesheet, and the folder which contains it, as WordPress Themes.
 
 
* The Theme information, which uses a standard format, goes inside a [[CSS comment block]].
 
 
WordPress can read the contents of the <code>style.css</code>, so it knows what Theme the stylesheet represents.
 
 
This happens on the web server, and has nothing to do with the web browsers.  CSS comments are ignored by web browsers.
 
 
== Theme Templates ==
 
 
Templates are individual PHP files within a WordPress Theme.
 
 
Each theme must have a template named <code>index.php</code>.
 
 
* Other templates are optional, but commonly used.
 
 
Templates have specific file names, each of which handles a specific pages, or set of pages, within WordPress.
 
 
Template files are where you write the HTML and PHP which WordPress will display as web pages.
 
 
== include statement ==
 
 
include is a PHP statement which allows you to include one PHP page inside another page.
 
 
This technique is useful for assembling a single page from fragments.
 
 
See:
 
 
http://php.net/manual/en/function.include.php
 
 
http://www.w3schools.com/php/php_includes.asp.
 
 
== Exercises ==
 
 
* [[Week Five Exercises (MGDP2060)]]
 
 
== Reading for next two weeks ==
 
 
Reading for next week: [[Chapter Thirteen (WordPress: The Missing Manual)|Chapter 13 - Child Themes]]
 
 
Reading for week after: [[Chapter Fourteen (WordPress: The Missing Manual)|Chapter 14 - Custom Themes]]
 
 
== See also ==
 
 
* [[Web Design and Development III (MGDP2060)]]
 
  
  
 
[[Category:Web Design and Development III (MGDP2060)]]
 
[[Category:Web Design and Development III (MGDP2060)]]

Revision as of 10:35, 20 August 2016

This article lists topics for Week Five of Web Design and Development III (MGDP2060).