Rikki

I am onboard with IPS for long, and here is my positive feedback on the current state of the nation:
 
- I love the strategy of moving from Pure forum to communities, with a tightly integrantes set of apps. This was a crucial move that allowed IPS to escape from the fierce competitivo on a shrinking market. As everybody knows, fóruns are disappearing, yet people are still getting together. This is why i prefer IPS package Over XF ir VB because there is a whole set of tightly packed tools to get my people collaborating.
- I love the new theme. "Oh it's too white" "oh só much white space"... For me it is definitely a great step forward. Is ir perfect? No, but it was definitely a major step forward!
- Integrations! We are not alone in the cyberspace, and there are many great apps and services out there. Integration with Zapier will be a major leap um interoperability and would allow IPS users to extract more value of their communities. I am looking forward to see IPS on Zapier, it os just taking too long.
- Support. Has been great. Thanks!
 
 
There is also less positive aspects, most related to pricing, business and evolution of the compromise with customers through time,  but now it is not the time to talk about that.

It's under Customization -> Appearance -> Icons & Logos.
As for push notifications, I'm not sure what our plans are on that.

We already have PWA support, though that doesn't include push notifications yet.

We are a way off of offering a white label service still - we plan to get the main app stable and add more functionality first. We'll post an announcement when we're ready to accept some interested sites 🙂 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

Oh that's right, this is what you'd need:
@media screen and (max-width: 767px) { body { zoom: 0.8; } }  

@opentype to the rescue 🙂 

But it just hide all mobilenavbar, incude the area where contain links and menu. What I need is, just hide the logo row, and move the menu to the same area of links or breadcumb.
Now it fine, I have the code apply incorrectlly....

1) In your mobileNavBar template, add this just before the closing </ul>:
<li> {template="mobileNavigationIcon" app="core" group="global" params=""} </li> 2) In globalTemplate, find the <header> tag and change it to:
<header class='ipsResponsive_hidePhone'>  

I agree!  I self host 2 forums and the IPS team has pulled me outta jams quite a few times!  Support ticket help is fast and accurate...and even here on the forums, I find the IPS Team very informative and helpful!! 
That goes for our peer to peer forum members too...help with forum functions, CSS and coding help is never far away with the talented group of forum members in this community!
Everyone...keep up the GREAT work!
 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

Just gotta throw it out there for any new potential customers, and to let staff know they're appreciated : 
Support : The few times I have ever needed support from Invision themselves, have always been answered in a timely manner, and "to the point focus", and I love it. Staff has always made a point of answering all my questions in a message, and I find that lacks in alot of other places. A+ support 🥰
Service : Out of 7 months of usage, I think we have experienced 1 "downtime" period, and for only a few hours. I currently use the Cloud package, and I gotta say it works pretty well out of the box, and is surprising what you can do with it 😉 Not to mention not having to worry about running the site it self is a huge relief 😂 
Keep up the great work!

4.4 used Roboto, 4.5 uses Inter.

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

Yeah, that is what I am saying. I am a software developer, and I understand design decisions that are made for a whole have different ramifications from design decisions that are made on a case by case basis.
But I also understand that your most core functionality needs to weigh heavily in those design decisions. Honestly, right now the system looks like it has a CSS file not loading or something.

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

That is fair. However, I was pointing out how (in my opinion) non-constructive your language was. Please... practice kindness when illustrating your points. 🙏 

In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to requirements.
It's pretty easy to take one particular page and find criticisms - but remember we are designing a suite where each page might have some shared functionality and some unique functionality. We have to design components that can work well in more than one perfect scenario. 

This post is... not the vibe.
There's a way to offer suggestions and offer constructive criticism versus call something "absolutely terrible" that people spent a lot of time and energy on. 

Yes, it’s my assessment that this layout is well-thought-out. (The one I commented, which was from Pages)
I work as professional web designer for more than 20 years and I customize these Pages templates all the time—inspecting every little detail, checking the flow of content in many situations and at every CSS breakpoint. 
Of course if you can’t have an open discussion and need to laugh at people just because they say something you don’t agree with, this discussion ends right here. If all you guys can do is judge a web layout in one desktop view, you know very little of web design and have a lot to learn, but with reactions like the one I quoted you are apparently not willing to. I am out. 

login issue is fixed, thanks!