Strider-CD/strider

Migrating Template Engine

Open

#831 opened on Jul 9, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (4,587 stars) (454 forks)batch import
enhancementhelp wanted

Description

There were discussions about template engines and swig made it through all that to be the choice, however with swig "no longer maintained" (https://github.com/paularmstrong/swig/issues/628), looks like eventually it will reach the point to consider migrating swig to other alternatives. I do like jinja style templating and I am also aware of some other young engines that has good benchmarks, like slm, dust, while veterans like handlebar, mustache and ejs are also good. But just to keep consistent and eliminate labor work on all html files, maybe nunjucks would be worth checking out?

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Knowledge of swig template syntaxFamiliarity with Strider's template files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate all HTML files in the Strider codebase that currently use the swig template engine. Compare the templating syntax and features of nunjucks (the suggested alternative) with swig to identify necessary changes. Review the existing issue discussions for any prior consensus or concerns. Propose a migration plan that minimizes changes to the HTML files and ensures backward compatibility of the CI/CD server's UI rendering.