remove: public retro board from /wiki

wiki/content/accounting-workflow.php

@@ -1,5 +1,5 @@
 <section id="accounting-workflow">
-    <h2 class="heading-1">13. Accounting Workflow</h2>
+    <h2 class="heading-1">12. Accounting Workflow</h2>
     <p>The name of the game is "Fill-in the Yellow Rectangles".</p>
     <img src="imgs/accounting-workflow.png">
 </section>

wiki/content/branding-workflow.php

@@ -1,4 +1,4 @@
 <section id="branding-workflow">
-    <h2 class="heading-1">11. Branding Workflow</h2>
+    <h2 class="heading-1">10. Branding Workflow</h2>
     <p>Our creative process is documented in detail in <a data-before="plat" href="https://polyatlas.wiki" target="_blank">Poly Atlas</a>, our free guide to the Branding process.</p>
 </section>

wiki/content/development-workflow.php

@@ -1,6 +1,6 @@
 <section id="development-workflow">
-    <h2 class="heading-1">12. Development Workflow</h2>
-    <h3 class="heading-2">12.1. Website project set-up:</h3>
+    <h2 class="heading-1">11. Development Workflow</h2>
+    <h3 class="heading-2">11.1. Website project set-up:</h3>
     <ol class="hanging-list">
         <li>Create Github repository</li>
         <li>Buy web domain</li>
@@ -19,7 +19,7 @@
         <li>Add Poly Cookies</li>
         <li>Create and add Favicon system</li>
     </ol>
-    <h3 class="heading-2">12.2. Prefixes conventions on Github commits</h3>
+    <h3 class="heading-2">11.2. Prefixes conventions on Github commits</h3>
     <ul class="hanging-list">
         <li><strong>add:</strong> Used when adding new features, functionalities, or content to the project.  <i>"add: contact form to the website."</i></li>
         <li><strong>fix:</strong> Employed when correcting bugs, errors, or issues within the project.  <i>"fix: alignment of accordion icons."</i></li>

wiki/content/getting-paid.php

@@ -1,13 +1,13 @@
 <section id="getting-paid">
-<h2 class="heading-1">8. Getting Paid</h2>
-<h3 class="heading-2">8.1. When will I get paid?</h3>
+<h2 class="heading-1">7. Getting Paid</h2>
+<h3 class="heading-2">7.1. When will I get paid?</h3>
 <p>Our internal deadline to process payments is 10th day of every month. However, it is possible for some payments related to specific projects to be processed every 14 days.</p>
-<h3 class="heading-2">8.2. How will I get paid?</h3>
+<h3 class="heading-2">7.2. How will I get paid?</h3>
 <p>Once you’ve started working in our team you must send an email to <a href="mailto:[email protected]" target="_blank">accounting@polyfen.com</a> with the corresponding details of one of the payment methods we approve.</p>
 <p>Approved payment methods:</p>
 <ul class="hanging-list arrow-bullet">
     <li><a data-before="wise" href="https://wise.com" target="_blank">Wise</a></li>
     <li>Bank Account Transfer (selected countries)</li>
 </ul>
-<p>For any requests about changing your payment method please contact<br> ✉️ <a href="mailto:"[email protected]">[email protected]</a>.</p>
+<p>For any requests about changing your payment method please contact<br> ✉️ <a href="mailto:[email protected]">accounting@polyfen.com</a>.</p>
 </section>

wiki/content/google-drive.php

@@ -1,5 +1,5 @@
 <section id="google-drive">
-    <h2 class="heading-1">10. Google Drive</h2>
+    <h2 class="heading-1">9. Google Drive</h2>
     <iframe style="border: 1px solid rgba(0, 0, 0, 0.1);" width="800" height="450" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Ffile%2F1Va1EE7o5DLbHGT8LNv5xq%2FGoogle-Drive%3Ftype%3Dwhiteboard%26node-id%3D8%253A541%26t%3D8XWj1bU7xBRCsBHY-1" allowfullscreen></iframe>
     <p><a href="https://www.figma.com/file/1Va1EE7o5DLbHGT8LNv5xq/Google-Drive?type=whiteboard&node-id=8%3A541&t=8XWj1bU7xBRCsBHY-1" target="_blank">Google Drive</a> (figma file)</p>
 </section>

wiki/content/naming-conventions.php

@@ -1,6 +1,6 @@
 <section id="naming-conventions">
