ARK2/Frontend - Revision history

John Layt: /* Scripts */

2018-04-16T14:34:07Z

‎Scripts

2018-04-16T13:56:22Z

‎Templates

2018-04-16T13:30:47Z

‎Build

2018-04-16T13:22:26Z

‎Useful References

2018-04-16T13:21:32Z

‎Templates

2018-04-16T13:13:45Z

‎Templates

2018-04-16T13:10:50Z

‎Linking

2018-04-16T13:09:36Z

‎Templates

2018-04-16T12:01:54Z

‎Linking

2018-04-16T11:42:13Z

‎Linking

@@ Line 393: / Line 393: @@
 == Scripts ==
-Javascript in ARK2 is not well defined as yet beyond the use of jQuery and various Bootstrap-based widgets.
+The use of Javascript in ARK2 is not very well defined or organised as yet beyond the use of jQuery and various Bootstrap-based widgets.
 == Styles ==

@@ Line 390: / Line 390: @@
 * framework/page.html.twig - Extends doc.html.twig and defines the full default set of blocks to use for styles, head, body, and scripts, includes other default blocks used by those blocks such as navbar, but excludes the content block to be used
 * pages/<page>.html.twig - Extends framework/page.html.twig to set the content block to be used by a page, and overrides any standard blocks with custom blocks to be used, e.g. override the standard styles or navbar blocks on this page. This is the root template rendered by a page view.
 == Useful References ==

← Older revision		Revision as of 13:30, 16 April 2018
Line 143:		Line 143:

	npm doctor		npm doctor
		+
		+	To install a new node package to use in the frontend, run:
		+
		+	npm install <package>

	To build a frontend run the frontend command with the name of the frontend:		To build a frontend run the frontend command with the name of the frontend:

← Older revision		Revision as of 13:22, 16 April 2018
Line 389:		Line 389:
	== Useful References ==		== Useful References ==

		+	* https://symfony.com/doc/3.4/form/form_customization.html
		+	* https://symfony.com/doc/3.4/reference/forms/twig_reference.html
	* http://www.helloerik.com/the-subtle-magic-behind-why-the-bootstrap-3-grid-works		* http://www.helloerik.com/the-subtle-magic-behind-why-the-bootstrap-3-grid-works

@@ Line 385: / Line 385: @@
 * framework/doc.html.twig - Skeleton of the HTML5 document, includes undefined blocks for styles, head, body and scripts
 * framework/page.html.twig - Extends doc.html.twig and defines the full default set of blocks to use for styles, head, body, and scripts, includes other default blocks used by those blocks such as navbar, but excludes the content block to be used
-* pages/<page>.html.twig - Extends framework/page.html.twig to set the content block to be used, and overrides any standard blocks with custom blocks to be used, e.g. override the standard styles or navbar blocks on this page
+* pages/<page>.html.twig - Extends framework/page.html.twig to set the content block to be used by a page, and overrides any standard blocks with custom blocks to be used, e.g. override the standard styles or navbar blocks on this page. This is the root template rendered by a page view.
 == Useful References ==
 * http://www.helloerik.com/the-subtle-magic-behind-why-the-bootstrap-3-grid-works

@@ Line 357: / Line 357: @@
       |- layouts/
-* blocks - Small chunks of twig code designed to reused and repeated use Twig Block import and inheritance, e.g. form fields, widgets, etc.
+* blocks - Small chunks of twig code designed to be reused and repeated using Twig Block inheritance, e.g. form fields, widgets, etc.
 * layouts - Arrangements of blocks into generic or task specific layouts, e.g. grids, tables, custom content views, etc.
 * pages - Definitions of the sets of standard blocks to use when building the HTML document for a particular page

@@ Line 342: / Line 342: @@
 == Templates ==
-Twig template resources are organised using a convention to make dynamic mixing of templates to create views possible.
+Twig template resources are organised using a convention to make dynamic mixing of templates to create many different Views possible.
 The twig folder for a frontend is organised as follows:
 == Linking ==

← Older revision		Revision as of 12:01, 16 April 2018
Line 339:		Line 339:

	The defining of streams within each target allows for the mixing of SASS and CSS source in a defined order so the cascading of stylesheets is applied in the correct order		The defining of streams within each target allows for the mixing of SASS and CSS source in a defined order so the cascading of stylesheets is applied in the correct order
		+
		+	== Templates ==
		+
		+	Twig template resources are organised using a convention to make dynamic mixing of templates to create views possible.
		+
		+	The twig folder for a frontend is organised as follows:
		+
		+

	== Linking ==		== Linking ==

@@ Line 342: / Line 342: @@
 == Linking ==
-The front-end is built from the source resource files in the 'build/' folder and installed in the 'src/' folder. The individual site folders then symlink to the required front-end in 'src/', or copy if they wish to edit in place.
+The front-end is built from the source resource files in the 'build/' folder and installed in the 'src/' folder. The individual site folders then symlink to the required front-end in 'src/'.
-To clone the build resources for a new front end from the Core front-end, run the create command. You must provide a name for your new front end, and the source code Namespace it will use, e.g. ARK, Wibble, or Foo. Only use the ARK namespace if the front end is intended for the main ARK project. This Namespace will be remembered by the system.
+To clone the build resources for a new front end from another front-end, run the frontend:create command. You must provide a name for your new front end, and the source code Namespace it will use, e.g. ARK, Wibble, or Foo. Only use the ARK namespace if the front end is intended for the main ARK project. This Namespace will be remembered by the system.
    ./build frontend:create <namespace> <frontend>