Thats a genius idea for making sure none of the elements goes our of viewport width. I always had this issue that a div has standard border padding, and width:100% pushes its right to out of viewport. Can't wait to try this.

Just few genuine questions, as I am learning, specifically in making static fixed header bars for few of my fun projects.

Does the meta tag in ur comment needs closure(>), or is it something I might have never come across?

Does implying a max-width 100 in percentage means every element gets max 100% of "its" parent element, which can be traced down back to HTML as super parent of all tags, and thus if I could use "vw" viewport width as units instead of %?

> I always had this issue that a div has standard border padding, and width:100% pushes its right to out of viewport.

You likely want `box-sizing: border-box`: https://www.paulirish.com/2012/box-sizing-border-box-ftw/

> I always had this issue that a div has standard border padding, and width:100% pushes its right to out of viewport.

What you probably want, in addition to the max-width, is

    box-sizing: border-box;

Then the border is included in the width calculation.

> Does the meta tag in ur comment needs closure(>), or is it something I might have never come across?

If you're writing XHTML, then you need to end the tag with /> instead of >. But for HTML5, it's valid as is. And browsers get it right either way.

> Does implying a max-width 100 in percentage means every element gets max 100% of "its" parent element, which can be traced down back to HTML as super parent of all tags, and thus if I could use "vw" viewport width as units instead of %?

That's a good question. I'm not familiar with the vw unit, but yea, that sounds basically right.

Yeah, if I don't find anybody, I will try to do it by myself. The backend will be made in Spring and I thought about using some template engine, like Thymeleaf to do the front. But I'd prefer to work with REST APIs.

I'm a long time backend java developer who has always struggled with frontend tech. The situation today is actually pretty nice; with bootstrap (or other) you can get a "decent" looking site with very little effort (ie better than raw html). And if you just want to work with API, there are a few jquery ui base widget libraries around[1] I've used in SPA's before. Good luck!

[1] http://www.jeasyui.com/

If you want to work with REST APIs, it might be good for you to create a SPA application. The easiest thing to start seems to be Vue right now. With vue-cli with it's build command.

https://github.com/vuejs/vue-cli/blob/master/docs/build.md

Just create a single `.vue` file, run it with `vue build file.vue` and you can immediately just start hacking around. It can be even built that way for production.

Feels simple like in the old days with single index.html, but you aren't missing any features of modern frontend stack.