Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update README.md added tage for front end build if it is passing or not * Add new site navigation - Added new default.pug with new navigation layout - Added new _navigation.sass with new styling * Fixed SASS Variables (#341) - _navigation.sass updated with SASS Variables * Update README.md * SASS Fixes/ Index pages updates/ Misc and New images (#342) * Fixed SASS Variables - _navigation.sass updated with SASS Variables * Update index.pug Added New index.pug Layout for the new front end * Update index.pug Added New index.pug Layout for the new front end * Refactoring + Adding Bulk files - Removed leftover Boostrap file as we are no longer using the framework. - Added New images - Updated index.js - remove bootstrap line from concat.js * Site.sass Update - Removal of @import bootstrap * Adding new pages (#343) * Fixed SASS Variables - _navigation.sass updated with SASS Variables * Update index.pug Added New index.pug Layout for the new front end * Update index.pug Added New index.pug Layout for the new front end * Refactoring + Adding Bulk files - Removed leftover Boostrap file as we are no longer using the framework. - Added New images - Updated index.js - remove bootstrap line from concat.js * Site.sass Update - Removal of @import bootstrap * Add New Pages with Corrisponting JS Files Add blank pages for all the dropdowns & added pages lines in express.js * Additions and Updates (#344) * Fixed SASS Variables - _navigation.sass updated with SASS Variables * Update index.pug Added New index.pug Layout for the new front end * Update index.pug Added New index.pug Layout for the new front end * Refactoring + Adding Bulk files - Removed leftover Boostrap file as we are no longer using the framework. - Added New images - Updated index.js - remove bootstrap line from concat.js * Site.sass Update - Removal of @import bootstrap * Add New Pages with Corrisponting JS Files Add blank pages for all the dropdowns & added pages lines in express.js * Additions and Updates - Added $ to JShint file for development - Fixed _navigation.sass to original CSS Variables - Add AI.js - Minor Tweaks to express.js - Add moments variable to getRecentUsers.js & Updated consistency of `'` over `"` - Added better Syntax for index.js - Added New index.Sass styles - added leaderboards.js - Updated README.md * Create AI Page (#345) # Updating Small update to index.sass on the size of certain elements and addition of ai page. * Removal of residual Bootstrap files (#346) - Boostrap files located in public/js - bootstrap files located in public/fonts * Landing Page Update (#347) # PUG ## index.pug The multiple and slide variants/containers were taken out and replaced by the improvement container. The latter is cleaner and easier to read, and takes less user imput for the same output. The rectangle containers were improved so they take less space and look somewhat cleaner. Other unused classes/code was cleaned for better readability. ## default.pug a link was added to the FAF logo on the footer, favicon image was also added. # SASS ## _navigation.sass Font sizes were all decreased so the website is easier to read and less on the "face" of the user. FAF logo on the footer is now aligned with the other footer elements. ## index.sass Creation of the styling of the improvement container, made the thinContainer titles have a z-index so the splat doesn't overlap them. Made other images and items smaller for better readability. # Images Some images were changed/updated to have a correct size ration for the rectangle container (from 1:1 to 16:9). * Navigation Page Update (#349) # PUG ## index.pug Fixed small bug with thin container being overlapped by splat img. ## default.pug Added FAF logo to mobile navbar. # SASS ## _navigation.sass Mobile navbar received some styling updates, icons and text got more padding for less mistakes in smartphone touch. Created styling for the FAF logo on mobile navbar. ## index.sass Improved improvement container so its responsive to screen size (making itself 3, 2 or 1 columns depending on how big the screen is). # Images New faction and resource pattern images added for mobile navbar * JS Fix (#350) * Licence #341 all Major Contributors to the site have agreed to this MIT Licence. any outstanding people who have not accepted change parts of the side that are no longer being used * Update Licence.md * Navigation Page Update # PUG ## index.pug Fixed small bug with thin container being overlapped by splat img. ## default.pug Added FAF logo to mobile navbar. # SASS ## _navigation.sass Mobile navbar received some styling updates, icons and text got more padding for less mistakes in smartphone touch. Created styling for the FAF logo on mobile navbar. ## index.sass Improved improvement container so its responsive to screen size (making itself 3, 2 or 1 columns depending on how big the screen is). # Images New faction and resource pattern images added for mobile navbar * JS Fix + Minor Update # PUG ## index.pug Made the rectangle containers more compact (easier to read). # SASS ## _navigation.sass topnav received an increase in font size for better readability ## index.sass Reduced padding of rectangle container text so it is more compact. # JS ## index.js Fixed issues with ACU cards caused by the previous deletion of other elements on the pug page (multiple and slide containers) without the deletion of their javascript functions. Causing JS to stop working due to not finding elements that don't exist. Co-authored-by: Rowey <[email protected]> * $Variables (#351) # PUG ### ai.pug Made the rectangle containers more compact (again, less on the "face" of the reader). ### default.pug Made a comment in a nav_absolute that seems misplaced but isn't. # SASS ### _navigation.sass and index.sass Starting to update most of the css variable var(--) for the better $variable used by sass. This is being done so @Mixins can be used soon. ### mixins.sass Cleared out of unused Mixins and updated to become the current variable.sass. It doesn't have any mixins but depending on the amount of mixins used, I might just not make a different page for variables and one for mixins (less pages = better). ### _mixins.sass and _footer.sass Both deleted as they are out of use. # JS ### index.js Made extra comments so JS is even clearer and updated the pulsating function to work without var(--) (JS can't use $color because it will render $color into the css rather than the actual color variable. Ergo, manual colors were used). #Images ### footerbanner.jpg Updated to a better version of it that will be better displayed on smaller screens. * Preparing for Localisation Support (#352) - Adds the Following to package.json : i18next,i18next-browser-languagedetector, i18next-fs-backend, i18next-http-middleware - Updates yarn.lock - Added Initialisation to express.js of i18n Support - Added locales' folder structure - Added translation.json files to locales folders * Minor fixes & Add new Pages (#353) - index.pug removed # calls with . notation - index.sass removed # calls with . notation - Added patchnotes.js & patchnotes.pug & updated express.js Accordingly * The fix for the fix (#354) # PUG and SASS ### index.pug #index.sass Just re-adding some # that were necessary for IDs in the JS * @use mixins (#356) * #@use and mixins ## PUG and SASS ### index.pug #index.sass Added mixins.$variables (the correct way, rather than just $variable). Renamed the split containers to grid. Grid is a much more fitting name than split for the "template" of the grid containers. ## _mixins.sass Received some new mixins. ## _navigation.sass Deleted alot of unnecessary 0px (px not needed) to clean up the Problems tab and rid the code of every "problem" it had. ## site.sass and deletion _mobile.sass, _fonts.sass and _elements.sass were deleted due to not being used and to clear space. site.sass now uses (once more) @use rather than @import. This is due to the fact that @import is being deprecated this year and replaced by @use. * @use and mixins ## PUG and SASS ### index.pug #index.sass Added mixins.$variables (the correct way, rather than just $variable). Renamed the split containers to grid. Grid is a much more fitting name than split for the "template" of the grid containers. ## _mixins.sass Received some new mixins. ## _navigation.sass Deleted alot of unnecessary 0px (px not needed) to clean up the Problems tab and rid the code of every "problem" it had. ## site.sass and deletion _mobile.sass, _fonts.sass and _elements.sass were deleted due to not being used and to clear space. site.sass now uses (once more) @use rather than @import. This is due to the fact that @import is being deprecated this year and replaced by @use. * Code Cleanup (#357) ##PUG and SASS Code was improved with SASS and older code was deleted/changed to use less lines for the same output. ACU container received a well deserving update ##JS cleaned up old JS of ACU container but currently it doesn't work perfectly. Whoever wants to fix it can get a cookie lol. * Update README.md (#358) - Added Public POEditor link for site translation * Language Tab + JS Fix (#359) ##PUG and SASS ### Navigation (default.pug, _navigation.sass) A language tab has been added since Rowey is working on adding multi-language capabilities to the website. ##JS ### index.js The faction containers got fixed and now work plus they have new hover and active animations. * Re-structuring + Cleanup (#360) ## Deletion Files deleted were 99% related to the styling of the website. Due to the new development of the website, these style sheets don't work anymore unless I stick to the naming conventions and previous work done. However, a great part of these files either seem to bear no purpose or are inefficient (such as using static sizes for the size or width of elements, making them non-responsive to changes in screen size). ## JS ### index.js Gave the language navigation it's own JS, trying to make it respond to click rather than hover but its a work in progress. ## PUG ### index.pug Added comments for clarity ### newshub.pug Starting to toy around with it, trying to understand the logic and way it was structured so we can update the newshub. I would just re-do it from start but the code being used from wordpress and the json is far too advanced for us to re-do at the moment. ### ai.pug Making the contents more compact so they are easier to read ### tutorials-guides.pug Creation of page, work in progress. ## JS ### index.js The faction containers got fixed and now work plus they have new hover and active animations. ## SASS Small changes done to the styling of the pages, changed margins and fixed other issues. * Update README.md (#361) - Replaced Image with new Frontend * Banners and Pages (#362) ## PUG ### default.pug Through a mixin banner and the use of blocks, now I have created a template for all the banners that is very easy to configure across the board. You will see almost all pug pages now have their own banner with images and text. The navbar has also become a bit smaller and Kazbek's statistics removed from it. ### index.pug Small changes and the removal of Kazbek's player statistics from the FAF Improvements section. ## SASS ### Overall Small styling changes, made the rectangle container a mixin so it can be added in multiple places yet changed on each page. ### _variables.sass Despite it containing unused content. This styling sheet now contains the current used variables. Therefore, _mixins.sass currently only has mixins and not both mixins and variables ## Images Images have been added/updated for the new banners every page has. ## Deletion Jquery was deleted since it wasn't being used. * Banners and Pages (#363) ## Content Creator Page This update is just the creation of the content needed for the content creator page, it using a pug mixin and being pretty much "completed" for now. ## default.pug The navbar received some re-ordering so it is ordered by longest to shortest text, giving it a cleaner look. ## Elsewhere Not much was changed, maybe I created the sass files needed for certain pages but nothing significant was done. * FAF TEAMS (#364) ## FAF TEAMS This update is just the creation of the content needed for the faf teams page, it using a pug mixin and being pretty much "completed" for now. * Leaderboard (WIP) (made with @MrRowey) (#375) ## Leaderboard Current work to "recreate" the leaderboards. * Game Server Player Counter (#378) Added back in the player counter to the main page Co-authored-by: MrRowey <[email protected]> * Fixed default.pug not working (#380) ## default.pug Small fix to default.pug so @MrRowey can continue to work on the player counter. ## index.pug JS was on the same indentation as a block content and so it wasnt working. I indented so it works. * 1V1 (#382) * Fixed default.pug not working ## default.pug Small fix to default.pug so @MrRowey can continue to work on the player counter. ## index.pug JS was on the same indentation as a block content and so it wasnt working. I indented so it works. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * Delete clans.json * Delete recent.json * 1v1 leaderboard (#383) * Fixed default.pug not working ## default.pug Small fix to default.pug so @MrRowey can continue to work on the player counter. ## index.pug JS was on the same indentation as a block content and so it wasnt working. I indented so it works. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * Delete clans.json * Delete recent.json * Leaderboard Update / Creation ## PUG Small changes to naming and the addition of certain IDs in certain elements for their use in js (for example, the global container having a #globalLeaderboard Id so it can be called in js when its clicked) ## JS ### Creation of the Pagination The complete creation of the next, previous and switch of leaderboard type (currently only global). This was done through just removing the previous contents with the'delete' class and re-adding the new ones which then would be changed either to the next 100 players or the previous 100. Huge thanks to both @MrRowey and @Sheikah ## Other scripts Small change done to updateLeagues.js so it moves the clans.json to the correct members folder and also adding a .gitignore to it so the json files dont get commited. * New frontend (#387) * Fixed default.pug not working ## default.pug Small fix to default.pug so @MrRowey can continue to work on the player counter. ## index.pug JS was on the same indentation as a block content and so it wasnt working. I indented so it works. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * Delete clans.json * Delete recent.json * Leaderboard Update / Creation ## Styling This update brings a lot of styling changes to the leaderboards and small tweaks to the size of the nav bar and other things. ## Functionality Now all 4 leaderboards are operational with their own searchbar that can compare across the board. It is still a work in progress to get the missing player issue working. ## Bigger Reason This commit is being done since my PC is having issues and I want to keep a safe copy of my work before its too late. * Leaderboards (#389) * Fixed default.pug not working ## default.pug Small fix to default.pug so @MrRowey can continue to work on the player counter. ## index.pug JS was on the same indentation as a block content and so it wasnt working. I indented so it works. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * 1v1 Leaderboard ## PUG index.pug and default.pug both received updates so only the index page shows the amount of players currently online. leaderboards.pug received some IDs in order to be able to receive the js from leaderboards.js adequately. ## JS leaderboards.js received the JS needed to be able to pull the data from 1v1.json and make the leaderboard for 1v1. Currently, it only supports the first 100 players, soon a First, last, previous and next buttons will be added. ## Other scripts Certain changes that were very minor were done on extractor.js, getRecentUsers.js and so on were done so the files from the API are placed in the correct folder. * Delete clans.json * Delete recent.json * Leaderboard Update / Creation ## Styling This update brings a lot of styling changes to the leaderboards and small tweaks to the size of the nav bar and other things. ## Functionality Now all 4 leaderboards are operational with their own searchbar that can compare across the board. It is still a work in progress to get the missing player issue working. ## Bigger Reason This commit is being done since my PC is having issues and I want to keep a safe copy of my work before its too late. * Leaderboards Completed ## SASS Changes Deletion of unused classes, cleanup of leaderboards styling, the adding of other classes that were needed for the new dropdown buttons. ## JS Changes The leaderboard finally is fully operational. With a time filter, search function, matchmaker filter and a clean UI that works both in desktop and mobile screen sizes. Alot of the previous JS was trimmed and made much more compact, so the leaderboards.js are occupying as least space as needed and now can be read much more easily. ## PUG Small changes done to certain naming classes and Ids for a cleaner and easier to read file. * Leaderboards and Extractor ## JS Improvements made to the extractor.js file, made far more compact and using less packages and way less code repetition. leaderboards.js also had improvements thanks to @Louvenarde's review on how to do certain processes on a more efficient manner (such as using flooring instead of slicing to get the last page of the leaderboards). Also updated to reflect the new changes done on extractor.js. ## Node-fetch installed so we could use fetch to call API. ## AI Page Deletion of the LOUD honorable mention due to the association's decision on the annual meeting. Co-authored-by: Javi Trek <[email protected]> * Fix Development Environment Issues (#392) ## Fix We commented out localization support for the time being and fixed other issues in other files due to missing package variables (such as let = require('moment'). * Navbar old (#393) * Fix Development Environment Issues ## Fix We commented out localization support for the time being and fixed other issues in other files due to missing package variables (such as let = require('moment'). * Navigation Bar 2.0 # Navigation ## Desktop Navbar Received some minor updates, having the same core structure but a new fade animation added to its menus. Now both the topnavbar and the desktop navbar share the same color for a more unified structure. The PLAY NOW button was reduced to a DOWNLOAD button. FAF NEWS > NEWS and the removal of other elements inside the GAME, COMMUNITY And COMPETITIVE tabs (for example, there isnt a Trainers page anymore since it will be part of the tutorials guide page). ## Mobile Nav Bar Complete and total overhaul of the previous navigation bar. Now with far cleaner code and less JS. Occupies the whole screen, stops user from scrolling inside navbar and has a far cleaner design that syncs with the rest of the splats and the "reforged" aesthetic. Alot of testing done on it with the inspector/dev tools of Chrome. But further testing is needed on an actual mobile device, just to make sure the font size and responsiveness is truly adequate. ## Footer Also received a small redesign while keeping the same core structure. Now it has a much cleaner design. Updated a couple of links and terminology as well. # Leaderboards ## Responsiveness The leaderboard had issues with the names of usernames having the " - " character (as seen with user "e------------") since it would break off into the next line when the username ran out of space rather than hide the overflow (increasing the height of the username column, making it not able to fit correctly with the other columns). The issue wasn't resolved directly, but instead the username column had an increase of space (at the expense of the rating column being smaller now). Also received minor changes with the placement of the buttons for ease of use. ## Other Smaller and trivial changes were done to certain variables or pages. Nothing worth mentioning (such as slight color changes on _variables.sass). * Landing page (#395) * Fix Development Environment Issues ## Fix We commented out localization support for the time being and fixed other issues in other files due to missing package variables (such as let = require('moment'). * Landing Page 2.0 ## Landing Page the landing page has received some well deserved updates. A lot of content was recycled and given much more cleaner and smoother designs (while using much more compact and less clunky code). ## h1, h2, p Now the website is featuring a stronger usage of h1, h2 and p for title, subtitle and paragraph. This will allow for a better standardization across the room and using less codes since .somethingTitle or .somethingSubtitle won't be used anymore. ## Image Purge with the new update to the landing page, a lot of old and unused images have been purged. Creating a cleaner image folder. ## Variables and Mixins Some Mixins (such as buttons) received a well deserved update as well. A tricolor (regular, light and dark) faction color variables have been created in case something needs to be faction color coded. * Removed Commented Code & Account pages Forming (#396) ## Removed commented code Removed some commented code that was planned to be done but currently with limited time has been removed and can be re-added at a later date ## started working on the pages for the user accounts to fit in with the new style * Mulitiple File Clean up & Page Addtions (#397) * Removed Commented Code & Account pages Forming ## Removed commented code Removed some commented code that was planned to be done but currently with limited time has been removed and can be re-added at a later date ## started working on the pages for the user accounts to fit in with the new style * Play Page and File clean up # working on the play page added some new images removed unsued files * oulince complted * added campagin-missions pages and fixed up nav bar for download * Play Page and File clean up # working on the play page added some new images removed unused files * Newshub (#398) * Fix Development Environment Issues ## Fix We commented out localization support for the time being and fixed other issues in other files due to missing package variables (such as let = require('moment'). * Newshub ## Newshub In this update, the newshub for the website and the client have both been created. Meaning their pug, sass, js pages and extractor API calls. ## Other Fine Adjustments Other smaller changes might have been done but they are not significant enough to bring mention. * FAF teams (#399) * Fix Development Environment Issues ## Fix We commented out localization support for the time being and fixed other issues in other files due to missing package variables (such as let = require('moment'). * Tiny Newshub * Comment out Leaderboard API Call * Add Embedded YouTube Video to Play.pug * Update package.json - Removed i18n packages for now as localaisaion support is not the main prioority -removed bootstrap-validator as we are no longer using the bootstrap framework ## Updated - async - autoprefixer - body-parser - dotenv - express - express-session - express-validator - highcharts - html-ellipsis - json-api-models - moment - node-fetch - semver-regex - showdown - trim-newlines - wpapi - grunt - grunt-contrib-concat - grunt-contrib-jshint - node - npm * Cleand out some of the route files with redunded lines ## index.js Removed all the app.get line that were to do with the old News/blog posts as well as the old tournement setup ## Lobby_api Changes ["countries"] to dot notation not sure if this works need to be tried on test server & removed blank lines ## middleware.js - Removed Unesseasy blacn lines - removed the news and commpeteive navlinks - removed all tournament cNavlinkes - replace var with correct let or const ## wp_connector.js Condence the file to 4 lines rather than 8 ## challonge_connect.js add new js file for the updated chalonge api fucnion which it TODO * Adding the GOG link pages * Client News Update ## New Features Besides now having a much cleaner and smoother design that fits better with FAF, the new newshub comes with a couple more features. ### Image Sizing Now all image sizes are supported! No need to make your images 145x97 or other cumbersome sizes. Now images are automatically re-sized. Images with a 16:9 ratio (2560x1440, 1920x1080, 1280x720 or anything "rectangular") will fit perfectly. Other non-rectangular images will still adjust correctly but might receive a cut-off. ### Unlimited Articles Since now the articles are on a "slider", we dont have a limit with how many articles we can have without sacrificing design. So 5, 7 or 12 articles will all display equally well! ### Responsiveness This design has media queries and responsive unit sizes (such as vw) to always adjust to the users preferences. Therefore, the news will display adequately whether it's on a full screen window or 1/4 of the monitor screen. ### More Information Less Clutter The new design also provides more links for the user. With joining the discord, twitch and youtube FAF content being one click away plus new sections for new players, community tools/spaces and developmet plus a Support FAF button and a Report a Bug button all in one compact and clean design! ## Other Many of the images inside the images folder have been moved to a logos folder in order to maintain a better order inside the folder (rather than having 40 images on one folder, have them on their own folders). * Fixing Links of Client-News Tiny commit to fix the links and a bit of wording on the client-news. * TOS Pages - All the TOS pages have been converted over to Pug files - English TOS page is the Default Page with a link to translated versions at the bottom of the page * Minor Fixes To Client News The client-news page has stayed mostly the same but received some minor styling changes that make the design more compact, takes away highlight/focus from minor parts and makes titles stand out more. * Fixing News Links Just re-adding the correct links to the client news. * FAF Teams ## Page Creation The FAF Teams has been updated. Now featuring a slicker design that elegantly incorporates the new background. The page now has 9 teams out of 11. Community Manager seemed more like a one person position and it seems the Game team will be disolved. Ergo, they were not added so we could have a perfect 3x3 grid for Teams. The teams also now feature a bigger description made by me using what was found in the teams page in the FAF wiki. * Donations Page ## Page Creation The Donation has been updated. Now featuring a slicker design that elegantly incorporates the new background. The page now has a pie chart to demonstrate how FAF expenses are being done and two buttons for Patreon and Paypal. * Contributions Page ## Page Creation The Contributions page has been updated. The page now has updated links and descriptions to the four forms of contribution to FAF (Development, Creating maps/mods, bug testing and graphic design/promotion). Content creators and AI development both have their own page (and therefore don't need to be in contribution) Issue hunt was taken out due to inactivity, this was approved by Rowey. Training was taken out due the inactivity/lack of movement of the training team. Usually people just answer questions on the gameplay channel and thats how they contribute to training, there isnt a link for that. ### Other Some other elements or pages have received minor updates for better appereance on mobile and smaller screen sizes. * Content Creators Page ## Page Creation The Content Creators page has been updated. The page now has the same youtubers but with an updated UI. However, the big deal now is that its contents come from the wordpress, making it easy to edit without pushing changes in github. * Tutorial and AI Pages ## Page Creation The Tutorial and AI pages have been updated. Both pages now feature up-to-date links. A cleaner design both in desktop and mobile. There isn't much else to talk about since both pages are mostly just HTML and styling, carrying no JS whatsoever. ### Other Some other elements or pages have received minor updates (such as AI/Co-op Play being renamed AI/Skirmish) * Campaign Page ## Page Creation Campaign and Co-op missions page created. It has all the information about the original 24 missions, the new seraphim and coalition campaign, new custom missions and links to join the official campaign development and a bit of information on how to help./create your own missions. * SCFA vs FAF Page ## Page Creation The steam changes page has been created. It includes a link to all the changes in the wiki plus the patchnotes. However, it also has a re-written/summarized version of the most significant changes. * Express JS cleanup ## Tournament Page The tournament page has received a small cleanup and work has started on it. Currently It has stopped since I'm learning how to go through oauth2 for challonge and using passport js/express js. ## Express.js Received a small cleanup in code (taking out repetiion and putting it into a for loop/for each statement). Will continue to receive updates and cleanups as I continue to learn more about it. * Express JS cleanup ## Eradication Nation With the power of one for each statement, I have absolutely cleared an insane amount of garbage (19 js files) from the backend express and routes files. For whoever codes this website in the coming future, please look up for each and for i statements because repeating the same code in 19 different files is extremely amateur hour and creates a file flood that makes understanding the website for new developers (such as myself) much harder because there is a lot of garbage being repeated that creates so much noise. * Delete package-lock.json * Re-Enable-Leaderboards * change API URL * Global Leaderboards Re-added Plus some other minor tweaks, no signficant changes being applied to other files worth naming. * Global Leaderboards Re-added Plus some other minor tweaks, no signficant changes being applied to other files worth naming. * Global Leaderboards Re-added Quick Fix Plus some other minor tweaks, no signficant changes being applied to other files worth naming. * Global Leaderboards Re-added Quick Fix Added a / to fix a call * News Articles Update ## News articles now have their own page/url Yes you read it right, now the FAF website has the capability to not only pull the articles from the wordpress and render them correctly. But, it also is able to create urls for users to share a specific article! ## UI Update The newshub page has also received some tweaks on the graphical side. * News Auto Refresh ## 5 minute updates Now the news will update every minutes, being able to show off the new content without needing a server re-build. * Login Test Small changes done to files to see what login functionalities work * File Update ## Deletion of Files Certain files were deleted either because they were re-incorporated somewhere else or because they are not currently in use. This is being done to reduce the amount of noise in the backend code since I'm quite inexperienced with the backend and the less files the easier it will be for me to understand the system. ### extractor.js Changes were done to certain naming conventions for better readability, plus some comments were added. ### getRecentUsers.js Changed into simpler/easier to read code. It has its module on express.js to run every 30 seconds. It takes the recent ranked (with at least 1 ranked game) players of the last 4 hours. * Pug Tags Bug Fix ## Deletion of Files Certain files were deleted either because they were re-incorporated somewhere else or because they are not currently in use. ### index.pug default.pug Both received a minor change that fixes an error that has been console logged for centuries to come. Finally I'm rid of that hellish "You shOULD not hAvE pug TAgs wITH muLtiPLE AtTriBUteS." * Pug Tags Bug Fix ## Deletion of Files Certain files were deleted either because they were re-incorporated somewhere else or because they are not currently in use. ## navigation.js / Navbar has its own js file and doesn't share it with index page So before, the home page and navbar shared the same js file. This has been fixed so only the navbar only brings the js it needs instead of every page having the navbar and the index/home page js. This also caused some console errors on non-index pages since it wouldnt be able to find elements that are only on the index page. ## getRecentUsers.js Stopped it from console logging since it would do so every 30 seconds... ## 404.pug 500.pug Both now show a banner image with the same message. * Backend Work ### Backend Changes This patch may not add much in the test server at the moment, but its a way to save the changes I'm doing while using discord as my oauth2 provider. I would add more detailled patches but this build is a bit experimental/learning so its very likely it will receive heavy changes. * Backend Work ### Backend Changes This patch may not add much in the test server at the moment, but its a way to save the changes I'm doing while using discord as my oauth2 provider. I would add more detailled patches but this build is a bit experimental/learning so its very likely it will receive heavy changes. * .env variables and logging in and out # Backend Changes ## .env Some variables that should have been secret have been put into the .env document to stop any funny business. ## login in and out Now the website is able to verify if you are logged in (through discord) and able to make only select routes checked if the user is logged in or not (currently all for testing purposes). * accounts -> account # Backend Changes ## Accounts folder The routes/views/accounts folder has been changed to just account to match the same folder in templates/views/account. ## Register Page I'm actively working on the register page, both on trying to make it much cleaner but also functional * Backend revival # Backend Changes ## Deleted files are coming back Certain files that were deleted originally are now coming back. I have a better understanding of the backend and I can re-add files that are needed. At some point I thought of re-doing the whole back-end but due to lack of direct testing and the fact that its a time-consuming task, I will try my best to just "plug back" the old backend with the new frontend. ## Files Being Updated Some files received PR's while the New Frontend was being developed. Ergo, I copy pasted the files changed (such as manage.js in clans or join.js). * Test Server Time! ## FrontEnd Changes ### Login Username When logged in, we should be able to see the username's name in the navbar and when hovering on it, settings such as change email, password, etc appear. ## BackEnd Changes ### Banners in account and clan pages Banners have been blocked from all account and clan pages since these are more technical forms which don't need vibrant images at the start of the page. ## Discord and Mongo out After doing enough testing locally, I believe its time I start testing on the actual test server. Ergo, the original passport strategy and values are coming back. Also because the test server can't run with these current settings and currently the leaderboards only work on the new website (which only runs on the test server atm). * Extractor env Independence Extractor.js does not use the env files anymore so its API calls do not produce errors while in the test server. Needs to be changed in the future (added a TODO to remember) * extractor.js env and error handling ### dotenv and extractor.js Extractor js now uses the env configuration on its API calls but also features its own default values in case they arent specified in the ENV. ### Error Handling All extractor.js calls now can handle errors and not break the whole application/website. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Test Server Commit ### Explanation This commit will not have a message about what has been changed since its being done just to test on the test server. This means I'll be changing small lines of code, commiting and then building the test server, seeing whats happening and repeat. * Fix Account POST Route Names Most of the forms in templates had an action/route that differed from what was set in express.js * Update POST Routes Post routes have been updated to the new user object used in the strategy * Show Username when logged in * Show Username when logged in * Show Username when logged in * Show Username when logged in * Show Username when logged in * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Test Server Commit * Clans Page ### Page and Upcoming Features The clans page has been created. Currently its a carbon copy of the leaderboards. However, I plan to give it more functions regarding seeing more clan details and their clan members when selecting/clicking a clan. ### Small Fixes Other files have received minor tweaks or comments to improve readability or documentation. * Individual Clan Pages ### Search Clans and learn more! Now the clan leaderboards have the option to search a clan's tag and find out more about said clan (such as its members, its description and so on). This is also accessible through the url /clans/* (* being the wildcard symbol, meaning any input), so if you type /clan/FEM, you'll find the FEM/Femboy clan. * Onboarding/Play Page ### Improved Onboarding The new /play page will be where users are redirected when they click DOWNLOAD on the navbar or any of the PLAY NOW buttons. On /play, users will see a short guide on how to install FAF and be able to deal with all the hurdles to play on FAF (steamlink, make sure to open game locally once, find the directory for SC:FA, why do we need to link your steam/gog account to FAF, etc) * Capitalization fixes + Backend ### index, contribution and AI pages These pages had incorrect capitalization (Such as Titles Being Capitalized Always). Now only names and the first letter are capitalized. ### account/express backend Axios is being undone due to a lack of local testing. The backend will now be tried to be done with the least amount of possible changes. * Flash Message + Play Page ### Flash Messages Now the website features flash messages! They can feature custom colors and have the capability of being shown in only specific pages. This matters because we dont want to place a "Dont register with a gmail account" flash message on every page but maybe only on a couple of pages such as /accounts/register for example. ### Play Page The play page has received a couple of fixes gramatically, added more resources to improve the process and a couple of styling changes thanks to the feedback received in the forum post. * Clan Management + Minor Styling Change ### Font Change Orbitron has been switched to Chakra Petch (thanks to Katharsas for finding this font) since it has better readabiliy yet maintains a futuristic style. ### Clan Routes The clan routes have been updated with the naming of data.attributes.token to just token and so on. * Clan Management + Minor Styling Change ### Font Change Orbitron has been switched to Chakra Petch (thanks to Katharsas for finding this font) since it has better readabiliy yet maintains a futuristic style. ### Clan Routes The clan routes have been updated with the naming of data.attributes.token to just token and so on. * Clan Management + Minor Styling Change ### Font Change Orbitron has been switched to Chakra Petch (thanks to Katharsas for finding this font) since it has better readabiliy yet maintains a futuristic style. ### Clan Routes The clan routes have been updated with the naming of data.attributes.token to just token and so on. * Undoing updates to backend ### Reverting to original Due to a lack of testing capabilities. All iniatives to update the backend have been been undone since the only available testing enviroment is the test server but its not good to rebuild it 100 times everytime I change a line of code. Ergo, will try to see how much can work with the outdated "request" library that is currently being in use" * Clan Pages, Steam and GOG link Guides # Clans ## Manage Received a styling update. Certain parts were removed (such as showing creation date or founder) since they seemed unnecessary for the clan settings part. Specially since these are shown when normally browsing a clan. ### Danger Zone Received a red background color and some wording changes to make it clearer how these options were final and not meant to fooled around with. ## create, accept_invite.pug Both received small minor styling changes. # Onboarding/Steam and GOG linking Both pages received a glow up with the inclusion of the guides with pictures to it. Making the steam and gog linking process much more streamlined for our users. * Clan Management + Register ## Clan Management I'm currently trying to improve the invitation process to become easier (copying the inviting link to the user after they create the invitation). ## Clan Pages Have had an increased setTimeout (from 100ms to 1000ms) to see if that works in the test server. ## Register Received minor changes in styling and HTML placing to see if it fixes the register button. * Home Page + Newshub ### Index The <a> tag in the Play Now button is now just as big as its button (was as wide as the whole screen, creating an invisible button link) ### Newshub The updated newshub (and other changes done to it in the develop br…
- Loading branch information
4 people
authored
Dec 29, 2022
1 parent
58dc374
commit e150043