thumb

copycat.py

@@ -0,0 +1,28 @@
+from glob import glob
+import os
+from shutil import copy2
+import frontmatter
+from pathlib import Path
+from PIL import Image
+
+
+
+# from frontmatter import frontmatter
+for folder in glob('projects/*'):
+    project = folder.replace('projects/', '')
+    with open(os.path.join(folder,project+'.md'), 'r') as f:
+            meta, content = frontmatter.parse(f.read()) 
+            if 'cover' in meta:
+                cover = meta.get('cover')
+                file = Path(f'static/img2/{cover}')
+                if file.is_file():
+                    try:
+                        with Image.open(file) as img:
+                            print(f'Ok im copying {cover} to {project}') 
+                            f, e = os.path.splitext(cover)
+                            img.save(os.path.join(folder, f + '.jpg'))
+                            img.convert('RGB')
+                            img.thumbnail((256,256))
+                            img.save(os.path.join(folder, 'thumb_' + cover), 'JPEG')
+                    except:
+                        print(f"Couldn't convert {cover}")

flask_boat.py

@@ -73,6 +73,35 @@ def render_home():
         f.write(render_template("home.html", **home))
         print('Rendered!')
 
+def render_home_thumb():
+    print('Rendering home with thumbnails')
+# with open('/home/kamo/public_html/render.html', 'w') as f:
+        # get the basic info of the website from the /contents/home.md file
+    meta, content = get_md_contents("home.md")
+    projects_list = []
+    for project in list_folders("./projects"):
+        project_info = get_md_contents(f"{project}.md",
+                                    f"./{projects}/{project}")[0]
+        project_date = datetime.strptime(project_info['date'], '%d/%m/%Y')
+        project_info['date'] = datetime.strftime(project_date, '%d %b, %y')
+        project_info['categories'].sort()
+
+        project_info['slug'] = project
+        projects_list.append(project_info)
+
+    projects_list.sort(reverse=True, key=lambda project: datetime.strptime(
+        project['date'], '%d %b, %y'))
+
+    # get the list of the projects, the functions, and the corpora
+    home = {
+        **meta,
+        "content": content,
+        "projects": projects_list
+    }
+    # f.write(render_template("home.html", **home))
+    # print('Rendered!')
+    return render_template("home2.html", **home)
+
 
 # FLASK APP
 
@@ -102,7 +131,8 @@ app.wsgi_app = PrefixMiddleware(app.wsgi_app, prefix='/soupboat/~kamo')
 # Homepage
 @app.route("/")
 def home_page():
-    return send_from_directory(app.root_path, 'render.html')
+    return render_home_thumb()
+    # return send_from_directory(app.root_path, 'render.html')
 
 
 # For generic pages we can include a common template and change only the contents

projects/chaotic-evil-puzzles/chaotic-evil-puzzles.md

@@ -11,7 +11,7 @@ categories:
   - Games
 ---
 
