If there are errors when submitting a namespace request, display them in the modal without doing a full page reload.

Requires AJAX.

(originally from #21)

We need to have a SMTP server to be able to send emails to users when they register and for other purposes.

CEA identified some accessibility issues that can be found in the following document:
DAASPortal_20200602_CEA_vLab_FIXES.DOCX.pdf

All issues have been addressed and fixes have been implemented where needed.

Comments can be found at the bottom of the document.

Currently no spam protection on forms.
Add captcha v3 to protect them and not burden the user.

Originally posted by @bbronzan in #21 (comment)

Export the types from the covid portal and create them via a Setup recipe.

I don't seem to have the permission to do it myself. /cc @sylus

The latest "Development release" workflow succeeded, but the dev deployment of the portal errors out reporting no healthy upstream.

When the language toggle button is collapsed into a hamburger menu, its displayed in the menu as a lowercase abbreviation (e.g. "fr"). It should probably read "Français" in this state, which would cohere better with the "Sign In" option below it.

• Add README
• Add CONTRIBUTION documentation
• Add SECURITY documentation

Allow users to update their account details:

• username
• email
• password

Originally posted by @bbronzan in #21 (comment)

The current semantic page structure could be improved to make better use of the HTML5 tags. Not only would this improve the accessibility, but it will improve the content structure for many other uses. (optimized reading-view, SEO, and more)

We'll be reworking the use of:

• headings <h1>,<h2> etc
• <article>
• <section>
• possibly more

Reference
https://www.semrush.com/blog/semantic-html5-guide/

The issue at large was first highlighted in the accessibility review: #43

Port existing forms module with some improvements

• Single controller for submissions
• Integrated server side validation
• Form submission script
• Form Submitted workflow hook
• Load Vuetify / VeeValidate librairies
• Implement VueComponent widget that allows us to write simple VueComponents in the admin

• ensure content parts have meaningful names

Site-wide

• Navigation Bar
• Page header
• Footer

Front page

• Section: Hero
• Section: digital background
• Section: no background
• Section: dark background

Page

• Section: title
• Section: list layout
• Section: tri-card layout
• Section: split layout

Language toggle works fine the first click or so, then you have to click it twice to actually change. Sometimes the page changes but the button label doesn't.

Originally posted by @bbronzan in #21 (comment)

I18n is supported, but need to add translated content to the French version.

• Contact Form 273bd21
• Login views with External provider support (#112)
• Protected page (protected by roles) 7ffd33a
• Tab Widget d431e6e
• Content pages aa73205
• Schedule Widget
• Creation of Hacker, volunteer content types #59
• Hackathon CustomSettings #59
• Hacker Registration form #59
• Volunteer Registration form #59
• Team management (create, join, leave) #59
• Challenge list widget #117 #59
• Challenge submission form (for authenticated users) #117 #59
• Team list for authenticated users (can join team if not already on a team)
• Team captain (can kick other members, can pick Challenge for team, can edit team description) #128
• Team description (captain can edit) #128
• Challenge (formerly case) selection for team captain #128

Admin features

• Admin: Get mailing list of participants
• Admin: Display useful information in SummaryAdmin views (Email, Team, etc)

Documentation

• #56

Setup a documentation site on GH pages using mkdocs for this site / modules.

Feedback is registered to a Slack channel that's limited to the Digital Innovation team. Moving it somewhere visible to Project 22 members is a manual process.

Register feedback (automatically) to a location that is accessible to our support and research staff. Let's start with #feedback-notifications in the Slack support workspace.

happy

Testing from mobile

Add a Matomo analytics module that injects the matomo analytics script into the footer zone of the frontend theme.

Any user that logs in via AAD should be given the appropriate role to view content and maybe submit namespaces ?

Build workflow tasks that allow a user to:

• Create a GitHub branch
• Create Single file commits to branch and push them
• Create a GitHub Pull Request for any branch

These tasks should use an api token that is encrypted in the database.

Content

• Set up
• Architecture (i.e. modules, themes)
• Module/Theme Specific pages

Publish

• MkDocs; GH Pages

Variations of "sign in" are used across the portal and could use alignment.

• Hamburger menu (mobile): "Sign In"
• Homepage button: "Login"
• Sign in page: "Log In"

Seems like services tend to use "sign in" these days. GitHub uses "sign up", "sign in", "signed in". But as long as its consistent...

Create an entry for Hackathon module and theme

Originally posted by @arnaudroystatcan in #55 (comment)

Think about refactoring this into a tag helper or liquid filter at some point

Originally posted by @jptissot in #57

Would it be possible to amend the automated process that creates PRs that add Profile manifests to the platform (#2):

• The filename should follow the convention: profile-[-a-zA-Z0-9]+.yaml
• The file should be placed in /config/kubeflow/

Remove the plugin from the Manifest template. @zachomedia says we are no longer using this.

If possible, the PR should be assigned to the DAaaS project.

Chrome iPad her FIP is completely cut off. (not a huge deal)

Bottom FIP sig is slightly cut off too.

Originally posted by @bbronzan in #21 (comment)

Change the "Email" input on ExternalLoginCallback to an "email" input so mobile browsers use the special keyboard.

Originally posted by @bbronzan in #21 (comment)

Turn the registration feature back on and include account-related pages as necessary.

Was thinking of publishing them to the Github nuget repository. But only publish releases.

Setup cypress tests with github actions

Make updates available at production URL.

As a user, I want to leave general feedback via the web portal to share my experience with the developers.

A simple up/down rating with a comment box is probably sufficient. We could reuse the GitHub module to submit an issue to a support or feedback repository with the content. This way we could automatically track progress on feedback that needs action.

Open to other suggestions.

When a new user comes to this page https://portal.covid.cloud.statcan.ca/ there are no links or instructions on how to get an account if they don't have one already.

This leaves users at a dead-end - they need either a sign up link or instructions on what to do next.

Let's get a simple list going on anything we know that still needs to be tweaked, but works well enough to user test during the hackathon next week.

Allow users to change their profile (name and profile). Investigate if it's possible to change account name in Orchard.

Originally posted by @bbronzan in #21 (comment)

Should this be part of the generic widgets module ? or part of another module for our team's assets ?

Originally posted by @jptissot in #57

The UX feedback I'm getting is that users are overwhelmed by the number of options in the portal. I think Kubeflow and Minio are the two most important options for 90% of users, so maybe there's a way to highlight "Get started with these two" and then leave the rest below?

1. Hero: BG does not scale exactly how we would expect, but at normal window sizes it actually looks ok. It's between sizes where things get funky.

(Try adding this to head... apparently this corrects the CSS background-size: cover)

<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

2. Feedback modal: Button slightly overlaps bottom of text input

3. section-panel: Description text just keeps goooooooooooing!

4. Add-on action modal: Is a bit of a mess, but likely caused by the text flow.

5. Account modal: Mild spacing issue

Support using multiple github api tokens which may have a different set of permissions.

Tokens should be accessible by name in the workflows.

https://www.npmjs.com/package/npm-run-all

Import the module from https://github.com/stc-digital-innovation/StatCan.OrchardCore/tree/master/src/Modules/StatCan.OrchardCore.GCCollab and make sure it works :)

happy

Brendan testing

Long modal titles can be occluded by the modal's close button. This is the case for "Request a Kubeflow namespace" modal, tested on mobile Firefox.

Safari iPad hero almost fits... the FIP is cut off slightly

Bottom FIP sig is slightly cut off too

Originally posted by @bbronzan in #21 (comment)

Add a empty project to include the test and cypress folder to the solution

Firefox Focus mobile hides the feedback modal when the bottom link is tapped.

The modal displays but when the text area gets focus and the keyboard comes up, it scrolls away.

The top link didn't do that though... strange!

Originally posted by @bbronzan in #21 (comment)

Firefox Focus mobile hides the namespace modal when the input has focus and the keyboard comes up.

(like the issue above with the feedback modal)

Originally posted by @bbronzan in #21 (comment)

We should experiment with shape wrappers instead of having partial html tags in different files.

Originally posted by @jptissot in #57