Fix formatting in CoC views, urls and template

Code-Institute-Community · Jul 7, 2023 · 3774100 · 3774100
1 parent f52e868
commit 3774100
Show file tree

Hide file tree

Showing 3 changed files with 31 additions and 21 deletions.
diff --git a/home/views.py b/home/views.py
@@ -147,8 +147,9 @@ def test_404(request):
     response.status_code = 404
     return response
 
+
 def codeofconduct(request):
     """
         A view to show the hackathon code of conduct.
     """
-    return render(request, 'code-of-conduct.html')
+    return render(request, 'code-of-conduct.html')
diff --git a/resources/urls.py b/resources/urls.py
@@ -7,5 +7,4 @@
     path('delete/<int:resource_id>/', views.delete_resource,
          name='delete_resource'),
     path('edit/<int:resource_id>/', views.edit_resource, name='edit_resource'),
-
 ]
diff --git a/templates/code-of-conduct.html b/templates/code-of-conduct.html
@@ -6,29 +6,39 @@
 <div class="row my-4">
     <div class="col-12 text-center mb-3">
         <h1>CODE OF CONDUCT</h1>
-        <p class="mt-2">Here at Code Institute we want to create a safe and welcoming environment for all hackathon participants.
+        <p class="mt-2">Here at Code Institute we want to create a safe and welcoming environment for all hackathon
+            participants.
             It's important to keep open communication with your team throughout the hackathon, as suddenly dropping off
             without letting them know can impact their progress and motivation, and may lead to incomplete tasks and
             disorganization. By participating in this event, you agree to follow this code of conduct:</p>
 
-            <ol class="text-left">
-                <li>Be respectful and inclusive towards all other participants, facilitators, Hackteam, Staff or anyone else involved in the hackathon. Discriminatory language or behavior of any kind is not allowed.
-                </li>
-                <li>Only register if you can commit a minimum of 3 hours a day.</li>
-                <li>Keep in contact with your team. All project discussions should take place within the dedicated team Slack Channel. This way, our Hackathon Facilitators and Staff can stay up to date on your progress and offer support when needed. We want to make sure that everyone on the team is aware of all goings-on.
-                </li>
-                <li>We want to ensure that everyone on the team has a chance to participate and add their unique skills and perspectives. Let's work together to make sure everyone is included and valued. More experienced team members should keep in mind that some members may be less experienced, and may need extra support and guidance. By offering more time and assistance to those who may need it, we can ensure that everyone has an opportunity to grow their skills and contribute to the project. Remember, this is a team effort and we want to work together to achieve our goals rather than rushing ahead.
-                </li>
-                <li>If you need to drop off from the event before it ends, you must inform your team and the team facilitator. If you drop off without informing your team, you will be ineligible to participate in the next hackathon.
-                </li>
-                <li>If you witness or experience any behavior that violates this code of conduct, please report it immediately to your facilitator, the HackTeam or the Code Institute Community Team.</li>
-
-            </ol>
-            <p>By participating in a Code Institute Hackathon, you agree to abide by this code of conduct and any decisions made by Code Institute regarding violations of it.</p>
+        <ol class="text-left">
+            <li>Be respectful and inclusive towards all other participants, facilitators, Hackteam, Staff or anyone else
+                involved in the hackathon. Discriminatory language or behavior of any kind is not allowed.
+            </li>
+            <li>Only register if you can commit a minimum of 3 hours a day.</li>
+            <li>Keep in contact with your team. All project discussions should take place within the dedicated team
+                Slack Channel. This way, our Hackathon Facilitators and Staff can stay up to date on your progress and
+                offer support when needed. We want to make sure that everyone on the team is aware of all goings-on.
+            </li>
+            <li>We want to ensure that everyone on the team has a chance to participate and add their unique skills and
+                perspectives. Let's work together to make sure everyone is included and valued. More experienced team
+                members should keep in mind that some members may be less experienced, and may need extra support and
+                guidance. By offering more time and assistance to those who may need it, we can ensure that everyone has
+                an opportunity to grow their skills and contribute to the project. Remember, this is a team effort and
+                we want to work together to achieve our goals rather than rushing ahead.
+            </li>
+            <li>If you need to drop off from the event before it ends, you must inform your team and the team
+                facilitator. If you drop off without informing your team, you will be ineligible to participate in the
+                next hackathon.
+            </li>
+            <li>If you witness or experience any behavior that violates this code of conduct, please report it
+                immediately to your facilitator, the HackTeam or the Code Institute Community Team.</li>
+
+        </ol>
+        <p>By participating in a Code Institute Hackathon, you agree to abide by this code of conduct and any decisions
+            made by Code Institute regarding violations of it.</p>
     </div>
 </div>
 
-
-
-
-{% endblock %}
+{% endblock %}