Fix list spacing and miss-alignment of green and red icons

Author: rosalieper

src/components/Pages/HostingPolicy.vue

@@ -8,7 +8,7 @@
           <p>This policy defines Wikimedia Deutschland’s (WMDE) expectations and criteria for hosting on Wikibase Cloud. It explains what kinds of datasets and use cases are supported by WMDE and how those decisions are made and implemented.</p>
           <p>The policy exists to ensure that Wikibase Cloud technical and financial resources, as well as staff capacity are used responsibly, intentionally, in alignment with WMDE’s mission. Wikibase Cloud is not intended to be a generic free hosting service for any purpose. The policy helps us maintain visibility into how the platform is used and provides a framework to support and encourage use cases aligned with the role we want Wikibase Cloud to play in the Wikibase Ecosystem, and to address cases that clearly fall outside that role.</p>
           <h3 class="mb-3 mt-6" id="target-audience">1.1 Target Audience</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>Primary audience: the <a class="font-weight-bold font-italic" href="#review-committee">Review Committee</a> responsible for reviewing and approving Wikibase Cloud hosting requests for continued use. The policy provides a shared framework for making consistent, transparent decisions grounded in mission alignment, resource realities, and inclusivity goals.</li>
             <li>Secondary audience: <span class="font-weight-bold">Wikibase Cloud's current and prospective users</span>, who can use this document to understand the reasoning behind WMDE’s hosting criteria and to self-assess whether their use case is likely to be accepted.</li>
           </ul>
@@ -59,7 +59,7 @@
           <p><span class="font-weight-bold">If after discussion the committee cannot reach a shared decision,</span> this indicates that certain criteria are not defined clearly enough. In such cases, the Review Committee will initiate clarification of the hosting policy before proceeding.</p>
           <h3 class="mb-3" id="prerequisites">3.1 Prerequisites</h3>
           <p>The following conditions must be satisfied before an instance can be hosted on Wikibase Cloud. These conditions are non-negotiable and cannot be offset by positive signals.</p>
-          <h4 class="mb-3" id="required-conditions"><v-icon color="green">mdi-circle</v-icon> Required Conditions (must be true)</h4>
+          <h4 class="mb-3 align-center d-flex" id="required-conditions"><v-icon color="green">mdi-circle</v-icon> Required Conditions (must be true)</h4>
           <p>These conditions must be met for an instance to be eligible for hosting.</p>
           <ul>
             <li>All fields of the <a class="font-italic" href="#wiki-profile">Wiki Profile</a> are complete, providing sufficient detail for the Review Committee to evaluate the intended use.</li>
@@ -69,7 +69,7 @@
             <li>The structured data is in the public domain or released under CC-0.</li>
             <li>The license for the text in other namespaces allows commercial and non-commercial use and derivatives (we recommend using the conformant licenses <a href="https://opendefinition.org/licenses/">from this list</a>).</li>
           </ul>
-          <h4 class="mt-4 mb-3" id="disqualifying-conditions"><v-icon color="red">mdi-circle</v-icon> Disqualifying Conditions (must not be true)</h4>
+          <h4 class="align-center d-flex mt-4 mb-3" id="disqualifying-conditions"><v-icon color="red">mdi-circle</v-icon> Disqualifying Conditions (must not be true)</h4>
           <p>If any of the following conditions apply, the instance cannot be hosted.</p>
           <ul class="mb-4">
             <li>Any indication that the dataset or behaviour may violate or already violates the <a href="/terms-of-use">Terms of Use</a> (e.g., copyright violations, prohibited content, abusive behavior, harassment, privacy violations). <v-icon color="orange">mdi-alert</v-icon> Violations of the Terms of Use are governed exclusively by the Terms of Use and are not subject to the procedures described in this policy.</li>
@@ -99,7 +99,7 @@
               </ul>
             </v-alert>
           </div>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>
               The dataset is only intended to be used by the contributing individual or organization with no clear external audience (people or groups who meaningfully benefit from accessing or reusing this data), including use cases that support purely internal workflows, private organisational processes, or personal documentation, like internal CRM systems, business asset management. <br />The <u>exceptions</u> that do not produce this concerning signal are:
               <ul>