-    <h2 class="heading-1">5. Naming Conventions</h2>
-    <h3 class="heading-2" id="client-codes">5.1. Client Codes</h3>
+    <h2 class="heading-1">4. Naming Conventions</h2>
+    <h3 class="heading-2" id="client-codes">4.1. Client Codes</h3>
     <p>We organize all of our work into projects and those projects are groups by their corresponding client.</p>
     <p>To facilitate our organization and file naming we create a 2-4 letters shortcode to reference each client.</p>
     <p>All internal projects are referenced with Client Codes as well:</p>
@@ -13,7 +13,7 @@
         <li data-marker="plkt">Polykit › <strong>PLKT</strong></li>
         <li data-marker="plpr">Polypress › <strong>PLPR</strong></li>
     </ul>
-    <h3 class="heading-2" id="project-types">5.2. Project Types</h3>
+    <h3 class="heading-2" id="project-types">4.2. Project Types</h3>
     <ul class="hanging-list arrow-bullet">
         <li><strong>Branding</strong></li>
         <li><strong>Web</strong></li>

wiki/content/projects-and-tasks.php

@@ -1,9 +1,9 @@
 <section id="projects-and-tasks">
-    <h2 class="heading-1">6. Projects &amp; Tasks</h2>
+    <h2 class="heading-1">5. Projects &amp; Tasks</h2>
     <p>Asana and Clockify projects follow the convention <a data-emoji="anchor" href="#client-codes">[Client Code]</a> › <a data-emoji="anchor" href="#project-types">[Project Type]</a>.</p>
     
     <p>There are 5 stages in the workflow of any task.</p>
-    <h3 class="heading-2" id="backlog">6.1. Backlog</h3>
+    <h3 class="heading-2" id="backlog">5.1. Backlog</h3>
     <p>We identify a requirement and add it to Asana as a task following SMART task practices:</p>
     <ul class="hanging-list arrow-bullet">
         <li><strong>Specific</strong></li>
@@ -12,14 +12,14 @@
         <li><strong>Relevant</strong></li>
         <li><strong>Time-bound</strong></li>
     </ul>
-    <h3 class="heading-2" id="to-do">6.2. To Do</h3>
+    <h3 class="heading-2" id="to-do">5.2. To Do</h3>
     <p>All backlog tasks that were selected for the present <a data-emoji="anchor" href="#sprints">Sprint</a>.</p>
-    <h3 class="heading-2" id="in-progress">6.3. In Progress</h3>
+    <h3 class="heading-2" id="in-progress">5.3. In Progress</h3>
     <p>One you start work on a specific task, the first thing to do is set its status as "In Progress" to let the rest of the team know what's being worked on.</p>
-    <h3 class="heading-2" id="for-review">6.4. For Review</h3>
+    <h3 class="heading-2" id="for-review">5.4. For Review</h3>
     <p>After you consider your task is complete, add a comment with the total amount of hours worked on the task, then change the task status to "For Review" and assign the task to your reporter.</p>
-    <h3 class="heading-2" id="complete">6.5. Complete</h3>
+    <h3 class="heading-2" id="complete">5.5. Complete</h3>
     <p>After your task is reviewed by a Reporter and approved it will be moved to the "Complete" column.</p>
-    <h3 class="heading-2" id="archived">6.6. Archived</h3>
+    <h3 class="heading-2" id="archived">5.6. Archived</h3>
     <p>Once a week, when doing the transition between Sprint cycles, the tasks that are in the "Complete" column will be archived.</p>
 </section>

wiki/content/team-messaging.php

@@ -1,14 +1,14 @@
 <section id="team-messaging">
-<h2 class="heading-1">4. Team Messaging</h2>
-<h3 class="heading-2">4.1. House Rules</h3>
+<h2 class="heading-1">3. Team Messaging</h2>
+<h3 class="heading-2">3.1. House Rules</h3>
 <ol class="hanging-list">
     <li>Be respectful and considerate.</li>
     <li>Use appropriate channels. If you don't know where to post a message, then you can ask anyone for clarification via DM (direct message) 
         or you can post your question in our <span data-before="slack" class="data-span">help</span> channel.</li>
     <li>When discussing times and dates be sure to clarify which timezone you're referring to.</li>
     <li>If you have any suggestions for our rules we encourage you to participate and let us know how we can make this better for everyone.</li>
 </ol>
-<h3 class="heading-2">4.2. Channels</h3>
+<h3 class="heading-2">3.2. Channels</h3>
 <h4 class="heading-3">General</h4>
 <ul class="wiki-team_messaging-general hanging-list">
     <li><strong>#announcements</strong><br>

wiki/content/time-off.php

@@ -1,5 +1,5 @@
 <section id="time-off">
