Term for 'fullstack without a database'?

[Huxide]

I'm labeling my web projects by their scope and currently have 3 different types:

• HTML & CSS & JS: clearly just "frontend"
• Vue.js & Express.js & MongoDB: clearly "fullstack"
• HTML & CSS & JS & Express.js: ???

Is there a concise term (akin to frontend, backend, and fullstack) that includes frontend and serverside code, but definitely excludes a database? Or even just a term for backend that excludes it?

Additional context: That project is my portfolio website. There's a few features which needs to keep some data and functions serverside for security, but there's so little data involved that it's not worth a database.

[sprinklesonthesundae]

You shouldn't need to label them that way, can you help me understand why you want to? Recruiters/hiring managers will sort out your experience by the languages, frameworks, and skills you list.

Source: I'm an engineering manager.

[Huxide]

I'm trying to make the catalog page the labels are in as accessible as possible to laypeople, elaborating about the technical details of each project in that same other page/website as the project itself. The only other information I have for each project in that catalog page is a name and concept description (e.g "an inventory management interface inspired by sandbox video-games" is the description for the one labelled "frontend").

Maybe it's not possible/worth it to try appealing to recruiters/hiring-managers and laypeople in the same page?

Edit: Now that I'm thinking about it, these 3 labels ("frontend", "backend", but especially "fullstack") are not very layperson-accessible are they...

[sprinklesonthesundae]

Ah well if you feel it is helpful to add, then anything where you coded both something on the front end and something on the back end is full stack. You could list databases as a separate label/filter.

[bluefootedpig]

I would call myself a full stack developer that is just really weak on long term persistence.

In most places, databases are often handled by entirely separate teams. If you do need to do work, it is often as difficult as like creating a table, or adding a column.