diff --git a/journals/constants.py b/journals/constants.py
index d8d394a5c1c70eaba9b0dd14311e18d26a40f07a..6c3bf17ca9d7470e5b8093a2cb26f628a99659d8 100644
--- a/journals/constants.py
+++ b/journals/constants.py
@@ -5,14 +5,18 @@ __license__ = "AGPL v3"
 # These are DOI's of the Journals, they are used as keys for the choicefield in `models.Journal`!
 SCIPOST_JOURNAL_PHYSICS = 'SciPostPhys'
 SCIPOST_JOURNAL_PHYSICS_SELECT = 'SciPostPhysSel'
+SCIPOST_JOURNAL_PHYSICS_COMMONS = 'SciPostPhysComm'
 SCIPOST_JOURNAL_PHYSICS_LECTURE_NOTES = 'SciPostPhysLectNotes'
 SCIPOST_JOURNAL_PHYSICS_PROC = 'SciPostPhysProc'
+SCIPOST_JOURNAL_PHYSICS_CODEBASES = 'SciPostPhysCodeb'
 
 # Journal open for submission
 SCIPOST_JOURNALS_SUBMIT = (
     (SCIPOST_JOURNAL_PHYSICS, 'SciPost Physics'),
+    (SCIPOST_JOURNAL_PHYSICS_COMMONS, 'SciPost Physics Commons'),
     (SCIPOST_JOURNAL_PHYSICS_LECTURE_NOTES, 'SciPost Physics Lecture Notes'),
-    (SCIPOST_JOURNAL_PHYSICS_PROC, 'SciPost Physics Proceedings')
+    (SCIPOST_JOURNAL_PHYSICS_PROC, 'SciPost Physics Proceedings'),
+    (SCIPOST_JOURNAL_PHYSICS_CODEBASES, 'SciPost Physics Codebases'),
 )
 
 # Journal closed for submission
diff --git a/journals/migrations/0047_auto_20181023_0829.py b/journals/migrations/0047_auto_20181023_0829.py
new file mode 100644
index 0000000000000000000000000000000000000000..8ed6780e37b06ac4f54bdd9b7a68ec627233d125
--- /dev/null
+++ b/journals/migrations/0047_auto_20181023_0829.py
@@ -0,0 +1,20 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.4 on 2018-10-23 06:29
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+    dependencies = [
+        ('journals', '0046_auto_20181020_2008'),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name='journal',
+            name='name',
+            field=models.CharField(choices=[('SciPostPhys', 'SciPost Physics'), ('SciPostPhysComm', 'SciPost Physics Commons'), ('SciPostPhysLectNotes', 'SciPost Physics Lecture Notes'), ('SciPostPhysProc', 'SciPost Physics Proceedings'), ('SciPostPhysCodeb', 'SciPost Physics Codebases'), ('SciPostPhysSel', 'SciPost Physics Select')], max_length=100, unique=True),
+        ),
+    ]
diff --git a/journals/templates/journals/journals.html b/journals/templates/journals/journals.html
index b215cf4d846a23bd84c2954728ca453db4d3f12e..af7f19e1b2b1941d152eaf36b5a35d5403c51962 100644
--- a/journals/templates/journals/journals.html
+++ b/journals/templates/journals/journals.html
@@ -64,14 +64,14 @@
   <h2><button class="btn btn-danger text-white mb-2 p-2" type="button" data-toggle="collapse" data-target="#WhereToSubmit" aria-expanded="false" aria-controls="WhereToSubmit"><strong>Help!</strong> Where should I submit?</button></h2>
   <div class="collapse" id="WhereToSubmit">
     <div class="card card-body">
-      <p>For <strong>Lecture Notes</strong>, <strong>Proceedings</strong> or <strong>Codebases/Datasets</strong>, the names say it all without ambiguity.</p>
+      <p>For <strong>Lecture Notes</strong>, <strong>Proceedings</strong> or <strong>Codebases</strong>, the names say it all without ambiguity.</p>
       <p>But what about your <strong>research results</strong>? Ask yourself these two questions:</p>
       <ul>
 	<li><em>Are these results exceptional in nature, in the sense that they represent a breakthrough or an achievement which clearly stands out?</em></li>
 	<li><em>Are you willing to make a special effort in conveying these results, in meeting the highest submission standards which we require, and in responding/reacting to any points raised under our toughest refereeing protocol?</em></li>
       </ul>
       <p>If you answered both questions in the affirmative, then consider submitting to <a href="{% url 'scipost:landing_page' 'SciPostPhys' %}">SciPost Physics</a>.</p>
