diff --git a/README.md b/README.md
index 91725f0df2e8084fd5d426c1109e23cba1a44ee3..1b91c7e1291a1ae15cf07ecbfd33fe316299f8f4 100644
--- a/README.md
+++ b/README.md
@@ -1,92 +1,64 @@
 # Web Chall Template
 
-Web challenge template
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git.sch.bme.hu/radlaci97/web-chall-template.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git.sch.bme.hu/radlaci97/web-chall-template/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!).  Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
+Template for web challenges in Python3.
 
 ## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+Web challenges usually look similar, hence the idea to provide a template. It supports fast prototyping, as changes are automagically propagated to the web server (both assets and code).
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+There are three directories (and servers); but only one is needed for a web challenge.
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+- Victim: a small Flask project with a template and assets.
+- Attacker: a different site, which can be used for testing cross-origin attacks.
+- Nginx: a glue for reverse proxying the above mentioned two sites. Should not be changed, except for secure contexts (`https://`), proxying websockets (`ws://`, `wss://`).
 
 ## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+The developer environment is easy to set up with docker-compose.
 
 ## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+### Try it out!
+`docker-compose up` sets up the whole environment. Then open `http://localhost`, where a landing page (served by `nginx`) is presented.
+
+### Development
+For VSCode, open `workspace.code-workspace`. This shows both sites. Any change is reflected on the web site (after a refresh on the browser).
+
+Feel free to add packages or use features! For cookie-based sessions, you can import `session`, set a `secret_key` (please use 16 random characters). It can contain basic types, and can be reset by deleting cookies. An example, showing how many times a user visited a site, is presented below:
+
+```patch
+--- a/victim/app.py
++++ b/victim/app.py
+@@ -1,9 +1,14 @@
+-from flask import Flask, make_response, redirect, render_template
++from flask import Flask, make_response, redirect, render_template, session
+ app = Flask(__name__, static_url_path='/', static_folder='static', template_folder='templates')
++app.secret_key = b'lulz'
+ 
+ @app.route('/index.html')
+ def index():
+-    return render_template('index.html')
++    if 'counter' in session:
++        session['counter'] += 1
++    else:
++        session['counter'] = 0
++    return render_template('index.html', counter=session['counter'])
+```
 
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+In the last line, we make the counter available to the template, where we can inject the value:
+
+```patch
+--- a/attacker/templates/index.html
++++ b/attacker/templates/index.html
+@@ -15,6 +15,8 @@
+ 
+ <p>This is an ATTACKER Flask application running on <snap id="origin-text">(Origin)</snap>.</p>
+ 
++<p>You have visited this site {{ counter }} times.</p>
++
+ {% endblock %}
+ </body>
+ </html>
+```
 
-## License
-For open source projects, say how it is licensed.
+## Note: Dirty hacks on links
 
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+The links to open the attacker's or victim pages are as follows: `http://attacker.radlaci97.sch.bme.hu/` `http://victim.radlaci97.sch.bme.hu/`. These are registered so that it points to localhost, and the Nginx in the container is configured to match the host with the host passed. Basically, it will show your page.