@@ -133,7 +133,7 @@
             <li>take steps to meet the <a class="font-italic" href="#hosting-criteria">Hosting Criteria</a>.</li>
           </ul>
           <h3 class="mb-3" id="review">4.3 Review</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>The <a class="font-italic" href="#review-committee">Review Committee</a>  reviews new applications on an ongoing basis, subject to the availability of its members.</li>
             <li>Each reviewer evaluates the use case independently against the <a class="font-italic" href="#hosting-criteria">Hosting Criteria</a>, noting the situations where essential information is missing or unclear.</li>
             <li>
@@ -192,8 +192,6 @@
                 <li>Is it intended for learning, experimentation, or something else?</li>
               </ul>
             </li>
-          </ul>
-          <ul>
             <li>
               <span class="font-weight-bold">Description of the dataset</span> (for projects intended for sharing and reuse, and for data staging)
               <ul>
@@ -204,17 +202,13 @@
                 <li>Perceived contribution to knowledge equity through data (if any)</li>
               </ul>
             </li>
-          </ul>
-          <ul>
             <li>
               <span class="font-weight-bold">Intended audience</span> (for projects intended for sharing and reuse)
               <ul>
                 <li>Who is expected to benefit from this data?</li>
                 <li>Potential application and tools that will be built on top of it</li>
               </ul>
             </li>
-          </ul>
-          <ul>
             <li>
               <span class="font-weight-bold">Contributor information</span>
               <ul>
@@ -228,12 +222,12 @@
           <h2 class="mt-7 mb-3" id="transparency-and-communication">5. Transparency and Communication</h2>
           <p>We aim to make hosting decisions clear, predictable, and respectful for all applicants.</p>
           <h3 class="mb-3" id="communication-of-decisions-to-applicants">5.1 Communication of Decisions to Applicants</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>Applicants receive a written decision summarizing the Review Committee’s assessment.</li>
             <li>When an instance is not accepted, the decision references relevant criteria, provides the minimum necessary reasoning for suspension without revealing internal deliberations, and any actions required to bring the instance into compliance.</li>
           </ul>
           <h3 class="mb-3" id="public-log-of-decisions">5.2 Public Log of Decisions</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>To support transparency and trust, WMDE will maintain a public log summarizing hosting decisions made by the Review Committee. Its purpose is to help the community understand how the policy is applied in practice.</li>
             <li>Sensitive or private information will not be published.</li>
           </ul>
@@ -245,7 +239,7 @@
           <h2 class="mt-7 mb-3" id="policy-revision-and-updates">6. Policy Revision and Updates</h2>
           <p>To ensure this policy remains accurate, effective, and aligned with WMDE’s mission and operational realities, it will be revised and updated on a regular basis.</p>
           <h3 class="mb-3" id="revision-cycle">6.1 Revision Cycle</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>
               The policy will undergo a formal revision <span class="font-weight-bold">at least once per year</span>, or sooner if:
               <ul>
@@ -257,25 +251,25 @@
             <li>Interim updates may be made if issues are identified during application reviews, re‑evaluations or appeals.</li>
           </ul>
           <h3 class="mb-3" id="responsible-parties">6.2 Responsible Parties</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>The Review Committee performs the policy revision.</li>
             <li>Community members may be consulted on proposed updates, especially when changes affect expectations for contributors or project eligibility.</li>
           </ul>
           <h3 class="mb-3" id="update-process">6.3 Update Process</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>Proposed changes are drafted by the Review Committee based on identified needs, operational learnings, or feedback.</li>
             <li>Draft updates are shared internally and externally for review and alignment.</li>
             <li>Once approved, updates are published on the relevant documentation pages.</li>
             <li>A summary of changes is added to the public decision log, ensuring transparency and traceability.</li>
           </ul>
           <h3 class="mb-3" id="previously-suspended-instances">6.4 Previously Suspended Instances</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>Instances suspended under an earlier version of this policy are not automatically re‑evaluated retrospectively.</li>
             <li>However, users may submit an appeal requesting a new review.</li>
             <li>Appeals for previously suspended instances are assessed according to the updated policy</li>
           </ul>
           <h3 class="mb-3" id="versioning">6.5 Versioning</h3>
-          <ul class="mb-3">
+          <ul class="mb-4">
             <li>Major outdated versions are archived but remain accessible for reference.</li>
           </ul>
         </v-col>
@@ -287,6 +281,5 @@
 <script>
 export default {
   name: 'HostingPolicy',
-  computed: {},
 }
 </script>