Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Full-stack responsive Django app using Bootstrap & JQuery

bootstrap, jquery, django
Leon Potgieter•290
@leonp84
A solution to the Entertainment web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I decided to tackle this project to solidify my understanding of the Django web framework and so built this as a full-stack application. Login and Logout sections are also present, but I decided not to wire these up to the database, so they’re cosmetic only.

In the future, for projects of this score I’m assuming a front-end framework like React would work better, instead of vanilla HTML with Bootstrap CSS. I would also like to give Tailwind CSS a go.

What challenges did you encounter, and how did you overcome them?

I had limited experience with asynchronous JavaScript up to know, so had to learn to launch backend interactions (Database update) based on JavaScript events. jQuery’s ajax syntax simplifies this quite a bit (compared to the vanilla JavaScript) so it made it easier.

What specific areas of your project would you like help with?

Feel free to point out mistakes or room for improvement, especially in the JavaScript file where I used jQuery’s ajax functions to work with the Python backend. I almost certainly am not following convention (snippet bellow) with the way I accomplished it, so would appreciate feedback.

$.ajax({
    url: "/update_bookmarks/",
    type: "POST",
    dataType: "json",
    headers: {
        "X-Requested-With": "XMLHttpRequest",
        "X-CSRFToken": CSRF_TOKEN, 
        'item': $(this).find('.item-id').text()
    },

Thanks Frontend Mentor, these are great challenges, and make for great portfolio projects!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Leon Potgieter's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.