article uses article css

src/diary/entries/201003

@@ -15,5 +15,3 @@ bottle, css, git, html, regex, regular expressions, website<br>
 <li>Pythex @ https://pythex.org/ is useful for checking whether your regular expression will catch your target strings</li>
 <li>First command line git merge. I usually do it on the website. It's really simple - switch to the branch you're merging the second branch into, type 'git merge second-branch' (second-branch = name of the second branch obviously), and fix any conflicts.</li>
 </ul>
-<br>
-<br>

src/diary/entries/raw/entries/200918

@@ -1,6 +1,34 @@
-<h1>5 my favorite GDC talks </h1>
+<h1>my favorite GDC talks </h1>
 september 18, 2020<br>
 <br>
 I really should be keeping a list of these with descriptions, so why not keep them in an article?<br>
 <br>
-Work on it later.<br>
+<a href="https://www.youtube.com/watch?v=UJiv14uPOac">Empathizing with Steam: How People Shop for Your Game by Chris Zukowski (2020)</a> - tips for how to design your Steam store page based on Zukowski's screenshare and shopping diary observations of ordinary people shopping on Steam
+<ul>
+<li>Essentially, make your gameplay genre absolutely clear within the first 4 screenshots and in the short description so that people will wishlist your game to buy during a Steam sale.</li>
+<li>first 4 images are shown when hovering over thumbnail in Steam. Make them represent the pillars of your gameplay, so the genre is clear.</li>
+<li>don't try to coerce new audiences into trying your game. try to find your audience and show them exactly what they are looking for.
+<li>include UI in screenshots, so gamers can decipher the genre and some gameplay mechanics</li>
+<li>Gamers naturally compare new games with the leading games of their genres to decide whether they will enjoy it.</li>
+<li>indie romance authors (who compete on a market of 8 million vs. steam's 40 thousand) use clear visual language in their coverart: tartan kilt + sword + distant castle = highland romance; animal behind a hunk = shapeshifter romance; woman in front of group of hunks = reverse harem. So a reader who sees a cover with multiple guys and a wolf, she knows it's a reverse harem of shape-shifting wolf boys without any descriptions or trailers.</li>
+<li>applying the wisdom of the romance authors, understand your audience's genre interests as sub-sub-sub-genres and make your genre crystal clear in your store page.</li>
+<li>Apply the tropes of your genre. The FPS coverart guy with the gun on all CoD and BF games, the two Street Fighter healthbars on the top of any fighter game</li>
+<li>Part 4 - How to manage a Steam sale</li>
+<li>People check their wishlist during sales, looking for discounts.</li>
+<li>People don't remember why they wishlisted games, so your page must look fresh even to your wishlist crew. Before a sale, post an update, theme your capsule image, post an announcement, upload a small patch, and comment in the forums.</li>
+<li>People remember games that are always on sale. Frequent sales increase familiarity.</li>
+<li>Power users use gg.deals or steamdb to track historic lows. Strategically staircase your way down over time. Coincide your all-time-lows with Big Steam Sales. Harness the fear of missing out.</li>
+<li>How to get from wishlist to cart</li>
+<li>Before clicking 'buy,' they check developer and publisher for someone they recognize or trust. They check 'more from this studio' to check familiarity with the dev's other games.</li>
+<li>Release more games to build this trust and familiarity.</li>
+<li>They check the 'relevant to you' bar to see if the genre matches games they've played and that friends with similar taste also like the game.</li>
+<li>How to manage your sales pricing</li>
+<li>How to get from cart to library</li>
+<li>After loading cart, they ask their friends whether they should go for it.</li>
+<li>Your current customers have to become ambassadors to complete this purchase loop. Treat them well! </li>
+<li>Abandon cart recovery in other online retailers beckons shoppers back before the sale ends. Steam lacks this, potentially losing devs 10% in revenue - https://www.annexcloud.com/blog/31-shopping-cart-abandonment-statistics-for-2018/</li>
+<li>Do a second marketing push during the last day of a sale.</li>
+<li>5 - How to wishlisters into buyers</li>
+<li></li>
+</ul>
+<br>

src/diary/entries/raw/entries/201003

@@ -15,5 +15,3 @@ bottle, css, git, html, regex, regular expressions, website<br>
 <li>Pythex @ https://pythex.org/ is useful for checking whether your regular expression will catch your target strings</li>
 <li>First command line git merge. I usually do it on the website. It's really simple - switch to the branch you're merging the second branch into, type 'git merge second-branch' (second-branch = name of the second branch obviously), and fix any conflicts.</li>
 </ul>
-<br>
-<br>

src/index.py

@@ -140,7 +140,7 @@ def diary(page):
 @route('/diary/entries/<page:int>')
 def entry(page):
     """diary entry"""
-    info = {'css': 'diary', 'title': 'blessfrey - developer diary', 'year': datetime.datetime.now(), 'entry': retrieve_article(page), 'latest': list_headlines(sort_files(gather_files())[0:5]), 'page': page}
+    info = {'css': 'feature', 'title': 'blessfrey - developer diary', 'year': datetime.datetime.now(), 'entry': retrieve_article(page), 'latest': list_headlines(sort_files(gather_files())[0:5]), 'page': page}
     abs_app_dir_path = os.path.dirname(os.path.realpath(__file__))
     abs_views_path = os.path.join(abs_app_dir_path, 'views')
     TEMPLATE_PATH.insert(0, abs_views_path )

src/static/css/feature.css

@@ -150,7 +150,7 @@ mark {
 
 .diary-entry {
     grid-area: 3 / 2 / 7 / 3;
-    background-color: #Ff0000;
+    background-color: #ff0000;
     padding: 5px;
 }
 

src/views/feature.tpl

@@ -1,7 +1,4 @@
 % rebase('frame.tpl')
-
-   <div class="body-row"> </div>
-
 <!--left column-->
     
     <div class="diary-entry">
@@ -10,3 +7,5 @@
     </div>
 
 % include diary-boxes.tpl
+
+    <div class="footer-row"> </div>

src/views/frame.tpl

@@ -1,15 +1,26 @@
 <!DOCTYPE html>
 <html lang="en">
+
 <head>
 % include('header.tpl')
 </head>
+
 <body>
+
 <div class="grid">
+
 % include('logo-bar.tpl')
+
 % include('nav.tpl')
+
     <div class="body-row"> </div>
+
 {{!base}}
+
 </div>
+
 % include('footer.tpl')
+
 </body>
+
 </html>

src/views/logo-bar.tpl

@@ -1,5 +1,5 @@
-    <div class="whitespace">
+    <div class="whitespace"> </div>
-        blessfrey.me<br>
-    </div>
 
-    <div class="blessfrey-logo"></div>
+    <div class="blessfrey-logo">
+        <center>blessfrey.me</center><br>
+    </div>