-<h2 class="heading-1">9. Time Off</h2>
+<h2 class="heading-1">8. Time Off</h2>
 <p>You are able to take any vacation, holidays, and time off as you desire.</p>
 <p>All we ask is that you let the rest of the team know with a reasonable amount of time ahead when possible.</p>
 </section>

wiki/content/time-tracking.php

@@ -1,5 +1,5 @@
 <section id="time-tracking">
-    <h2 class="heading-1">7. Time Tracking</h2>
+    <h2 class="heading-1">6. Time Tracking</h2>
     <p>Work tracked in Clockify should have the same name as the corresponding Asana task.</p>
     <p>If there is no related Asana task, feel free to name the timelog at your will.</p>
     <p>However, there are two things that must be carefully set:</p>

wiki/index.php

@@ -25,29 +25,28 @@
         <ul class="toc">
             <li><a href="#tech-stack" class="caption">1. Tech stack</a></li>
             <li><a href="#sprints" class="caption">2. Sprints</a></li>
-            <li><a href="#retro" class="caption">3. Retro</a></li>
-            <li><a href="#team-messaging" class="caption">4. Team Messaging</a></li>
-            <li><a href="#naming-conventions" class="caption">5. Naming Conventions</a></li>
+            <li><a href="#team-messaging" class="caption">3. Team Messaging</a></li>
+            <li><a href="#naming-conventions" class="caption">4. Naming Conventions</a></li>
             <ul>
-                <li><a href="#client-codes" class="caption">5.1. Client Codes</a></li>
-                <li><a href="#project-types" class="caption">5.2. Project Types</a></li>
+                <li><a href="#client-codes" class="caption">4.1. Client Codes</a></li>
+                <li><a href="#project-types" class="caption">4.2. Project Types</a></li>
             </ul>
-            <li><a href="#projects-and-tasks" class="caption">6. Projects &amp; Tasks</a></li>
+            <li><a href="#projects-and-tasks" class="caption">5. Projects &amp; Tasks</a></li>
             <ul>
-                <li><a href="#backlog" class="caption">6.1. Backlog</a></li>
-                <li><a href="#to-do" class="caption">6.2. To Do</a></li>
-                <li><a href="#in-progress" class="caption">6.3. In Progress</a></li>
-                <li><a href="#for-review" class="caption">6.4. For Review</a></li>
-                <li><a href="#complete" class="caption">6.5. Complete</a></li>
-                <li><a href="#archived" class="caption">6.6. Archived</a></li>
+                <li><a href="#backlog" class="caption">5.1. Backlog</a></li>
+                <li><a href="#to-do" class="caption">5.2. To Do</a></li>
+                <li><a href="#in-progress" class="caption">5.3. In Progress</a></li>
+                <li><a href="#for-review" class="caption">5.4. For Review</a></li>
+                <li><a href="#complete" class="caption">5.5. Complete</a></li>
+                <li><a href="#archived" class="caption">5.6. Archived</a></li>
             </ul>
-            <li><a href="#time-tracking" class="caption">7. Time tracking</a></li>
-            <li><a href="#getting-paid" class="caption">8. Getting paid</a></li>
-            <li><a href="#time-off" class="caption">9. Time off</a></li>
-            <li><a href="#google-drive" class="caption">10. Google Drive</a></li>
-            <li><a href="#branding-workflow" class="caption">11. Branding workflow</a></li>
-            <li><a href="#development-workflow" class="caption">12. Development workflow</a></li>
-            <li><a href="#accounting-workflow" class="caption">13. Accounting workflow</a></li>
+            <li><a href="#time-tracking" class="caption">6. Time tracking</a></li>
+            <li><a href="#getting-paid" class="caption">7. Getting paid</a></li>
+            <li><a href="#time-off" class="caption">8. Time off</a></li>
+            <li><a href="#google-drive" class="caption">9. Google Drive</a></li>
+            <li><a href="#branding-workflow" class="caption">10. Branding workflow</a></li>
+            <li><a href="#development-workflow" class="caption">11. Development workflow</a></li>
+            <li><a href="#accounting-workflow" class="caption">12. Accounting workflow</a></li>
         </ul>
     </nav>
     <main class="sub-sites"> 
@@ -64,10 +63,6 @@
         <?php include 'content/sprints.php';?>
         <!-- INCLUDE SPRINTS.PHP end -->
         <hr>
-        <!-- INCLUDE RETRO.PHP start -->
-        <?php include 'content/retro.php';?>
-        <!-- INCLUDE RETRO.PHP end -->
-        <hr>
         <!-- INCLUDE TEAM-MESSAGING.PHP start -->
         <?php include 'content/team-messaging.php';?>
         <!-- INCLUDE TEAM-MESSAGING.PHP end -->