supriya2233/blog-web-application

Purpose and Runtime

A server-rendered blog CRUD application for creating, listing, editing, and deleting categorized posts. It runs on Node.js with Express and renders HTML through EJS. The server entry point is app.js; package scripts and dependencies are defined in package.json.

Posts are intentionally ephemeral: application state lives in an in-memory array and is lost whenever the Node process restarts.

Server and Routing Boundary

app.js is the central application controller. It owns Express initialization, static-file serving, EJS view rendering, request parsing, and the routes that implement post lifecycle operations.

The browser interacts through normal HTTP page/form requests rather than a separate API. Route handlers read form data, mutate in-memory state, then render or redirect to EJS pages.

Grounding:

• app.js

• views/index.ejs

• views/edit.ejs

Post Lifecycle and State

The core domain is a blog post, including content and category information. The in-memory post collection is the persistence boundary and source of truth for all views.

Primary flow:

1. A user opens the post list.

2. The server renders available posts.

3. Create and edit forms submit to Express routes.

4. The route mutates the in-memory collection.

5. The browser is redirected or receives a newly rendered page.

6. Delete requests remove a post from the same collection.

There is no database, authentication system, external API, or durable storage layer.

Grounding:

• app.js

• views/new.ejs

• views/edit.ejs

Presentation Layer

EJS templates define the server-generated screens:

• views/index.ejs presents the blog/post listing and navigation to actions.

• views/new.ejs provides post-creation input.

• views/edit.ejs provides post-update input.

• views/404.ejs is the fallback presentation for unmatched resources.

Templates are the boundary between server-owned post data and browser HTML.

Grounding:

• views/index.ejs

• views/new.ejs

• views/404.ejs

Static Client Assets

Express serves browser assets from public. Styling is centralized in public/css/style.css, supporting the responsive interface. Client-side theme behavior is isolated in public/js/theme.js, which handles light/dark mode independently of post CRUD state.

Grounding:

• public/css/style.css

• public/js/theme.js

• app.js

Operational Model

The application is a single Node process, normally started with npm and exposed locally on port 3000. Development mode uses Nodemon for process restart on source changes; this also clears posts because state is process-local.

There is no deployment infrastructure, background worker, message queue, cache, database, or third-party service represented in the repository.

Grounding:

• package.json

• package-lock.json

• app.js