Developer's Code: A the Blog Inside Node.js My to Guide

CMS. or This isn't using third-party I by Ghost, blog WordPress, built powered it anyNode.js, Express, MongoDB, andEJS— scratch. all from

I I'd and it next what works, a the at choices under I peek why kept the hood made did, how if I going. add Here's

Stack 🛠️ Tech Overview

• Express Node.js +and routing the server for
• MongoDB Mongoose) (withfor storing blog posts
• EJSfor templates rendering dynamic
• Static assets in /publicand images for CSS, JS,

writing, of AsExpress 5.2.xthe release current and Technical-Committee-endorsed is line, framework's stable,26 Node.jsno route in matters async/await 5 Active version. longer handlers, for meaning LTS need is to support than That more route in it finally manual a native async sounds: the current Express I wrap every shippedtry/catchsensible if Express 4 keep catches server widely 5 crashing from to perfectly scratch starting you're from just is and the me. — project still the Express is used default. but for today, rejections stable, them unhandled a promise

"a EJS hides doing scenes is this straight is on a much MongoDB's lets into which magic doesn't it structure document you, the DSL. onto specifically post I object," blog of embedded — behind maps a of the than impose me and learning basically with model new HTML templating stack none drop plain naturally a Express picked Nothing rather bit whole was JSON happening. point. here JavaScript because what's

Structure 📁 Project

│ ├── │ models/ articles/ └── public/ ├── ├── └── └── └── NumberFormatter.js │ ├── article.js server.js └── views/ articles.js routes/ index.ejs │ │ │ show.ejs └── ├── scripts/ │ ├──

app: for Express is classic This MVC-flavored a layout an fairly

• models/of holds shape the the data the Mongoose schema —
• views/the holds rendered — templates what EJS gets
• routes/happens — is request when holds URL hit handlers a the what
• server.jsstarts wires and three listening all together

I a a It's separate out that small enough didn't project bother splittingcontrollers/route — in the folder handlersroutes/articles.jsIf or user logic. to refactor that's next I'd grew comments, usually routing reach are first the the the live include tags, for. to accounts, enough to blog simple right

The Flow Main 🔁

1. Home Route (/)

In server.js:

=> createdAt: formatWithAbbreviation const res.render('articles/index', }); res) }); app.get('/', articles, { await (req, = articles Article.find().sort({ async }); { 'desc'

• all MongoDB Fetches from articles
• (newest creation Sorts date them first) by
• EJS with a them template into along an formatter Passes number

Model The 2. Article

Behind thatArticle.find()sits a schema Mongoose call inmodels/article.jslooks . like this: roughly Mine

required: true { const 0 }, true views: { articleSchema); module.exports true, mongoose String, }, type: default: title: required: articleSchema slug: body: type: { Number, { = true type: required: mongoose.Schema( }, }, = ); } String, timestamps: require('mongoose'); }, new mongoose.model('Article', = String, type: { const { true unique:

The } timestamps: true {is lot of it option quiet here — work a and adds automatically maintains doingcreatedAt and updatedAthits data. on sorting which ever malformed relies before schema route say) it newest-first. gets database, the corrupting is a fields, exactly also silently (missing the for Mongoose's means my a validation rejected than title, home what article rather

3. Article Routes (/articles)

In routes/articles.jsI handle: ,

• post creation New
• Editing
• Deletion
• Viewing individual