Aumet Web Portal
Technology stack
This project was seeded by Cricket Angular
As a front end developer, I used Angular (13 as it is now), to create the front end, using a design template already handed out to me (not the actual design, rather a guidelines). To setup a prototype, I created a dummy NodeJs server to serve static json, once ready, I switched to the production API on the production environment. This way of development aids me to visualize the API design, document it and design for possible edge cases, without breaking the server. Even though I am not responsible for the backend, nor is it supposed to be the case that I design first, but in most of my projects, I usually am in to the team first, so instead of waiting for the API design to be ready, I just do it myself. When the backend developers are ready, I submit a Postman documentation, and we take it from there. That is much faster and more accurate way of work. Example document (of another project): https://documenter.getpostman.com/view/2735789/RztrK7Fr
As a front end developer, I used Angular (13 as it is now), to create the front end, using a design template already handed out to me (not the actual design, rather a guidelines). To setup a prototype, I created a dummy NodeJs server to serve static json, once ready, I switched to the production API on the production environment. This way of development aids me to visualize the API design, document it and design for possible edge cases, without breaking the server. Even though I am not responsible for the backend, nor is it supposed to be the case that I design first, but in most of my projects, I usually am in to the team first, so instead of waiting for the API design to be ready, I just do it myself. When the backend developers are ready, I submit a Postman documentation, and we take it from there. That is much faster and more accurate way of work. Example document (of another project): https://documenter.getpostman.com/view/2735789/RztrK7Fr
Angular Universal: as it was required for the pages to be crawlable by web bots, and shareable over web, SSR was needed.
SEO: The team had SEO experts that would required certain build up of urls, and meta tags, in addition to tracking information to be logged into Google Tag Manager, thus, the project was adapted to create highly dynamic URLs, using user company names, countries, and sometimes medical specialty, and every action was trackable and loggable. Here is the documentation of the tracked tags:
https://bitbucket.org/amalayyash/aumetgatracking/src/master/
https://bitbucket.org/amalayyash/aumetgatracking/src/master/
Multilingual: The project was setup to handle as much as 5 languages (that feature was never used because the client never provided translations). To be able to create up to 5 languages build, I dropped the Angular multilingual I18n module, and created a simpler version, where the build is done once, the translations are provided upon request on client or server, via Javascript. Used mainly Gulp to finish the job of creating multiple index files, and took out the SSR from the src folder into the host folder, to be able to fine tune routing for different languages in NodeJs. (Angular is good, but sometimes they butt their noses into everybody else's job!)
Private area
To login, use client@email.com, and ayyash123.
PS. The project was stopped due to change in business direction into a more ecommerce mobile-app.
