<commit_before># Physical Web Content Manager
The aim of this project is to implement a backend for museums and exhibits that utilizes
Physical Web technology. The backend will allow visitors to access information about exhibit
pieces without the need to install any apps. Physically, this will be accomplished using
Eddystone beacons located near each piece. We focus on developing the software side used to
configure these beacons.
To achieve this, we will create an Android App that allows museum curators to configure the
Physical Web beacons they want to deploy and then upload the content that will be served. The
app will support combinations of text, images, audio and video. It will use Google Drive API for
its storage backend. The app will also allow the curators to create a map of the exhibition and
the beacons deployed, with the map also being stored on Google Drive. The app will also
support storing multiple entire configurations (a map and its associated beacon content) so that
the end-user can quickly deploy the content they need when exhibits change.<commit_msg>Updated layout<commit_after># Physical Web Content Manager
The aim of this project is to implement a backend for museums and exhibits that utilizes
Physical Web technology. The backend will allow visitors to access information about exhibit
pieces without the need to install any apps. Physically, this will be accomplished using
Eddystone beacons located near each piece. We focus on developing the software side used to
configure these beacons.

To achieve this, we will create an Android App that allows museum curators to configure the
Physical Web beacons they want to deploy and then upload the content that will be served. The
app will support combinations of text, images, audio and video. It will use Google Drive API for
its storage backend. The app will also allow the curators to create a map of the exhibition and
the beacons deployed, with the map also being stored on Google Drive. The app will also
support storing multiple entire configurations (a map and its associated beacon content) so that
the end-user can quickly deploy the content they need when exhibits change.
{'fraction_non_alphanumeric': 0.019337016574585635, 'fraction_numerical': 0.0, 'mean_word_length': 4.825737265415549, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1576616', 'n_tokens_mistral': 476, 'n_tokens_neox': 457, 'n_words': 352}