#576 Created Support page skeleton #595
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked-waiting-for-further-changes
bug
bug-only-on-server-for-mobile-not-webpage
Bug-Report-After-Merge
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
further-changes-needed
future-problem-not-fixint-this-period
help wanted
invalid
last-week-issue-to-fix
library
low-priority
needs input
needs review
not-implemented.
project documentation
question
research
reviewed
Script
security
SQL
style
Team 1
Team 2
team leaders
test-creation
testing
topLevel
unassigned
Under-review
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K!595
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "#-576-support-page"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created a skeleton for the support page with main university links (portal and university websites).
Files changed:
by no means is the style of the page finalized. it's just a touch and should probably be changed later
Created Support page skeletonto #576- Created Support page skeleton#576- Created Support page skeletonto #576 Created Support page skeletonReview on #559
Whats done
Reviewed the cleanup of
for issue #576
Tested on Arch Linux using Brave and Firefox
* Running the code with NPM run
Inspected the following files
app.js:
* Indentation/code styling
* Clean
* No new additions (not an issue)
* General code quality
* *Improvements to add:
* None
* Issues:
* Once again, none noticed.
footer.js:

* Indentation/code styling
* Clean
* Comments
* No new additions (not an issue)
* General code quality:
* Improvements to add:
* I would like to see the text "FAQ(Placeholder)" in the footer to be changed to something like "Support and FAQ" or similar to signal that the site exists.
* Issues:
* Once again, none noticed.
Support.js:
* Indentation/code styling
* It follows prettier
* Comments
* A few added, but they are well placed and make up for quantity with quality... minus the "Please remove !! this is just a joke" part. That came off as too jokey a comment.
* General code quality:
* Improvements to add:
* Possible improvements could be to change the spacing between or turn the FQA text into buttons.
* And also, to make a text fold-out if the corresponding button is pressed.
* Issues:
* Update the comment to be something more fitting. But the section being commented on can stay.
Support.module.css:
* Indentation/code styling
* It follows prettier
* Comments
* No problems here either. They are fitting. However, just to be a little pedantic, I would like to see comments for ".support-page p" and ".support-item:last-child". With this, the whole CSS would be commented.
* General code quality:
* Improvements to add:
* Nothing, besides the comment thing.
* Issues:
* Again, the comment coverage problem. Besides that, not.
What needs to be done
* Update the "Please remove !! this is just a joke" comment.
* Give one basic comment for both ".support-page p" and ".support-item:last-child".
Conclusion
After the described things have been done. After that, it can be merged without a problem.
The small problems brought up are now fixed, and this PR can now be merged.