Site:Frontend:BuildingBlocks - Revision history

TonyR: /* Example: Create a Page Include */

2012-07-03T18:39:47Z

‎Example: Create a Page Include

2012-07-01T20:23:15Z

2011-10-02T00:17:12Z

‎Accounts

2011-10-01T22:59:39Z

2011-10-01T19:09:48Z

‎Static Resources

2011-10-01T19:00:40Z

‎Page Include

2011-10-01T19:00:15Z

‎CSS File

2011-10-01T18:59:54Z

2011-10-01T18:44:41Z

2011-10-01T18:26:08Z

‎Pages

@@ Line 47: / Line 47: @@
   </head>
   <body>
-    <?cs evar:MS.site.pageinclude["header"] ?>
+    <!ms:include value="header"!>
   </body>
   </html>

← Older revision		Revision as of 00:17, 2 October 2011
Line 178:		Line 178:

	Accounts are typically used for featured profiles on your website. These normally consist of cast from a movie, directors, producers, etc. Accounts can be considered a global user, because they can appear across multiple sites. Accounts also have the ability to login to a site, so it is possible for your feature profiles to interact with your site members.		Accounts are typically used for featured profiles on your website. These normally consist of cast from a movie, directors, producers, etc. Accounts can be considered a global user, because they can appear across multiple sites. Accounts also have the ability to login to a site, so it is possible for your feature profiles to interact with your site members.
		+
		+	Accounts are sometimes referred to as owners. This is due to legacy terminology. They both mean the same thing.

	== Users ==		== Users ==

← Older revision		Revision as of 22:59, 1 October 2011
Line 174:		Line 174:
	height: <!PROGRESS_BAR_HEIGHT!>px;		height: <!PROGRESS_BAR_HEIGHT!>px;
	}		}
		+
		+	== Accounts ==
		+
		+	Accounts are typically used for featured profiles on your website. These normally consist of cast from a movie, directors, producers, etc. Accounts can be considered a global user, because they can appear across multiple sites. Accounts also have the ability to login to a site, so it is possible for your feature profiles to interact with your site members.
		+
		+	== Users ==
		+
		+	Users belong to your site. Depending on the type of site you have, they can have profiles and resell content just like Accounts do. Sites can be grouped together so they same user account works across multiple sites.
		+
		+	== Content ==
		+
		+	Content belongs to either an account or a user. Content can range from a wide variety of items, such as: videos, photos, blogs, news, products, inventory, events, songs, albums, and objects.

@@ Line 53: / Line 53: @@
 == Static Resources ==
-Each site has an upload system with the easy Metrixstream drag&drop uploader. This is intended to offer a
+Each site allows you to upload files. This is intended to offer a
-storage location for all of your images, style sheets, javascript, etc.
+storage location for all of your images, style sheets, javascript, etc. Images can be uploaded into the site uploader or into a module uploader.
 The benefit of using the integrated static resource system, is that you don't need to worry about all of the complicated

@@ Line 150: / Line 150: @@
 === Page Include ===
   <div id="progressbar">
     <div class="inner"><div>
-  </div>
+  </div></nowiki>
 === JavaScript File ===

@@ Line 167: / Line 167: @@
     background-color: white;
+  }
-−
   #progressbar .inner {
     background-color: red;

← Older revision		Revision as of 18:59, 1 October 2011
Line 132:		Line 132:
	</body>		</body>
	</html>		</html>
		+
		+	== Modules ==
		+
		+	A module groups together a page include, static resources, and variable constants. Modules really help keep your functionality organized. You also have the ability to export modules into a self contained zip file, which you can then import into another site of yours.
		+
		+	The page include portion of the module allows you to create your module's HTML structure.
		+
		+	The variable constants are extremely powerful, because they allow you to share information between your page include and your static resources. This means that your static resources get interpreted on the fly and outputted with the appropriate variable substitution.
		+
		+	Here is an example of a basic progress bar that can be controlled via javascript. (This example uses jQuery.)
		+
		+	=== Variable Constants ===
		+
		+	PROGRESS_BAR_WIDTH = 500
		+	PROGRESS_BAR_HEIGHT = 20
		+
		+	=== Page Include ===
		+
		+	<div id="progressbar">
		+	<div class="inner"><div>
		+	</div>
		+
		+	=== JavaScript File ===
		+
		+	function setProgressBar(percentage) {
		+	$("#progressbar .inner").css("width", Math.floor(<!PROGRESS_BAR_WIDTH!> * percentage * 100) + "px");
		+	}
		+
		+	=== CSS File ===
		+
		+	#progressbar {
		+	width: <!PROGRESS_BAR_WIDTH!>px;
		+	height: <!PROGRESS_BAR_HEIGHT!>px;
		+	background-color: white;
		+	}
		+
		+	#progressbar .inner {
		+	background-color: red;
		+	width: 0px;
		+	height: <!PROGRESS_BAR_HEIGHT!>px;
		+	}

@@ Line 21: / Line 21: @@
   <body>
     HELLO WORLD
   </body>
   </html>

@@ Line 5: / Line 5: @@
 == Pages ==
-Pages are the most basic requirement for building a site. A page consists of the HTML necessary to display your page. Pages have the ability to reference the template engine, but this is entirely optional.
+Pages are the most basic component for building a site. A page is referenced from a URL. If you create a page titled "hello", then you would access it by navigating to http://www.example.com/?page=hello.
 === Example: Create a "Hello World" page ===