I'm a self-taught programmer who loves learning and problem-solving.
💻 Tech stack
My stats:
💼🔭 Projects and plans
What I'm up to 👀
📌 Open source, workshops, hackathons and challenges
Contributing to the coding community — getting involved in open source
I've recently been helping out with MDN Web Docs (I'm a maintainer/reviewer for l10n-fr at translated-content, I also contribute to English content and more)
Working on my portfolio and fun side projects
Picking up new skills, mastering what I know and training my problem-solving (have a look at some of my repositories)
Rather than using the default GitHub Pages 404 page, a custom 404 page should be created in 404.html (place in root level of the repo) to avoid loss of traffic and confusion for users. Consider including a sitemap (possibly formatted as a table) in the main content container.
Motivation
Allows users to navigate the site more easily/find what they're looking for if an erroneous link is requested (likelihood is higher after site/directory reorganization).
#15 — Add/attribute licenses to QUÉtudes-info for clearer directives on sharing site content, and to "allow" contributions (open sourcing the project: two separate licenses for the content/prose and the code).
#22 — Update "help" page entries, notably the "having issues" one
#15 — Replace current README with general overview, add various docs files for contributing, style guide, etc. (+ issue/PR/discussion/contributor etiquette)
#15 — Move current README content into ABOUT.md in a docs folder
The site footer should be updated to include a "contribute to QUÉtudes-info" banner, making it easier to locate the GitHub repo/source file (can be part of a PR/series of PRs fixing the other tasks in this issue or added and tracked separately).
The repository files could be better organized. The following changes should be made:
All pages that are linked in the dropdown section of the navbar should be placed in a folder (e.g. all pages that are part of the "What is CEGEP" section should be moved to a folder, likely named whatiscegep)
Images (aside from the favicon) should be moved to an assets folder
JS scripts should be moved to a scripts folder
IMPORTANT: Correct/update all links and sources accordingly!
The 2022-23 school year has started, and the important dates need to be updated/"reinitialized". (Update the Applying to CEGEP -> Important Dates page)
Links on QUÉtudes-info leading to another page or heading of the site do not need to be absolute. The https://cw118.github.io portion of such absolute paths is unnecessary, and relative paths tend to be more efficient/the recommended way of including links.
The tool currently works fine, but is difficult to maintain (especially for outside contributors) as it relies on displaying images for a selected program. The planned re-implementation will instead use JSON files for each CEGEP, then compare.js will fetch a JSON object based on the selected CEGEP, and dynamically display all information stored for the child object matching the selected program.
This will also involve a slight reorganization, with compare.js moved out of the scripts folder into its own program-compare folder, where all JSON files will be stored as well.
Once all of the above is done, the image files (assets) associated with the old/"deprecated" version of the Program Comparison Tool can be removed.
HTML automatically detects when a <ul> or <ol> element is nested within another, so most, if not all, uses of the inner class for <ul> and <ol> are unnecessary and can/should be removed.
Bill reforms caused some important changes in cegep policies regarding the exit exam (english or french), number of french courses, etc. QUÉtudes-info content should be updated to reflect these reforms.
For the months/titles (incl. "Past dates") that have events, transform the titles into clickable collapse sections to reduce page length/size. (cf. the page "Application Systems" for examples of dropdowns with Bootstrap)
Create and embed a contact form in the "contact" page, which is currently blank. Ideally, a link to the form should be included/mentioned on the "help" page as well (e.g. report issues/submit questions and more ):
Embed contact form on "contact" page (also include a link to allow users to complete the form in a separate tab)
Update various "help" page entries, notably the "get in touch" one