mobile issues

Author: Finnegan Cappelli

assets/css/styles.css

@@ -240,16 +240,7 @@ ul {
 }
 
 @media(max-width:768px) {
-    html, body {
-        margin: 0;
-        padding: 0;
-        width: 100%;
-        overflow-x: hidden;
-      }
 
-      .background-container {
-        padding-top: calc(1em + 40px);
-    }
     .hamburger {
         display: block;
         z-index: 1;
@@ -266,24 +257,20 @@ ul {
     }
 
     .navigation {
-        position: fixed;
-        top: 0;
-        left: 0;
-        width: 100%;
-        z-index: 1000;
-        box-sizing: border-box;
+        position: relative;
+        top: 0px;
     }
 
     .navigation-menu {
         position: fixed;
-        right: -100%;
+        right: -110%;
         top: 0px;
         gap: 0;
         margin: 0px;
         flex-direction: column;
         background: rgba(0,0,0,70%);
         width: 100%;
-        height: 30%;
+        height: 35%;
         text-align: center;
         transition: 0.5s;
     }
@@ -317,6 +304,10 @@ ul {
     text-align: left;
 }
 
+.rules-list {
+    text-align: left;
+}
+
 .sponsors {
     display: flex;
     text-align: center;

assets/css/styles.css.map

@@ -67,8 +67,7 @@ <h4>Theme</h4>
               </section>
               <section class="rules">
                 <h4>RITSEC CTF 2025 General Rules</h4>
-                <h6>by RITSEC</h6>
-                <ol>
+                <ol class="rules-list">
                   <li>There should be no cooperation between teams. Sharing flags, hints, or any other information about a challenge with anyone other than your team or a CTF organizer during the CTF is prohibited.</li>
                   <li>Do not direct message challenge authors in any attempt to receive hints and other information about the challenges. All communication will be through the RITSEC CTF Discord server. If you believe that a challenge is down or broken you can state it in the relevant channel.</li>
                   <li>Do not attack the CTF or RITSEC infrastructure. This includes the webservers running the CTF engine, the challenge servers, any devices on the RIT network, and any other services used to run the CTF. If you aren't sure if you should be accessing something, ask a CTF organizer.</li>