-## There are 100 lot boxes with 100 different jigsaw puzzles of 100 pieces.*  
+## There are 100 lot boxes with 100 different jigsaw puzzles of 100 pieces.*
 ![100 boxes compose the face of aymeric if seen from a precise point of view](https://hub.xpub.nl/soupboat/~kamo/static/img/100-boxes.jpg)
 _\* (exact quantities to be defined)_
 
@@ -22,39 +22,39 @@ Each puzzle is an A2 sized image displaying the works we did during this trimest
 
 _f.e. A puzzle could be the rules for an RPG; or the map of a bitsy game with some critical texts about gamification; a generated maze, a fan fiction, the glossary, the list of one sentence games, etc._
 
-In other words, the collection of puzzles will be a sort of inventory of our research framed in the form of jigsaw. 
+In other words, the collection of puzzles will be a sort of inventory of our research framed in the form of jigsaw.
 
 ## The pieces are scattered through all the loot boxes, in a way that each one contains parts of multiple puzzles.
 ![shuffle of the jiigsaw pieces](https://hub.xpub.nl/soupboat/~grgr/static/img/jigmix.png)
 
 This could be done in a meaningful way: the idea is not to have total random pieces, but legible fragments from each content.
 
-## When players buy the loot box they can compose the puzzle, but the result is a patchwork of different images. 
+## When players buy the loot box they can compose the puzzle, but the result is a patchwork of different images.
 ![in each loot box there is a patchwork of different puzzles](https://hub.xpub.nl/soupboat/~grgr/static/img/patchworks.png)
 
-If the puzzles have different images but the same pieces pattern, each loot box can have a complete puzzle, but with mixed pieces. In this way we can avoid the frustration that having an  incomplete jigsaw puzzle could cause.  
+If the puzzles have different images but the same pieces pattern, each loot box can have a complete puzzle, but with mixed pieces. In this way we can avoid the frustration that having an  incomplete jigsaw puzzle could cause.
 
-## On the website of SI17 the players can upload their fragments, and compose together an online version to complete all the jigsaw puzzles. 
+## On the website of SI17 the players can upload their fragments, and compose together an online version to complete all the jigsaw puzzles.
 ![demo web interface](https://hub.xpub.nl/soupboat/~kamo/static/img/puzzle-web.jpg)
 
-We can numerate or identify each piece of the puzzles with a code. This could be done when we generate the pattern of the puzzle with Python 👀. To upload a fragment of puzzle, the player is required to insert the code of the pieces, and maybe take a picture. In this way we can be sure that only who has the fragment can insert it online. 
+We can numerate or identify each piece of the puzzles with a code. This could be done when we generate the pattern of the puzzle with Python 👀. To upload a fragment of puzzle, the player is required to insert the code of the pieces, and maybe take a picture. In this way we can be sure that only who has the fragment can insert it online.
 
 
-## Optional feature: users can upload pictures of their fragments and we could have a collective documentation of the work. 
+## Optional feature: users can upload pictures of their fragments and we could have a collective documentation of the work.
 ![demo upload pictures](https://hub.xpub.nl/soupboat/~kamo/static/img/share-puzzle.jpg)
 _This is not unpaid work, it's participation_
 
-Nice feature for the website could be that you can see the digital version of the puzzle, but on mouse :hover we could show the pictures from the public. A puzzle of photos of puzzles. This could be challenging but funny to develop. 
+Nice feature for the website could be that you can see the digital version of the puzzle, but on mouse :hover we could show the pictures from the public. A puzzle of photos of puzzles. This could be challenging but funny to develop.
 
 ## On the website of SI17 there is a community section for exchanging the fragments and complete the puzzle
 ![demo xchange puzzle fragments](https://hub.xpub.nl/soupboat/~kamo/static/img/xchange-puzzle.jpg)
 
-The community section with users and exchange etc could be tricky, but we can stay as simple as possible and do it with Flask. The exchange section should exclude by design the speculation on the pieces or money. A fragment for a fragment. 
+The community section with users and exchange etc could be tricky, but we can stay as simple as possible and do it with Flask. The exchange section should exclude by design the speculation on the pieces or money. A fragment for a fragment.
 
 ## On the website of SI17 the public can access to the experiments, games and researches as well
 ![demo other contents on the website](https://hub.xpub.nl/soupboat/~grgr/static/img/lootbweb.png)
 
-In this way we can provide access to the contents such as the bitsy games, the karaoke video, the ruleset of our games, the reading list, etc. 
+In this way we can provide access to the contents such as the bitsy games, the karaoke video, the ruleset of our games, the reading list, etc.
 
 ### Risk / Benefit assessment
 
@@ -64,10 +64,10 @@ PROS
 + a lot of design
 + not to much code
 + use what we already have
-+ interesting interaction with the public 
-+ performative element ready for the launch 
++ interesting interaction with the public
++ performative element ready for the launch
 + multiple temporalities (individual puzzle, contents, shared puzzles)
-+ world building 
++ world building
 
 CONS:
 - not an API  👀
@@ -80,7 +80,7 @@ CONS:
 The process to make the puzzles could be easy as design - print - cut - shuffle - package, nothing more (+ website)
 
 ![box](https://hub.xpub.nl/soupboat/~grgr/static/img/puzzle-box.jpg)
-The loot box could provide a context and the instruction of the game, as well as the link to the website. 
+The loot box could provide a context and the instruction of the game, as well as the link to the website.
 
 
 ## Scenario
@@ -89,13 +89,13 @@ Mapping the chaotic evil puzzles in the through the different scenari
 
 ### of the form
 
-_scenario 1: The lootbox is a physical box that contains something_ 
+_scenario 1: The lootbox is a physical box that contains something_
 
 Fragments of several puzzles.
 
 ### of the feature
 
-_scenario 7: The items in the loot-box are complementary and it is necessary to connect with other loot-box owners in order to assemble the pieces together._ 
+_scenario 7: The items in the loot-box are complementary and it is necessary to connect with other loot-box owners in order to assemble the pieces together._
 
 There is a single player aspect and there is a collaborative aspect. These two components could be mediated by an online platform, such as the online shared puzzles, but could also work offline if people just combine the pieces of their loot boxes.
 
@@ -103,11 +103,11 @@ There is a single player aspect and there is a collaborative aspect. These two c
 
 _scenario 2: The loot box is a collection of the prototyped games (and researches!) we did so far curated in some kind of form_
 
-The jigsaw puzzle is just a form of encryption of our contents. A shared surface in which we can publish really different things such as a fan fiction, a board game, a link to a video karaoke or a videogame, an essay, the characters of a roleplaying game, etc. 
+The jigsaw puzzle is just a form of encryption of our contents. A shared surface in which we can publish really different things such as a fan fiction, a board game, a link to a video karaoke or a videogame, an essay, the characters of a roleplaying game, etc.
 
 _scenario 3: The loot box is a collection of mini-games + an ultimate game that has to be performed with other players that purcahsed the LB_
 
-There are several layers of playability and access: 
+There are several layers of playability and access:
 
 1. to solve the fragments (single player jigsaw)
 2. to access the contents (games, texts, etc. )
@@ -186,7 +186,7 @@ Thanks and see you sun ☀️
 - short term puzzles (link to multimedia contents, puzzle shards)
 - long term puzzles (hidden messages, 1 word in each puzzles and a secret sentence)
 - size and quantity
-- The jigsaw puzzles results should be secret? There would be much more mistery. Can we reveal only during the launch, but not on the loot boxes? Maybe is a compromise, but maybe is not necessary. Should we reveal them only in the website meanwhile they are completed? Could be.  
+- The jigsaw puzzles results should be secret? There would be much more mistery. Can we reveal only during the launch, but not on the loot boxes? Maybe is a compromise, but maybe is not necessary. Should we reveal them only in the website meanwhile they are completed? Could be.
 - [Generate Jigsaw Puzzle with python](https://github.com/jkenlooper/piecemaker)
 - [How To Laser Cut a Jigsaw Puzzle](https://www.youtube.com/watch?v=xqhOrY8unn4)
 - [Jigsaw puzzle generator](https://draradech.github.io/jigsaw/index.html)