CASE STUDY · 05

GREENLIFESTYLE

A full-stack sustainability web platform created as a university project to encourage greener habits through content, community, and guided action.

Git Commits

Repository development history

Core Framework

Django

Python-based full-stack architecture

Main Interface Style

Tailwind CSS

Utility-first frontend styling

Project Type

University Project

Academic build with real product scope

Project Overview

GreenLifestyle appears to have been designed as a student-built sustainability platform focused on promoting environmentally responsible habits through digital education and user participation. Its subject matter points to a goal of helping people discover greener lifestyle practices in a way that feels practical rather than abstract.

What makes the project stronger than a typical coursework demo is that it includes real application structure: user authentication, tip creation and publishing, community updates, admin management, static information pages, and a layered Django app organization. That gives it the shape of a complete social-impact web application rather than a single-page academic prototype.

Core Dependencies and Frameworks

The technology stack was selected to minimize operational overhead while maximizing developer velocity.

Backend Framework

Django

Primary full-stack framework handling routing, templates, models, forms, and admin features.

Python

Core programming language powering the application logic.

Frontend Layer

HTML Templates

Server-rendered interface built through Django template rendering.

CSS

Supports visual customization and layout behavior across templates.

JavaScript

Adds client-side interactivity where needed.

Tailwind CSS

Utility-first styling approach configured through Tailwind and PostCSS.

Tooling & Delivery

PostCSS

Used with Tailwind CSS as part of the frontend styling pipeline.

GitHub Actions

Repository includes workflow automation for deployment processes.

Node Package Tooling

package.json and package-lock.json indicate frontend build dependencies were managed with npm.

System Data Flow and Security Boundaries

The system is designed in discrete layers, establishing strict boundaries between the client, the server actions, and the database.

>User Roles

#The platform supports general visitors, authenticated users contributing eco tips, and administrators managing content and community activity.

>Public Sustainability Website

#The public-facing layer likely contains the homepage, static informational pages, and discoverable sustainability content.

>Authentication Surface

#Handles login, logout, and account-related access control for community participation.

>Eco Tips Module

#Supports the creation, display, and management of sustainability tips contributed by users or maintained by administrators.

>Content Flow

>Security Boundary

#Django authentication and app-level separation create the boundary between public reading experiences and protected contribution or administration features.

Source Code Organization

A predictable folder structure is critical for a solo developer to maintain velocity over time.

GreenLifestyleMain Django project configuration directory that likely contains settings, URL routing, and WSGI/ASGI setup.

accountsAuthentication and account-related logic for login, logout, and user management flows.

administrationCustom admin-side application logic for internal dashboard and moderation features.

coreShared application pages, utilities, and foundational site logic.

tipsDedicated domain module for eco tips, likely including models, views, forms, and publishing behavior.

templatesDjango template files for rendering the user interface.

staticCSS, JavaScript, images, and other static frontend assets.

.github

workflowsAutomation files for deployment or CI-related workflows.

manage.pyStandard Django project entry point for running management commands.

requirements.txtPython dependency list for the Django backend environment.

package.jsonFrontend tooling manifest for Tailwind CSS and related Node-based dependencies.

tailwind.config.jsTailwind CSS configuration controlling utility generation and theme behavior.

postcss.config.jsPostCSS configuration supporting the frontend CSS compilation workflow.

Database Schema Overview

The database design for GreenLifestyle is likely centered on a small but meaningful relational structure typical of Django applications: users, content entities, and administration workflows. For a university project, this is a strong design direction because it balances educational clarity with enough domain depth to support real interactions such as publishing, moderation, and community contribution.

Zero-Trust Architecture

Database Schema Overview

Identity

SCHEMA

users

RLS

profiles

RLS

sessions

RLS

Sustainability Content

SCHEMA

tips

RLS

Community

SCHEMA

community_updates

RLS

submissions

RLS

engagement_records

RLS

Administration

SCHEMA

admin_logs

RLS

publication_states

RLS

moderation_records

RLS

Migration Matrix

The repository structure strongly suggests a normalized Django app model where separate domains such as accounts, tips, and administration are isolated into their own apps for maintainability.

Commit history mentioning tip publishing fixes indicates that content state management, such as draft or published visibility, was an intentional part of the schema design.

The inclusion of admin dashboard and community update features implies the project evolved beyond a basic CRUD demo into a more operational content platform.

Mutation Layer

GreenLifestyle uses classic Django server-side request handling, where mutations are processed through view logic, forms, and model-backed workflows.

Server Action Modules

accounts views

Handles authentication flows such as login, logout, and user access control.

tips CRUD

Manages creation, editing, publishing, and display of sustainability tips.

administration dashboard

Provides internal actions for oversight, moderation, and content management.

community updates flow

Supports posting and surfacing updates that keep the platform active and community-oriented.

static and core page rendering

Delivers educational pages and shared site logic through server-rendered templates.

Visual Identity and Styling Rules

The design system focuses on clean and structured presentation, establishing a consistent brand identity.

Principles

Friendly sustainability-first interface focused on clarity and approachability.
Educational product design that keeps content easy to read and navigate.
Tailwind-driven styling for rapid iteration during academic development.
Practical layout choices over experimental visuals, matching a university project’s product goals.
Interface hierarchy that supports both public readers and admin users.

Visual Identity Guidelines

Eco Green

#22C55E

Primary sustainability accent for buttons, highlights, and action cues.

Leaf Dark

#166534

Deeper green for headers, emphasis, and stronger contrast moments.

Clean White

#FFFFFF

Base background and reading surface.

Soft Gray

#F3F4F6

Subtle section backgrounds and card surfaces.

Earth Text

#1F2937

Primary body text for readable content presentation.

Typography Scale

Headings

600-700

Modern Sans-Serif

Used for section titles, navigation emphasis, and dashboard headings.

Body Text

400-500

Readable Sans-Serif

Used for sustainability content, user guidance, and educational copy.

Utility Text

400-600

System Sans-Serif

Used in forms, labels, buttons, and administration interfaces.

Engineering Patterns

Architectural Trade-offs and Key Decisions