+
+
+ new TwentyNineteen_Walker_Comment(),
+ 'avatar_size' => twentynineteen_get_avatar_size(),
+ 'short_ping' => true,
+ 'style' => 'ol',
+ )
+ );
+ ?>
+
+ sprintf(
+ '%1$s %2$s',
+ $prev_icon,
+ /* translators: Comments navigation link text. The secondary-text element is hidden on small screens. */
+ __( 'PreviousComments', 'twentynineteen' )
+ ),
+ 'next_text' => sprintf(
+ '%1$s %2$s',
+ /* translators: Comments navigation link text. The secondary-text element is hidden on small screens. */
+ __( 'NextComments', 'twentynineteen' ),
+ $next_icon
+ ),
+ )
+ );
+ endif;
+
+ // Show comment form at bottom if showing newest comments at the bottom.
+ if ( comments_open() && 'asc' === strtolower( get_option( 'comment_order', 'asc' ) ) ) :
+ ?>
+
+
+
+
+
+
+
+
+
+
diff --git a/wp-content/upgrade-temp-backup/themes/twentynineteen/contributing.txt b/wp-content/upgrade-temp-backup/themes/twentynineteen/contributing.txt
new file mode 100644
index 00000000..4cebefc2
--- /dev/null
+++ b/wp-content/upgrade-temp-backup/themes/twentynineteen/contributing.txt
@@ -0,0 +1,19 @@
+=== Contributing to Twenty Nineteen ===
+
+= Compiling SCSS =
+
+Twenty Nineteen relies on Sass, which allows us to more easily share code between multiple stylesheets (style.css, style-editor.css, etc.). To compile Sass files (.scss), use the built-in npm build tool. The build tool will make sure that your compiled CSS code stays in sync and has the correct formatting.
+
+Installation instructions
+
+1. Using a command line interface, go to the “twentynineteen” directory `cd /my-computer/local-wordpress-install/src/wp-content/themes/twentynineteen`.
+
+2. Type `npm install` into the command line, and press the [return] key, to install all Node.js dependencies.
+
+3. The dependencies may take a few minutes to download but once it completes, you’re done.
+
+Usage instructions
+
+1. After making a change to a .scss file, run `npm run build` from within the theme directory to build the CSS files with your new changes. You may need to run the build command twice to update style-rtl.css (because the RTL process might update from style.css before that is updated from Sass file changes).
+
+2. You can also “watch” the theme directory for Sass changes and rebuild the CSS anytime a change occurs by running: `npm run watch`.
diff --git a/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff b/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff
new file mode 100644
index 00000000..7f859ce2
Binary files /dev/null and b/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff differ
diff --git a/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff2 b/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff2
new file mode 100644
index 00000000..6651a428
Binary files /dev/null and b/wp-content/upgrade-temp-backup/themes/twentynineteen/fonts/NonBreakingSpaceOverride.woff2 differ
diff --git a/wp-content/upgrade-temp-backup/themes/twentynineteen/footer.php b/wp-content/upgrade-temp-backup/themes/twentynineteen/footer.php
new file mode 100644
index 00000000..28a5ee4d
--- /dev/null
+++ b/wp-content/upgrade-temp-backup/themes/twentynineteen/footer.php
@@ -0,0 +1,57 @@
+
+
+
+
+
+
+
+
+
+
+