-      <p>On the other hand, if your results represent a significant advance but you desire a simpler submission and refereeing process, then <a href="{% url 'scipost:landing_page' 'SciPostPhysAdv' %}">SciPost Physics Commons</a> will provide you with a more streamlined experience.</p>
+      <p>On the other hand, if your results represent a significant advance but you desire a simpler submission and refereeing process, then <a href="{% url 'scipost:landing_page' 'SciPostPhysComm' %}">SciPost Physics Commons</a> will provide you with a more streamlined experience.</p>
     </div>
   </div>
   <div class="card-deck">
@@ -89,7 +89,7 @@
     </div>
     <div class="card">
       <div class="card-header banner">
-	<h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysAdv' %}">SciPost Physics Commons</a>&nbsp;&nbsp;<em><small style="color: red;">New!</small></em></h1>
+	<h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysComm' %}">SciPost Physics Commons</a>&nbsp;&nbsp;<em><small style="color: red;">New!</small></em></h1>
       </div>
       <div class="card-body">
 	<p>SciPost Physics Commons is a premium-quality refereed Journal for the general field of Physics.</p>
@@ -122,15 +122,12 @@
     </div>
     <div class="card">
       <div class="card-header banner">
-	<h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysCoDat' %}">SciPost Physics Codebases and Datasets</a>&nbsp;&nbsp;<em><small style="color: red;">New!</small></em></h1>
+	<h1 class="m-0"><a href="{% url 'scipost:landing_page' 'SciPostPhysCodeb' %}">SciPost Physics Codebases</a>&nbsp;&nbsp;<em><small style="color: red;">New!</small></em></h1>
       </div>
       <div class="card-body">
-	<p>SciPost Phys. CoDat. is an innovative peer-reviewed publication venue for modern forms of scientific contributions:</p>
-	<ul>
-	  <li>reuseable codebases</li>
-	  <li>structured datasets</li>
-	</ul>
-	<p>Submissions undergo stringent peer-witnessed refereeing, with criteria tailored for this type of content; accepted manuscripts become full-fledged publications.</p>
+	<p>SciPost Physics Codebases is an innovative peer-reviewed publication venue for modern forms of scientific contributions which too often remains unrecognized: codes and algorithms at the heart of contemporary research.</p>
+	<p>This Journal offers proper recognition for code authors, in the form of fully-fledged citable publications.</p>
+	<p>Submissions undergo stringent peer-witnessed refereeing, with criteria tailored for this type of content.</p>
       </div>
     </div>
   </div>
diff --git a/scipost/static/scipost/2018_10_SciPost_Journals_plan.png b/scipost/static/scipost/2018_10_SciPost_Journals_plan.png
index 232fd2fe82656d0517e4e9f45003fed86ba68579..15b6b88d0edfcea5a765423dec530ada708f8b4c 100644
Binary files a/scipost/static/scipost/2018_10_SciPost_Journals_plan.png and b/scipost/static/scipost/2018_10_SciPost_Journals_plan.png differ
diff --git a/scipost/templates/scipost/PlanSciPost.html b/scipost/templates/scipost/PlanSciPost.html
index 61ec80ab31727707de15c548b8e0a55dac23b6b5..f48e270d885c0a0d0d89d83b3ebb64cdeab9c0e0 100644
--- a/scipost/templates/scipost/PlanSciPost.html
+++ b/scipost/templates/scipost/PlanSciPost.html
@@ -54,7 +54,7 @@
 	<div class="card-header"><strong>Support</strong></div>
 	<div class="card-body">
 	  <ul>
-	    <li>Sufficient <a href="{% url 'sponsors:sponsors' %}">Sponsorships</a> to cover the equivalent of one more full-time editorial staff in our team</li>
+	    <li>Sufficient <a href="{% url 'sponsors:sponsors' %}">Sponsorships</a> to cover the expected workflow (minimum of one more full-time editorial staff per new field)</li>
 	  </ul>
 	</div>
       </div>
diff --git a/submissions/migrations/0037_auto_20181023_0829.py b/submissions/migrations/0037_auto_20181023_0829.py
new file mode 100644
index 0000000000000000000000000000000000000000..64dd8dcb10fda999c084c018d644c0109819d59a
--- /dev/null
+++ b/submissions/migrations/0037_auto_20181023_0829.py
@@ -0,0 +1,20 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.4 on 2018-10-23 06:29
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+    dependencies = [
+        ('submissions', '0036_merge_20181002_1358'),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name='submission',
+            name='submitted_to_journal',
+            field=models.CharField(choices=[('SciPostPhys', 'SciPost Physics'), ('SciPostPhysComm', 'SciPost Physics Commons'), ('SciPostPhysLectNotes', 'SciPost Physics Lecture Notes'), ('SciPostPhysProc', 'SciPost Physics Proceedings'), ('SciPostPhysCodeb', 'SciPost Physics Codebases')], max_length=30, verbose_name='Journal to be submitted to'),
+        ),
+    ]