Skip to case study
All projects
Selected work04 / 04 · 2 min read

Project case study ↘

Social Bookmarking

Turn saved images into a shared discovery feed.

The project connects image publishing with social relationships. Django serves the pages, while JavaScript requests update interactions and load additional image fragments.

Conceptual system sketch · not a product screenshot
My role
Developer · personal learning project
Context
Social interactions and content discovery with Django
Project status
Educational implementation
Period
Oct 2024 – Aug 2025

The challenge

Start with the problem.

The problem

An image collection becomes more useful when people can discover who saved it, follow related profiles and interact without reloading an entire page for each action.

The approach

Combine image bookmarking, user profiles and social relationships in Django, with AJAX endpoints for likes, follows and paginated image loading.

My contribution

From idea to implementation.

01 /

Image publishing and discovery

Implemented image bookmarking, image-list pagination and per-session view counting.

02 /

Profiles and social relationships

Connected profile editing with like/unlike and follow/unfollow interactions.

03 /

Activity feed

Built an activity model that references different objects and a dashboard that filters activity from followed users.

Architecture

How the pieces connect.

Django accounts, images and action modules connect ORM relationships, server-rendered templates and JavaScript/AJAX requests.

  1. Publish and manage identity

    Account and image views handle profiles and the image bookmarking flow.

  2. Request an interaction

    JavaScript sends AJAX requests for likes and follows; image-like responses return JSON.

  3. Record and filter activity

    The activity model links actions to different objects, and the dashboard selects followed-user activity.

  4. Load more images

    Paginated image fragments let the browser extend the list through additional requests.

Tools of the build

  • Python
  • Django
  • PostgreSQL
  • JavaScript
  • AJAX

Decisions

The thinking behind the code.

01

Enhance server-rendered pages with AJAX

Keep Django templates and add targeted requests for social actions and pagination.

Why this choice / trade-off

Focused updates keep the frontend small, while client scripts still need to handle responses and interface state.

02

Use a generic activity model

Reference different action targets through GenericForeignKey and suppress matching recent events.

Why this choice / trade-off

A flexible feed can represent several content types, with more application-level responsibility for target relationships.

03

Count views per session

Track image visits in the session to avoid counting each repeat request in the same browsing session.

Why this choice / trade-off

This is a simple browsing-session count, with accuracy limited by how sessions are created and retained.

The result

What the project delivers.

  • Image bookmarking and profile editing in one application.

  • Likes, follows and paginated image fragments handled through AJAX.

  • An activity feed filtered by followed users, with per-session image view counting.

What I learned

Social features combine data relationships with small interface updates. Working through likes, follows and a generic activity feed makes query scope, duplicate events and browser state concrete design concerns.

Follow the evidence

Go deeper into the implementation in the source repository.

Keep exploring

Let’s build something useful.

Get in touch