chore: deprecating beaker; refreshing outdated docs (#559)

* chore: deprecating beaker; refreshing outdated docs

* chore: refresh logo

README.md

@@ -1,5 +1,5 @@
 <div align="center">
-<a href="https://github.com/algorandfoundation/algokit-cli"><img src="https://bafybeihfrtfg4vcufkcqmrtslkhx737ppz2fgn2lnctsd6waduqhhhibye.ipfs.nftstorage.link/" width=60%></a>
+<a href="https://github.com/algorandfoundation/algokit-cli"><img src="https://ipfs.algonode.xyz/ipfs/QmZqt55wHXrZzhBihSVzXDvwp9rguvLAvFhUm1qJR6GYeQ" width=60%></a>
 </div>
 
 <p align="center">

docs/cli/index.md

@@ -630,7 +630,7 @@ Name of an official template to use. To choose interactively, run this command w
 
 * **Options**
 
-    tealscript | python | react | fullstack | beaker | base | playground
+    tealscript | python | react | fullstack | base | playground
 
 
 

docs/features/generate.md

@@ -43,7 +43,7 @@ of available operations and parameters.
 #### Python
 
 ```python
-# A similar working example can be seen in the beaker_production template, when using Python deployment
+# A similar working example can be seen in the algokit python template, when using Python deployment
 from smart_contracts.artifacts.HelloWorldApp.client import (
     HelloWorldAppClient,
 )
@@ -66,7 +66,7 @@ response = app_client.hello(name="World")
 #### TypeScript
 
 ```typescript
-// A similar working example can be seen in the beaker_production template, when using TypeScript deployment
+// A similar working example can be seen in the algokit python template with typescript deployer, when using TypeScript deployment
 import { HelloWorldAppClient } from "./artifacts/HelloWorldApp/client";
 
 const appClient = new HelloWorldAppClient(
@@ -104,7 +104,7 @@ Custom generate commands are defined in the `.algokit.toml` file within the proj
 
 ### Understanding `Generators`
 
-A `generator` is essentially a compact, self-sufficient `copier` template. This template can optionally be defined within the primary `algokit templates` to offer supplementary functionality after a project is initialized from the template. For instance, the official [`algokit-beaker-default-template`](https://github.com/algorandfoundation/algokit-beaker-default-template/tree/main/template_content) provides a generator within the `.algokit/generators` directory. This generator can be employed for executing extra tasks on AlgoKit projects that have been initiated from this template, such as adding new smart contracts to an existing project. For a comprehensive explanation, please refer to the [`architecture decision record`](../architecture-decisions/2023-07-19_advanced_generate_command.md).
+A `generator` is essentially a compact, self-sufficient `copier` template. This template can optionally be defined within the primary `algokit templates` to offer supplementary functionality after a project is initialized from the template. For instance, the official [`algokit-python-template`](https://github.com/algorandfoundation/algokit-python-template/tree/main/template_content) provides a generator within the `.algokit/generators` directory. This generator can be employed for executing extra tasks on AlgoKit projects that have been initiated from this template, such as adding new smart contracts to an existing project. For a comprehensive explanation, please refer to the [`architecture decision record`](../architecture-decisions/2023-07-19_advanced_generate_command.md).
 
 ### Requirements
 
@@ -130,7 +130,7 @@ The custom command employs the `copier` library to duplicate the files from the
 
 ### Examples
 
-As an example, let's use the `smart-contract` generator from the `algokit-beaker-default-template` to add new contract to an existing project based on that template. The `smart-contract` generator is defined as follows:
+As an example, let's use the `smart-contract` generator from the `algokit-python-template` to add new contract to an existing project based on that template. The `smart-contract` generator is defined as follows:
 
 ```toml
 [algokit]
@@ -176,4 +176,4 @@ $ algokit generate smart-contract -a contract_name "MyCoolContract"
 
 #### Third Party Generators
 
-It is important to understand that by default, AlgoKit will always prompt you before executing a generator to ensure it's from a trusted source. If you are confident about the source of the generator, you can use the `--force` or `-f` option to execute the generator without this confirmation prompt. Be cautious while using this option and ensure the generator is from a trusted source. At the moment, a trusted source for a generator is defined as _a generator that is included in the official AlgoKit templates (e.g. `smart-contract` generator in `algokit-beaker-default-template`)_
+It is important to understand that by default, AlgoKit will always prompt you before executing a generator to ensure it's from a trusted source. If you are confident about the source of the generator, you can use the `--force` or `-f` option to execute the generator without this confirmation prompt. Be cautious while using this option and ensure the generator is from a trusted source. At the moment, a trusted source for a generator is defined as _a generator that is included in the official AlgoKit templates (e.g. `smart-contract` generator in `algokit-python-template`)_

docs/features/init.md

@@ -20,7 +20,7 @@ $ ~ algokit init
 ? Name of project / directory to create the project in:  my-cool-app
 ```
 
-Once above 2 questions are answered, the `cli` will start instantiating the project and will start asking questions specific to the template you are instantiating. By default official templates such as `python`, `fullstack`, `react`, `beaker` include a notion of a `preset`. If you want to skip all questions and let the tool preset the answers tailored for a starter project you can pick `Starter`, for a more advanced project that includes unit tests, CI automation and other advanced features, pick `Production`. Lastly, if you prefer to modify the experience and tailor the template to your needs, pick the `Custom` preset.
+Once above 2 questions are answered, the `cli` will start instantiating the project and will start asking questions specific to the template you are instantiating. By default official templates such as `python`, `fullstack`, `react`, `python` include a notion of a `preset`. If you want to skip all questions and let the tool preset the answers tailored for a starter project you can pick `Starter`, for a more advanced project that includes unit tests, CI automation and other advanced features, pick `Production`. Lastly, if you prefer to modify the experience and tailor the template to your needs, pick the `Custom` preset.
 
 If you want to accept the default for each option simply hit [enter] or alternatively to speed things up you can run `algokit init --defaults` and they will be auto-accepted.
 
@@ -60,7 +60,7 @@ Copying /Users/algokit/algokit-init/my-smart-contract/smart_contracts/.env.templ
 🎉 Performed initial git commit successfully! 🎉
 🙌 Project initialized at `my-smart-contract`! For template specific next steps, consult the documentation of your selected template 🧐
 Your selected template comes from:
-➡️ https://github.com/algorandfoundation/algokit-beaker-default-template
+➡️ https://github.com/algorandfoundation/algokit-python-template
 As a suggestion, if you wanted to open the project in VS Code you could execute:
 
 > cd my-smart-contract && code .
@@ -79,11 +79,11 @@ There are a number of options that can be used to provide answers to the templat
 
 As well as the official Algorand templates shown when running the init command, community templates can also be provided by providing a URL via the prompt or the `--template-url` option.
 
-e.g. `algokit init --template-url https://github.com/algorandfoundation/algokit-beaker-default-template` (that being the url of the official beaker template, the same as `algokit init -t beaker`).
+e.g. `algokit init --template-url https://github.com/algorandfoundation/algokit-python-template` (that being the url of the official python template, the same as `algokit init -t python`).
 
 The `--template-url` option can be combined with `--template-url-ref` to specify a specific commit, branch or tag
 
-e.g. `algokit init --template-url https://github.com/algorandfoundation/algokit-beaker-default-template --template-url-ref 9985005b7389c90c6afed685d75bb8e7608b2a96`
+e.g. `algokit init --template-url https://github.com/algorandfoundation/algokit-python-template --template-url-ref 0232bb68a2f5628e910ee52f62bf13ded93fe672`
 
 If the URL is not an official template there is a potential security risk and so to continue you must either acknowledge this prompt, or if you are in a non-interactive environment you can pass the `--UNSAFE-SECURITY-accept-template-url` option (but we generally don't recommend this option so users can review the warning message first) e.g.
 
@@ -101,18 +101,18 @@ If you want to create a community template, you can use the [AlgoKit guidelines
 
 Answers to specific template prompts can be provided with the `--answer {key} {value}` option, which can be used multiple times for each prompt. Quotes can be used for values with spaces e.g. `--answer author_name "Algorand Foundation"`.
 
-To find out the key for a specific answer you can either look at `.algokit/.copier-answers.yml` in the root folder of a project created via `algokit init` or in the `copier.yaml` file of a template repo e.g. for the [beaker template](https://github.com/algorandfoundation/algokit-beaker-default-template/blob/main/copier.yaml).
+To find out the key for a specific answer you can either look at `.algokit/.copier-answers.yml` in the root folder of a project created via `algokit init` or in the `copier.yaml` file of a template repo e.g. for the [python template](https://github.com/algorandfoundation/algokit-python-template/blob/main/copier.yaml).
 
 ## Non-interactive project initialization
 
-By combining a number of options, it is possible to initialize a new project without any interaction. For example, to create a project named `my-smart-contract` using the `beaker` template with no git, no bootstrapping, the author name of `Algorand Foundation`, and defaults for all other values, you could execute the following:
+By combining a number of options, it is possible to initialize a new project without any interaction. For example, to create a project named `my-smart-contract` using the `python` template with no git, no bootstrapping, the author name of `Algorand Foundation`, and defaults for all other values, you could execute the following:
 
 ```
 
 $ ~ algokit init -n my-smart-contract -t python --no-git --no-bootstrap --answer author_name "Algorand Foundation" --defaults
 🙌 Project initialized at `my-smart-contract`! For template specific next steps, consult the documentation of your selected template 🧐
 Your selected template comes from:
-➡️ https://github.com/algorandfoundation/algokit-beaker-default-template
+➡️ https://github.com/algorandfoundation/algokit-python-template
 As a suggestion, if you wanted to open the project in VS Code you could execute:
 
 > cd my-smart-contract && code .

docs/tutorials/algokit-template.md

@@ -3,7 +3,7 @@
 This README serves as a guide on how to create custom templates for AlgoKit, a tool for initializing Algorand smart contract projects.
 Creating templates in AlgoKit involves the use of various configuration files and a templating engine to generate project structures that are tailored to your needs.
 This guide will cover the key concepts and best practices for creating templates in AlgoKit.
-We will also refer to the official [`algokit-beaker-default-template`](https://github.com/algorandfoundation/algokit-beaker-default-template) as an example.
+We will also refer to the official [`algokit-python-template`](https://github.com/algorandfoundation/algokit-python-template) as an example.
 
 ## Table of Contents
 
@@ -26,7 +26,7 @@ We will also refer to the official [`algokit-beaker-default-template`](https://g
 
 For users who are keen on getting started with creating AlgoKit templates, you can follow these quick steps:
 
-1. Click on `Use this template`->`Create a new repository` on [algokit-beaker-default-template](https://github.com/algorandfoundation/algokit-beaker-default-template) Github page. This will create a new reference repository with clean git history, allowing you to start modifying and transforming the base beaker template into your own custom template.
+1. Click on `Use this template`->`Create a new repository` on [algokit-python-template](https://github.com/algorandfoundation/algokit-python-template) Github page. This will create a new reference repository with clean git history, allowing you to start modifying and transforming the base python template into your own custom template.
 2. Modify the cloned template according to your specific needs. You can refer to the remainder of this tutorial for an understanding of expected behaviors from the AlgoKit side, Copier - the templating framework, and key concepts related to the default files you will encounter in the reference template.
 
 ## Overview of AlgoKit Templates
@@ -47,7 +47,7 @@ AlgoKit provides the `algokit init` command to initialize a new project using a
 
 This file is the AlgoKit configuration file for this project which can be used to specify the minimum version of the AlgoKit. This is essential to ensure that projects created with your template are always compatible with the version of AlgoKit they are using.
 
-Example from `algokit-beaker-default-template`:
+Example from `algokit-python-template`:
 
 ```toml
 [algokit]
@@ -61,7 +61,7 @@ This specifies that the template requires at least version `v1.1.0-beta.4` of Al
 Python projects in AlgoKit can leverage a wide range of tools for dependency management and project configuration. While Poetry and the `pyproject.toml` file are common choices, they are not the only options.
 If you opt to use Poetry, you'll rely on the pyproject.toml file to define the project's metadata and dependencies. This configuration file can utilize the Jinja templating syntax for customization.
 
-Example snippet from `algokit-beaker-default-template`:
+Example snippet from `algokit-python-template`:
 
 ```toml
 [tool.poetry]
@@ -71,11 +71,7 @@ description = "Algorand smart contracts"
 authors = ["{{ author_name }} <{{ author_email }}>"]
 readme = "README.md"
 
-[tool.poetry.dependencies]
-python = "^3.10"
-beaker-pyteal = "^1.0.0"
-algokit-utils = "^1.3"
-python-dotenv = "^1.0.0"
+...
 ```
 
 This example shows how project metadata and dependencies are defined in `pyproject.toml`, using Jinja syntax to allow placeholders for project metadata.
@@ -176,7 +172,7 @@ python_path:
 
 After mastering the use of `copier` and building your templates based on the official AlgoKit template repositories, you can enhance your proficiency by learning to define `custom generators`. Essentially, generators are smaller-scope `copier` templates designed to provide additional functionality after a project has been initialized from the template.
 
-For example, the official [`algokit-beaker-default-template`](https://github.com/algorandfoundation/algokit-beaker-default-template/tree/main/template_content) incorporates a generator in the `.algokit/generators` directory. This generator can be utilized to execute auxiliary tasks on AlgoKit projects that are initiated from this template, like adding new smart contracts to an existing project. For a comprehensive understanding, please consult the [`architecture decision record`](../architecture-decisions/2023-07-19_advanced_generate_command.md) and [`algokit generate documentation`](../features/generate.md).
+For example, the official [`algokit-python-template`](https://github.com/algorandfoundation/algokit-python-template/tree/main/template_content) incorporates a generator in the `.algokit/generators` directory. This generator can be utilized to execute auxiliary tasks on AlgoKit projects that are initiated from this template, like adding new smart contracts to an existing project. For a comprehensive understanding, please consult the [`architecture decision record`](../architecture-decisions/2023-07-19_advanced_generate_command.md) and [`algokit generate documentation`](../features/generate.md).
 
 #### How to Create a Generator
 

docs/tutorials/intro.md

@@ -126,7 +126,7 @@ Once the `Algorand Python` based project is created, you can get started by buil
 
 [![Watch the video](https://ipfs.algonode.xyz/ipfs/Qmc9mRaPoDyhUFmek4ETxVfKUKzUg9pf3Tss5xwkBGdQis)](https://ipfs.algonode.xyz/ipfs/Qma6gNqxsSFc9Jbh8kBTZyVLv5gqFj1xnrsjoeT6MAAwCw/)
 
-The App ID of the deployed contract and its Algorand address is displayed, followed by the message returned from the smart contract call (`Hello, Beaker`).
+The App ID of the deployed contract and its Algorand address is displayed, followed by the message returned from the smart contract call (`Hello, Python`).
 
 1. Start LocalNet
 2. Build the smart contract. Notice how a folder named `artifacts` is created with the [AVM (Algorand Virtual Machine)](https://developer.algorand.org/docs/get-details/dapps/avm/) related artifacts for deploying your smart contract.

src/algokit/cli/init.py

@@ -72,7 +72,6 @@ class ContractLanguage(Enum):
 
     PYTHON = "Python 🐍"
     TYPESCRIPT = "TypeScript 📘"
-    PYTEAL = "PyTeal 🔧"
 
 
 class TemplateKey(str, Enum):
@@ -117,7 +116,6 @@ def __eq__(self, other: object) -> bool:
 LANGUAGE_TO_TEMPLATE_MAP = {
     ContractLanguage.PYTHON: TemplateKey.PYTHON,
     ContractLanguage.TYPESCRIPT: TemplateKey.TEALSCRIPT,
-    ContractLanguage.PYTEAL: TemplateKey.BEAKER,
 }
 
 
@@ -140,10 +138,6 @@ def _get_blessed_templates() -> dict[TemplateKey, BlessedTemplateSource]:
             url="gh:algorandfoundation/algokit-fullstack-template",
             description="Official template for starter or production fullstack applications.",
         ),
-        TemplateKey.BEAKER: BlessedTemplateSource(
-            url="gh:algorandfoundation/algokit-beaker-default-template",
-            description="Official template for starter or production Beaker applications.",
-        ),
         TemplateKey.BASE: BlessedTemplateSource(
             url="gh:algorandfoundation/algokit-base-template",
             description="Official base template for enforcing workspace structure for standalone AlgoKit projects.",

tests/init/test_init.test_init_template_selection.approved.txt

@@ -9,7 +9,6 @@ DEBUG: selected project_type = Smart Contracts 📜
 ? Which language would you like to use for the smart contract?
 Python 🐍
 TypeScript 📘
-PyTeal 🔧
 DEBUG: selected language = ContractLanguage.PYTHON
 DEBUG: template source = gh:robdmoore/copier-helloworld
 DEBUG: Attempting to load project config from {current_working_directory}/.algokit.toml

tests/init/test_init.test_init_wizard_v2_flow.Full Stack.approved.txt

@@ -9,7 +9,6 @@ DEBUG: selected project_type = Smart Contracts & DApp Frontend 🎛️
 ? Which language would you like to use for the smart contract?
 Python 🐍
 TypeScript 📘
-PyTeal 🔧
 DEBUG: selected language = ContractLanguage.PYTHON
 DEBUG: template source = gh:robdmoore/copier-helloworld
 DEBUG: Attempting to load project config from {current_working_directory}/.algokit.toml

tests/init/test_init.test_init_wizard_v2_flow.Smart Contract.approved.txt

@@ -9,7 +9,6 @@ DEBUG: selected project_type = Smart Contracts 📜
 ? Which language would you like to use for the smart contract?
 Python 🐍
 TypeScript 📘
-PyTeal 🔧
 DEBUG: selected language = ContractLanguage.PYTHON
 DEBUG: template source = gh:robdmoore/copier-helloworld
 DEBUG: Attempting to load project config from {current_working_directory}/.algokit.toml