Fonctionalités méli-mélo

Requirements for a proper méli-mélo feature

• Be reusable;
• Be sponsored by a department and by an active representative of that department;
• Must include an implementation plan that explains the steps taken by the sponsored department on how they will actively work the feature to get it integrated into GCWeb;
• Must not contain any interference with wet-boew and GCWeb, meaning no component override nor extention (such thing should customization be contributed in the provisional or stable GCWeb or wet-boew component instead);
• Each individual sub-feature and style must be demoed, for instance each CSS classes or JS configurations;
• Working demo must be published using the GCWeb Jekyll template;
• Feature name must be in this format: Year and month of the time of the feature's publication followed by a short name identifying the feature (feature name example shown below).

Contribution instructions

• Code and/or reorganize the feature by levering GCWeb Jekyll theme.
• Create a feature folder in the méli-mélo GCWeb root folder.
• Loading features must not change the state of any generic page. Features must be explicitly activated through HTML by the web publisher, like wet-boew plugins or by using a CSS class to hook onto an HTML element.
• Feature's name must follow this notation: year-month-featureName. The year and month must correspond to the feature's initial publication date. For example "2021-05-steps".
• Implementation plan should be published along with the feature's web pages. Each item of the implementation plan must be dated because we are going to use it to measure the integration progress into GCWeb. The expectation is to get the méli-mélo feature fully integrated into GCWeb within less than one (1) year. See an example of an implementation plan
• Test your code and submission by using your GitHub pages.
• Submit the méli-mélo feature through a new GitHub PR in the GCWeb project.
• Once approved by the technical review, it will be assigned to a méli-mélo compilation and released on Canada.ca at the next release windows between 1 to 3 weeks.
• Update the méli-mélo feature code by executing the implementation plan and addressing all TODO's identified by the wet-boew technical review team.
• Participate at the weekly wet-boew Tuesday afternoon code sprint.
• Create the GCWeb provisional/stable feature aligned with our enterprise design approach.

Technical review checklist

This list contains the steps that the wet-boew technical review team uses to approve new méli-mélo features.

• Ensure the project sponsor is clearly identified;
• Project folder name follows the naming convention explained above;
• Each JavaScript feature and each style are demoed;
• Perform a code review to ensure there are no overrides nor conflict with GCWEb and/or wet-boew;
• Quickly check if we don't notice any major or obvious web accessibility and security issue. However, the accessibility conformance remains the responsibility of the publisher when implementing the feature into a web page;
• Ensure the feature doesn't automatically change the state of a generic page when loaded. It must not impact any content unless the feature is explicitly activated through the HTML code, like through the use of a CSS class or the presence of a data attribute;
• Review the implementation plan to ensure it contains a reasonable due date and deliverable. It must include:
  • Engagement with the Digital Transformation Office (DTO) at Treasury Board Secretariat;
  • Review and perform the identification of the feature transformation requirement to be able to complete the integration progress into GCWeb;
  • Produce accessibility conformance report and attach usability report, if any;
  • Transformation of the méli-mélo functionality into a GCWeb provisional feature;
  • Complete feature stabilisation task, like working example translation, writing guidance, publishing ACRs, feature API documentation, etc.