b3457m0d3 · September 15, 2015 15:06
diff --git a/content b/content
 Design is a broad term used to refer to purpose, planning, or intention that exists or is thought to exist behind an action, fact, or material object.  In the scope of Web Design we have 2 main partitions:

 Front-end – dealing with user interface/interaction design (UX), and graphic design
 Backend – dealing with behind the scenes data-processing software that runs on the server and also handles storage/manipulation of said data in congress with the cues from the front-end
 Programming exists in both sects:

 Front-end programming is rendered in the browser and therefore is both expanded and limited by the browser in use.  This also means that commands are executed even after the page has loaded which lends well to it’s uses: handling user interaction and server communications involving user input along with executing visual-effects.  Backend programming happens in the background, meaning the user never sees it happen.  In fact your backend program is out of the picture by the time the page is loaded, handling things like data collection, access & storage to that data, likely in conjunction with a database of some sort, and general automation (i.e.) page generation).

 The two schools of thought walk right up to line in this case, as the two must work together to accomplish the common task of creating  a usable, and user-friendly user experience. As such, transport formats have of course been developed to smooth out the process, and design patterns have been extensively developed to make the process as painless as possible.
	Design is a broad term used to refer to purpose, planning, or intention that exists or is thought to exist behind an action, fact, or material object. In the scope of Web Design we have 2 main partitions:

	Front-end – dealing with user interface/interaction design (UX), and graphic design
	Backend – dealing with behind the scenes data-processing software that runs on the server and also handles storage/manipulation of said data in congress with the cues from the front-end
	Programming exists in both sects:

	Front-end programming is rendered in the browser and therefore is both expanded and limited by the browser in use. This also means that commands are executed even after the page has loaded which lends well to it’s uses: handling user interaction and server communications involving user input along with executing visual-effects. Backend programming happens in the background, meaning the user never sees it happen. In fact your backend program is out of the picture by the time the page is loaded, handling things like data collection, access & storage to that data, likely in conjunction with a database of some sort, and general automation (i.e.) page generation).

	The two schools of thought walk right up to line in this case, as the two must work together to accomplish the common task of creating a usable, and user-friendly user experience. As such, transport formats have of course been developed to smooth out the process, and design patterns have been extensively developed to make the process as painless as possible.