drill-n-bass / apiarena Goto Github PK

Apiarena site

This project concerns the website apiarena.com. The Apiarena website is a representative website of the company that deals with the wholesale of games and console-related products.

In addition to the information that the website should contain in connection with its activities, this website will allow sending inquiries from customers.

The page will contain the following content:

• home page with information about the company
• contact information
• company logo
• pictures of the products the company sells
• a form for sending inquiries about the availability of goods.

The new Apiarena site based on the old ultiglobal.com. The reason I obtained the data I needed to get started this way was because the developer responsible for the old version of the site didn't have time to provide me with the static files I needed. Due to the fact that I wanted to start migrating data as soon as possible and start working on building a new website using Django, I considered it right to use HTTrack application. Then I added all the static files from the old site to the project in Django ("Apiarena Django site"). This is how the work on the new website apiarena.com began.

After adding the appropriate paths to settings.py: STATIC_URL = '/ static /' STATICFILES_DIRS = [os.path.join (BASE_DIR, 'static'),] and a html file named home.html to / Templates, I modified the import paths of the js libraries.

For this, I changed link from ../ to https: //

The Git related info:

Since the creation of my website took a long time - which was related to deepening my knowledge of JS, Django, and creating a website for Apiarena - commits for early versions of 'my-personal-page' repository are fragmented in several repositories. The skeleton of an early version of my Django website is located as a project branch with the Apiarena repo.

This confusion was the result of the transition from using the GIT Bash terminal to the implemented Git commit system in Visual Studio Code. However, I must admit that I was aware of the circumstances I entered before they happened. All these circumstances were intentional, because I wanted to check a few things thanks to them that would give me additional valuable programming knowledge.

• First, I wanted to see how well Visual Studio Code is doing with Git.
• I wanted to know how difficult it is to separate repositories (using Visual Studio Code)
• I also wanted to see how difficult it is to split the Django project into two projects (because initially, both my website and the Apiarena project were actually one project: they had one common settings.py, but different models, py and views.py and url.py)

Due to the fact that the Apiarena project was not implemented in a large team, and the entire aspect related to Django was only my participation, I could allow myself to take the first steps in building the Apiarena website a test site for the issues raised above.

The next stages of work on my personal page and on the Apiarena project have already been carried out in accordance with the methodology of working with GIT repositories.

Thanks to the successful migration, all changes in the Apiarena repository only apply to this project.