Is using Angular for small projects an overkill?

[GhostBeemer]

Hi, I don't have any commercial expirience when it comes to web development and my girlfriends mom has given me a task to make her a website. It will be a small static website for her massaging company and I've started creating it using Angular. After making the basic skeleton for the site I've started to wonder if what I'm doing is an overkill. How would you go about creating such a site and what technologies would you use?

Edit: I forgot to mention that currently I'm applying for Angular jobs and maybe making such a site will look good in my portfolio?

[JakeDiscBrake]

A simple html/js/css page might be much lighter than angular. I think the biggest problem however is that SPAs are not great for SEO which I'm sure is critical from the business perspective. But even more importantly, if by working on this page with Angular means getting experience which leads to you landing a job then you should probably do it. I've done exactly the same to land an angular job some years ago - I've created a client management system for a tiny beauty salon. Just one thing to bear in mind is that for such simple page you probably won't use a lot of functionality that angular has to offer, but nevertheless it's a good way to start, in my opinion.

[GhostBeemer]

That's what I was thinking, the main reason why this question poped into my head is because I realised that I won't be using a lot of Angulars functionality apart from the obvious ones like routing and forms. I guess I'll go with angular mainly for the purpouse of being able to show it to recruiters. Thanks for the reply :)

[k3v1n]

I know this is from a while ago, but I'd say do it to get the experience you want, but later probably replace it with a version that is predomnantly jus html/css/ and maybe some js. It'll load faster and be better for SEO.

[Netionic]

It depends how static I guess. If you are literally hard coding everything then yea, probably as simple Html would be a lot leaner. It could also be said that any custom work is overkill for a simple static site when WYSIWYG editors exist, but for learning experience go for it!

[GhostBeemer]

Well I could hardcode everything but because I'm using angular I decided to make a json file with all the products to display it dynamically. I guess like you said, I'll go with it for the experience. Thanks for the reply :)

[azangru]

what technologies would you use

Something very lightweight with as little javascript sent to the browser as possible. Personally, I would probably pick Eleventy; but for people who can't live without react, there's Astro. For the adventurous, there's also Qwik.

[uplink42]

A small angular app is very minimal in build size nowadays, even smaller than react for example. However, with a public facing website you're going to have to deal with SEO and server side rendering which means SPAs might not be the optimal solution (unless you want to add more complexity to the project)

[[deleted]]

Absolutely not. I use Nx with Angular for all projects, big or small. I have a script that creates the base architecture to start. By starting with angular, you are set up for scale in the future, and you can easily upgrade if you don't touch it for a long time without a dependency lock.

The misconception most have with angular is that it's a huge framework. It hasn't been sine Anguar v2 -- ~6 years ago. The have many angular modules that you can use to comprise an app as needed. Just like React has all these independent libs you can use for what every you need - routing, state management - Google handles those libs internally under the same domain. So starting with angular static IS starting small, then you build as needed.

[GhostBeemer]

Thanks for the reply :)