LGME: Adding in items.json for lab, fixing build-assets (#111)

* Adding in items.json for lab

* Syncing code with docs, adding banners to alerts

* Fixing alert

Author: switch180

.github/scripts/build-assets.py

@@ -73,6 +73,8 @@
 with ZipFile('battle-royale.zip', 'w') as workshop_zip:
 	for pyscript in glob.glob('./scripts/*.py'):
 		workshop_zip.write(pyscript)
+	for js_script in glob.glob('./scripts/*.json'):
+		workshop_zip.write(js_script)
 shutil.move(os.path.join(os.getcwd(), 'battle-royale.zip'), os.path.join(dest_root, 'assets', 'battle-royale.zip'))
 
 #Create Global Serverless ZIP

content/game-player-data/core-usage/Step2.en.md

@@ -13,6 +13,7 @@ The code you downloaded in the initial steps include a Python script in the **sc
 
 ```py
 import boto3
+
 dynamodb = boto3.client('dynamodb')
 
 try:
@@ -42,14 +43,14 @@ try:
             "ReadCapacityUnits": 1,
             "WriteCapacityUnits": 1
         }
-        )
-        print("Table 'battle-royale' created successfully.")
+    )
+    print("Table 'battle-royale' created successfully.")
 except Exception as e:
     print("Could not create table. Error:")
     print(e)
 ```
 
-::alert[Edit **scripts/create_table.py**, set both `ReadCapacityUnits` and `WriteCapacityUnits` to **100** for *battle-royale* table.]
+::alert[Edit **scripts/create_table.py**, set both `ReadCapacityUnits` and `WriteCapacityUnits` to **100** for *battle-royale* table and save the file.]{header="Change the capacity units."}
 
 The preceding script uses the [CreateTable](https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_CreateTable.html) operation using [Boto 3](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html), the AWS SDK for Python. The operation declares two attribute definitions, which are typed attributes to be used in the primary key. Though DynamoDB is [schemaless](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/SQLtoNoSQL.CreateTable.html), you must declare the names and types of attributes that are used for primary keys. The attributes must be included on every item that is written to the table and thus must be specified as you are creating a table.
 

content/game-player-data/join-games/Step2.en.md

@@ -75,8 +75,7 @@ python scripts/start_game.py
 You should see output in your terminal indicating that the game was started successfully.
 
 ```text
-Started game: 
-Game: c6f38a6a-d1c5-4bdf-8468-24692ccc4646   Map: Urban Underground
+Started game: Game: c6f38a6a-d1c5-4bdf-8468-24692ccc4646   Map: Urban Underground
 ```
 
 Try to run the script a second time in your terminal. This time, you should see an error message that indicates you could not start the game. This is because you have already started the game, so the `start_time` attribute exists. As a result, the request failed the conditional check on the entity.

content/game-player-data/open-games/Step2.en.md

@@ -60,7 +60,7 @@ except Exception as e:
     print(e)
 ```
 
-::alert[Edit **scripts/add_secondary_index.py**, set both `ReadCapacityUnits` and `WriteCapacityUnits` to **100** for `OpenGamesIndex`.]
+::alert[Edit **scripts/add_secondary_index.py**, set both `ReadCapacityUnits` and `WriteCapacityUnits` to **100** for `OpenGamesIndex`. Then, save the file.]{header="Change the capacity units"}
 
 Whenever attributes are used in a primary key for a table or secondary index, they must be defined in `AttributeDefinitions`. Then, you `Create` a new GSI in the `GlobalSecondaryIndexUpdates` property. For this GSI, you specify the index name, the schema of the primary key, the provisioned throughput, and the attributes you want to project.