Upsection - Revision history

Dereckson at 00:31, 17 November 2024

2024-11-17T00:31:17Z

@@ Line 1: / Line 1: @@
-=== Upsection ===
+'''Upsection''' allows to deploy our static sites builder.
 We need to maintain dependencies for the Gulp/handlebars site builder
 across several repositories. The dependencies are brittle, security issues
@@ Line 39: / Line 52: @@
 ** HTML from handlebars templates
 ** YAML for data

MoustaphaAs: Removed redirect to Static sites

2024-10-31T20:31:10Z

Removed redirect to Static sites

← Older revision		Revision as of 20:31, 31 October 2024
Line 1:		Line 1:
	~~#REDIRECT [[Static sites]]~~
	=== Upsection ===		=== Upsection ===
	We need to maintain dependencies for the Gulp/handlebars site builder		We need to maintain dependencies for the Gulp/handlebars site builder

MoustaphaAs at 20:24, 31 October 2024

2024-10-31T20:24:42Z

← Older revision		Revision as of 20:24, 31 October 2024
Line 1:		Line 1:
	#REDIRECT [[Static sites]]		#REDIRECT [[Static sites]]
			=== Upsection ===
			We need to maintain dependencies for the Gulp/handlebars site builder
			across several repositories. The dependencies are brittle, security issues
			will require to upgrade to a version of a package invoked by gulp-<feature>,
			but gulp-<feature> will be abandoned and unmaintained. That's the usual
			scenario. When it's maintained, the way to load the library in JS has changed.

			That hard maintenance problem requires an unified solution, to be able to do it
			one for all the sites. '''Upsection''' is the name of this ongoing effort to
			maintain, and provide a tool to populate the dependencies and build the site
			with a simple `make`. Proof of concept lives in {{repo\|upsection}}.

			A second advantage is the current repository creation process is a little
			bit cumbersome, as highlighted by the previous sections instructions to
			fetch the build mechanism and the src/ folder in two different sources.

			Upsection repository contains our full usable template in ONE place.

			As of 2024-10, Upsection dependencies aren't up-to-date, so you'll need if you use it
			to upgrade Node packages to the one used in {{repo\|join}} or {{repo\|infra-www}}.

			Expected features:

			* Create a site with a `upsection` command
			* Being able to only store upsection configuration + assets directories in the websites repositories
			** `upsection` can regenerate the build mechanism: package.json, node dependencies
			** Site get freshest dependencies for the build mechanism

			Current languages stack:

			* At upsection level
			** Python for upsection itself
			** BSD make (Makefile) to generate needed files
			* At static site build level
			** Node.JS and Gulp still manage the site build
			* For the site assets
			** SCSS
			** modern JS with Babel to transpile when needed
			** HTML from handlebars templates
			** YAML for data

Dereckson: Redirected page to Static sites

2024-10-26T10:26:34Z

Redirected page to Static sites

New page

#REDIRECT [[Static sites]]