New docs website - what works and what doesn't?

[rstoenescu]

Hello and Happy Holidays from the Quasar Framework team!

We are excited to announce the community preview launch of our new documentation website. This preview/beta version gives you a sneak peek at the design and features of the main site, which we will be launching in the near future. Besides many goodies that you will discover, it also includes a highly requested feature: dark mode. In addition to the sleek new design, the site now has a toggle that allows you to switch between "light" and "dark" themes.

A lot of work has been put into the new docs, not just for the looks but for the "engine" powering it too, but we will detail this later.

We hope this preview will give you a better understanding of how the site will look and function, and we welcome any feedback you have, preferably here on this forum post. What do you love about it? What do you dislike about it?

https://new-docs.quasar.dev - (temporary URL until we merge it into quasar.dev)

Thank you for your interest in Quasar, and we look forward to bringing you the full version of our documentation website soon!
PS: do not use this as your daily driver for the information on it may get out of sync

PPS: The new docs will get some updates from time to time. If anything appears out of place, it may be due to caching (which we haven't yet optimized for the new docs), so clear it. And enjoy!

PPPS: Major update deployed on February 28th. Lots of feedback has been implemented for which we are grateful. There is additional feedback to be taken into account in a future update.

PPPPS: Another major update deployed today (March 7th). If anything seems out of place, please clear cache. The cache has not been optimized yet and it's scheduled when we deploy the new website over the current one.

PPPPS: Another update deployed today (March 24th). If anything seems out of place, please clear cache. The cache has not been optimized yet and it's scheduled when we deploy the new website over the current one.

PPPPPS: Launched the new docs on our main domain quasar.dev (March 28th).

[george-dragnea]

It looks great, great work everybody.

Header
I like the new header, but I prefer to have only one menu because it's very crowded and on a laptop, it takes too much screen.
Also, that grey doesn't look modern, I would use smaller fonts.
Logo | Menu links | Search | Version selector

Homepage content
I would add some companies /projects that use quasar.

Footer
The footer is too big, I will keep only one row without content from docs.

[rstoenescu]

Thanks for the feedback

[d4ism3l]

Quasar has been a great job!! It is the best frontend framework, but i not have very good internet access. I can download doc for use offline at any way. Or maybe you cant create a docset for devdocs. That would be great. Thank you so must for that work.

[underdoeg]

Looking ok. the blue shadow under the header is a little dominant / distracting

[otabekoff]

Not only that but the ones under the cards too.

[IlCallo]

About the blue shadow, are you using it into light or dark mode?

[tohagan]

I like the colours and layout. I think the blue trim is needed to maintain your branding. Dark mode ... yey!!! Endorsements are great.

[1377sayaba]

It's amazing 🤩😍
But i can't waiting to see version 3 anymore
Does Anybody know about the time ?

[IlCallo]

We prepared Qv2 to allow a lot of internal refactoring without adding user-facing breaking changes
We'll probably push back Qv1 EOL and we won't start working on Qv3 until we stop supporting Qv1, but you'll still get a lot of goodies into Qv2 lifecycle :)

[adarshmadrecha]

Few cents from my side

1. When toggling the Dark Mode for a code snippet, it should be applied to either to that single code sinippet or all the code snippets. Currently its applied to entire website too.

2. Blue under the header is too much, also noted in this comment

[rstoenescu]

Thanks for the feedback.

The toggling of dark mode per code snippet only is unfortunately not feasible at this point.

[IlCallo]

About the blue shadow, are you using it into light or dark mode?

[MedEqz]

Quasar is an amazing framework and I love it, but the UI/UX of this docs looks terrible to me, more specifically the dark mode
It's not reflecting at all how good the framework is and it's too much far away from actual designs standards

[Seanitzel]

I have to agree with this.

I love Quasar, and it's hard for me to type this after thinking about the amount of effort you guys probably put into this new design, but i really don't think it does any justice with the level of the framework it self(sorry!).
I think that the best thing to do for Quasar to become a more popular framework would be to make a completely new design, and again i'm sorry and i know it's probably hard reading this.

If that is out of the question than i would take most of the feedback written here by other people.

I feel bad because i honestly feel Quasar would have been more popular if it had better UI.

Thanks for all the hard work you guys are putting into this <3

[IlCallo]

Hi guys, we welcome any practical suggestions, but there isn't much we can do about subjective feedback like those
We really focused more on branding, accessibility and UX at this time, starting from the feedback of past surveys

We'll collect more structured feedback in a couple months and act accordingly, after everybody has the time to explore the new docs in their day-to-day life

[MedEqz]

My main practical suggestion would be : keep it simple

• I feel that I have to understand how the doc works and is organized before the doc can help me
• Of course the documentation isn't the only reason that explain why quasar is so underrated but I am sure that this is one of the main
• Think about potential newcomers who want to compare Quasar with other tools, all they have to start is the documentation
• I think the new version looks better (only) in mobile view because objects and shadows are smaller and the spirit of the space and blue theme fits well. Unfortunatly we don't work on mobile (mostly ?)
• We have 2 navbar (with differents sub menu) + 1 sidebar with submenu, this is too much and I think some part doesn't have to be enhanced at this point on a technical documentation. Maybe you should set them apart on a dedicated web view ? (ex: Team, Blog, Sponsor, Roadmap ?) And delete at least 1 navbar
• So maybe the main reason is that you try to put too much in here while people just want to acces practical and technical information faster
• Concerning colors, shadows and fonts I can't make concret proposals because mine could be worse
• To finish, I don't think the "why to donate" and "how to contribute" have their place next to "layout and grid" and "vue components" on the sidebar, much less in first place. People who want to donate and contribute will do but not because you put these topic priority to others
• Maybe it should go into the dedicated page with "Team / Blog / etc." and let much space for prioritized things

I'm just trying to help as I can with my feedback and in any case, thanks for your work guys

[rstoenescu]

Thanks for the detailed feedback!

[ssuess]

• When switching sections (DOCS/COMPONENTS/etc) there is no indication which section you are in other than the URL. Menu items should be highlighted in some way
• 2 top bars of menus are not great, and the relationship between them is unclear
• Font choices and letter spacing are awkward and decrease legibility
• Agree with the above about the glowing blue, it is too much
• Agree with the above that Quasar is an amazing framework and deserves cleaner, clearer docs than this.

[rstoenescu]

Thanks for the feedback

[IlCallo]

About the blue glowing, are you using it into light or dark mode?
Can you share a screenshot of the parts where you feel it is too much?

[zanzara]

Personally I don't believe that it is up to the docs that this gem isn't more popular in the dev-land.
We all love Quasar and learned it with -- and managed our amazing apps with -- the docs that just exists!!!

Sure, everything could always be better. And dark mode is really a must-have nowadays having so huge screens 😄
But lets start with this next step of Quasar docs now.

[rstoenescu]

For sure. And it's not like we draw a line in the sand and say "this is IT". The docs will keep on improving, based on the feedback that we receive and also on our todo list which keeps on growing with ideas.

[euphemism]

One thing I have noticed is that on mobile the menu to open the right-side drawer with the table of contents is gone. It was nice to get an overview of the topics/examples for the current component being viewed and being able to jump down (potentially a long ways) instead of a lot of vertical scrolling.

[IlCallo]

This is actually good feedback, we should be able to bring this feature back later on

[rstoenescu]

This was already on my pipeline. Good to see someone misses it so I won't add it just for the sake of it :)

[rstoenescu]

...and pushed it. Will re-deploy the new docs tomorrow.

[rstoenescu]

Redeployed the new docs. If anything appears out of place, it may be due to caching (which we haven't yet optimized for the new docs), so clear it. And enjoy!

[ssuess]

I think one of the main issues with the new site is that it combines promotional material with technical documentation to the detriment of each (which are competing with each other strongly via the confusing menu structure). I think separating these more clearly (and using different design cues for each) would be a big help. The current site is mostly a decent reference site for developers with its sidebars and anchor links, but promotional pages should be conceived of differently (and removed from this structure). I could see this morphing into two sites which link to each other:

• quasar.dev: with welcome, layman's description, images, company support/promo, links to resources/docs. Would do this as single col layout, lots of white space, etc
• docs.quasar.dev or quasar.dev/docs: technical docs in similar style to current with left hand index, searchable info, anchor links, etc

The main vue site is a lovely demonstration of this kind of division actually: https://vuejs.org/

[rstoenescu]

One of the problems that we saw happening is some devs not understanding what Quasar is, who is it for and how to quickly get started with it, so we tried our best to offer more guidance. For a seasoned Quasar developer this might seem as information getting in the way rather than helping, but we need to take care of everyone regardless of their experience. However, we will take this feedback into consideration.

[ssuess]

Thanks. I hope you know I think the framework you guys have produced is the best I have seen and a joy to work with. I recommend it all the time, and want to help it be the best it can be.

[IlCallo]

VueJs docs are actually the ones we mainly took inspiration from, the new docs follow their same structure:

• the landing page leans more on the marketing-side, with a couple quick-start links and boxes explaining the framework features
• once you land on docs (https://new-docs.quasar.dev/docs), via link or via the search bar, you get the left drawer with technical-only sections. In the current docs, marketing and techincal sections are mixed instead

[MedEqz]

What about something like a "Quasar bootcamp" like Taylor Orwell did for Laravel Bootcamp ?
It could be a great idea to present all the major feature that deserve to be highlighted and define what Quasar is or could / should be according to Quasar Team

[ldiebold]

@MedEqz "Quasar bootcamp"? Nope, we don't need

• Assume most devs dislike subscription based.
• JavaScript ecosystem isn't PHP ecosystem and you probably know how Laravel became popular.
• PHP evolves and became complex.
• Most devs started learning from frameworks instead of starting from the fundamental.

There is a need to understand where Quasar fits in the space that is not a risk for business to adopt for the next 10 years.

Did you look at the link? The Laravel Bootcamp is not subscription based. It's basically just a free guide to help people get a grasp of the framework fast. Why wouldn't we want that?

I do know how Laravel became popular (I've co-interviewed Taylor, and have followed him and Jeffrey Way for the past 8 or so years). It was through coherence, dedication to a beautiful API and world class education. That's absolutely worth modeling. It's probably the best example we have of an open source framework building a robust, maintained framework that has zero concern for funding. Taylor has employees, one of which solely dedicates his time to Laravel's many free, open source projects.

@MedEqz something similar to this will likley happen this year, just takes time!

[suleimanas]

Marvellous, Great choice of color.
just one thing guys
compare the left menu in: https://new-docs.quasar.dev/components ( it's fixed on the left - easier to focus on - I'm getting old for sure :) )
and any other component page: https://new-docs.quasar.dev/vue-components/card/ (centered)

[rstoenescu]

Hi,

Thank you for the feedback. The landing, components & 404 pages are intended to occupy all the screen real estate, as opposed to the other ones which should not. And you might be asking why not? First of all, on wide screens you'd have the content in the middle and the navigation menu and TOC on the far left and far right sides, leaving a huge gap between each of the three page parts. The problem is exacerbated on ultra-wide screens. What we want to achieve is for devs to be able to navigate quickly without the eyes and mouse travelling too much, along with other UX & aesthetics considerations as well.

Also, as a side note not related specifically to the topic at hand but with implications on the current layout, you will notice that some pages have a TOC and some don't. On the previous docs the page content would jump horizontally when switching between pages with different TOC presence -- and now we fixed this and it doesn't jump anymore, considerably easing out the cognitive effort.

[otabekoff]

Personal opinions: It looks like that you switched the docs to oldest version. The current in use Quasar Docs is more functional and more beautiful and easier to use. Also, I didn't like the new colors, components selector (which has image cards like old style), the shadow which is dominant below some components like header and card. And BTW, the footer is so big :). The new font with lighter font weight is not well for eyes. Need to work on header. Also, its font sizes are big. Again, the second row of header is getting much of the space. The new dark teal and orange colors are not very welcoming. It's a tolerable Docs to say better than nothing.

[metalsadman]

it would be best if you put your points in a bullets (if many), so it's easier to gather said data later.

[FrankySnow]

I don't want to feel harsh on the people that made this new landing page, but to me this doesn't feel mature. That may be a good starting point, but needs to be improved a lot.

• Colors :
  • there's #00b4ff everywhere at full saturation ; it should be declined in a palette and used with more subtlety :
    • it causes too much contrast in the header with the dark background or the grey text
    • the blue box-shadow is disturbing : too opaque, too saturated, too much (as others said)
  • the orange #eb7434 feels odd too, especially with the blue box-shadow on the buttons
• Typography : too much letter-spacing on some blocks
• Layout :
  • I like the new header but the hierarchy between the 2 lines is unclear (maybe too much items)
  • the "Twitter cards" carousel UX is disappointing :
    • I don't want to click the arrow 15x or hold down 1s to advance 1 card
    • I want to be able to scroll horizontally or click 1x to advance 1 (or more) card
    • the UX would feel a lot more modern with CSS (or JS) scroll-snapping (that's something missing in a lot of Quasar components)
• Content/behavior :
  • why is there a hamburger menu on mobile to directly access the docs and not on desktop ?
  • why is there a dark/light mode toggle on pages where light mode is not available ? on mobile the tooltip is not visible because it is triggered on hover
  • the dark/light toggle on component examples should toggle only that component, not the entire website
  • there is a "Components" page (that lacks light mode too) that feels disconnected from the "Vue components" menu, it should serve as an index page for that menu
  • the "Why should you choose Quasar?" section on the landing page should serve as the main point of the landing page : extended with details and examples to show at first sight how awesome Quasar is, without the need to explore the docs

To emphasize the last point (and many others), I consider the React MUI landing page as the best example : modern look, good typography, balanced colors, interactive examples that one wants to play with.

I really think that Quasar deserves such a beautiful landing page and I'd be happy to help !

[rstoenescu]

Greatly improved the twitter cards scrolling. Will be available on next docs deployment.

[rstoenescu]

Thanks for all the feedback. Got a few comments:

why is there a dark/light mode toggle on pages where light mode is not available ? on mobile the tooltip is not visible because it is triggered on hover

Because when you first visit the website the header is the first thing that pops out. It gets the focus of the viewer and it's an opportunity for him/her to learn what the header can do. Should the theme switcher button not be there, this feature will be very hard to pick up later.

the dark/light toggle on component examples should toggle only that component, not the entire website

Not feasible at this point.

there is a "Components" page (that lacks light mode too) that feels disconnected from the "Vue components" menu, it should serve as an index page for that menu

The "Components" page was designed for dark mode only on purpose, just like the landing page. We could tweak it later for light mode also, but at this point it looks great only on dark mode. Also, it does not refer only to the UI Components. It's a place for newcomers to get acquainted to everything the UI has in store (directives, utils, plugins, etc etc) which all fall under the broader meaning of "components" (or "parts") umbrella. So bottom line, it doesn't quite fit as an index for the "Vue components" menu item, but it stands out on the header especially for the newcomers.

the "Why should you choose Quasar?" section on the landing page should serve as the main point of the landing page : extended with details and examples to show at first sight how awesome Quasar is, without the need to explore the docs

We'll continue on tweaking the landing page.

[IlCallo]

About the blue box-shadow, are you using it into light or dark mode?
Can you share some screenshots related to the points you noted?

[WCN-llc]

Hi!
The current version of the Quasar documentation is, in my opinion, beautifully done!
I use the documentation all the time during development, and the current documentation site is open.
Working with the documentation all the time is not tiring. Everything is in harmony:

1. the height of the top panel is normal, which increases the space to view the documentation.
2. the main menu is on the left, and it is immediately clear that - "there is everything here". Search and find!
3. the left menu is well divided into logical sections.
4. good font and font size. Well done color accents and contrast of text and page background.
5. The right menu on the pages is smaller in width, and it is clear that it is secondary and relates specifically to the current page.
   Etc.

The new design, unfortunately, has lost many of these advantages.

Maybe, with all due respect to your designers, put out a contest for designers, and have the community vote on the options?!

[rstoenescu]

Thanks for the feedback. We'll take all points into consideration.

[markc]

Ooh, my first impression is this is "kiddie candy" for gamers or something. Like Discord. The thick faded blue separator under the header and on top of the footer is way too much. It should be just a thin blue line like under the subject headings in the footer. I like dark themes in general but the dark blue, in this case, is discordant with typical dark themes (ie; Vue docs) so I would have to switch to the light theme, BUT, the general text color is too light, especially on the LHS nav pane. Some of us are getting old and even glasses do not help so little more contrast and slightly larger font sizes would be appreciated. Last niggle, the front page of new-docs runs my Chromium browser at 40% cpu usage.

[rstoenescu]

Thanks for the feedback.

[rstoenescu]

The CPU usage is due to the stars in the background being animated.

[zuck]

Without all of that blue-glow is now starting to look better...BTW next steps are using Montserrat just for headings and something more standard for body text, remove all that weird letter-spacing and adjusting a little bit font size and colors:

The version selector should stay at left, IMHO, for quicker access.

Regarding the landing page, if you want to make it more visually catching, maybe an inspiration can come from GitHub one:

[guilhermeaiolfi]

Exactly, that font for content seems a bit off. It is too big making some content to overflow:

Some combinations of colors/size is not as sharp as an standard font:

(See number 7 and number 1 in the version badge)

[IlCallo]

Font-size has been increased to 16px to fix readability issues and match with other framework documentations

[rbeeli]

For the light/dark mode switch, consider using the one from the vue.js docs: https://vuejs.org/guide/introduction.html. It's more intuitive IMO, and why not align with vue?

Also, the default theme should be the system theme, or light, but not dark. Very few docs use dark theme as their default, so why going on a design adventure and change this established practice?

TBH: It does not feel like a seasoned designer has created this page, sorry for the harsh words, but that's my impression. It lacks consistency. The UX is bad, there is no reason to have two menu bars in the header. DOCS and COMPONENTS? What's the difference?

I would highly recommend to separate the technical docs from the marketing material and start page. Now it tries to serve everything in the same place, making it just confusing and annoying. Once you do that, there will be no need to have two header menus either.

Also, these buttons just look ugly:

Gray border on metallic blue?

[IlCallo]

I'd suggest you to check out this question and the provided questions

You'll find many answers about what feels strange to you

[sullyD64]

Hi guys, I'm really digging the new look after the recent round of fixes. I was a bit skeptical in the beginning and I didn't like it that much, but I think that we're now going in the "right" direction. The main focus is now more clear than before (it's a developer-oriented documentation, after all), and the flashier, marketing-oriented design features are less heavier on the eyes.

I'd like to thank @rstoenescu, @IlCallo, Dreamonkey and everyone involved for listening to the community's feedback, even the harsher ones.

With that being said, I'd like to spend my two cents, because I really see the potential in this new site and I think we're really close to perfection. My feedback is mostly typography oriented, since I believe that's the main pain point that still needs to be fully addressed. Let's go:

• Drop Montserrat in docs pages in favor of a more "default" font family, such as Roboto or Inter. Roboto is Material Design's default font (and even the default font in Quasar CLI scaffolded apps and Quasar UI components), so i think it's a good fit, since we claim to implement Material Design. Inter, on the other side, is Vitepress' default font, and appears in virtually every major Vue related doc site (vuejs.org, vitejs.org, vueuse.org, windicss.org and so on), so it's instantly recognisable by Vue developers. I really like the standout vibe Montserrat gives in the homepage, but I think it's a bit harder to read in everyday use than Roboto or Inter.
• Increase the space between the three main columns in the doc layout. I feel the main content is a bit cramped and a bit claustrophobic, this is especially true in content-heavy pages (think of QTable or quasar.config.js)!
• Decrease font size on the right TOC. Again, this is to ensure the TOC acts as an overview of the page. The rule of thumb is that the TOC should almost never overflow to the bottom of the screen. I think the spacing between toc elements is ok.
• Decrease font size on the left menu. This should be larger than the TOC but smaller that the main content.
• Increase the space before headings. This is also to reduce density and provide more space in long pages.
• Consider "flipping" the horizontal line after every heading (line first, then heading text). This again helps better separate different sections.

Regarding the "marketing" section:

• I really don't like the look of the Components cards. The letter spacing in titles and descriptions is way too much. I can understand why it is like this, because with a smaller font size or spacing there would be too much whitespace. Then why not make every card smaller? Instead of using a 4-column grid, can we consider making every card smaller, so maybe we can fit up to six (or even eight) components on a single line? I think having smaller cards gives a better feeling of "whoa, there's a lot of stuff here" than having to deduce that by looking at the size of the scrollbar. Scrolling is boring!

• Regarding the usage of QChips to filter components:

  1. it's not clear that I can use them to filter the components (maybe add a little text hint?).
  2. I think the light blue background should be darker here, the contrast with the white label is not optimal.
  3. Why don't we give every chip a different color, and use them as "tags" on the component cards, so it's even more clear that each component belongs to a different group?

• Last but not least: I think the homepage suffers the same problem of the component cards in terms of letter spacing. The blue, uppercase headings and the three "feature cards" are hard to read, at least i find it hard to read them without imagining this voice, lol. But that's personal taste, I see what you're going for here, I don't personally like it, but I think i'll come to accept it we just dial it down a bit :)

Overall, again thank you if you've reached this point. I'm 100% confident we share the same bigger picture and want the best for Quasar, as a framework and as a community. Let's reach for the stars 🚀 !

[IlCallo]

Thanks for the polite and precise reply :)
We're aware there still are some things to fix and we'll keep listening to the community even after the stable release of the new docs is out

We are already aware of some of the issues you mention, but we want to check out if they're shared by the majority of the community before acting on them, as there are some tradeoffs (readability vs performance) which we are still evaluating

[WCN-llc]

As far as I understood the purpose of the new design is to attract as many users as possible and, as a consequence, to increase the financial support of the project.
In my opinion, this is a good goal and it is well deserved.
But I think that by changing the design - the goal can not be achieved!
I think the goal should be formulated as "if you do business with Quasar - you don't need anything else!
And now an example:
I want when creating a project template to "select":
Material Design 3.
GraphQL and Rest Api at the same time
and so on.
And this in Quasar out of the box - no!
When I start working on a project, I want:
q-pa-xs-md - it's there!
q-xs-fixed - that's not there!
text-h2 - it's there!
q-text-xs-[25px] - that's not there!
and so on!
In this sense, Quasar competes with Tailwindcss, for example.
I don't understand the logic: why in Quasar I can set fields depending on the size of the screen, but fonts and position can't!
I also want a graphics component and I want to create a youtube clone and I need a video component! - this doesn't exist!
And in practice it turns out the following: Quasar helps a lot, Quasar is good, but as soon as "a little to the side", then the "tambourine dance" begins!

I'm sure that we need to concentrate not on a new design, but on standardization and expanding capabilities!

[septatrix]

This is not directly about the new docs but a request for a feature I would really like:

One aspect I have grown to love from Vuetify are offline docs. I.e. their docs are a PWA and cached for offline. This is very helpful when developing on-the-go (e.g. train) without a (stable) internet connection.
If this is (understandably) out of scope for the redesign, would it be okay to create a separate follow-up issue for this?

[rstoenescu]

We had (and still have) that before them. When we'll merge the new docs over the current ones it will work as SSG + PWA. Right now, the new-docs subdomain is used for feedback only and not optimized.

[Deadstronaut]

[IlCallo]

Hey there, thanks for the kind words, but this discussion is only meant to provide feedback about the new docs UX, so we won't answer here about other feature requests or unrelated bugs, or missing/wrong content
Please open a new discussion, for feature requests, or an issue, for bugs
Or you can ask these questions into our Discord server, using the proper channel for each

When we search for components search animation is very attractive but can you put a back button to _**new-docs.quasar.dev/component**_s address?

It's not really clear what do you mean, can you attach a couple screenshots to better explain the problem and the desired behaviour?

[bonatoc]

DO not go white on black, it's atrocious, just like the font.
What's with this black thing everywhere?

There are much better designers (or for that matter, css pre-made themes, including... Quasar's own!) than this out there, I'm sorry if I'm hurting someone's feelings, but this is way too subpar when compared to the professional, well designed, super-fast tool that Quasar is.

Please don't do this.

The docs are just perfect as they are.

It was an error to close the forums and go to Discord.
Google is not crawling new quasar code excerpts anymore.
And like it or not, search is still an important discovery tool for many devs.

[rstoenescu]

The docs have both "light" and "dark" themes. Just use the one that you like.

[lodembeep]

The new docs is awesome ! However i would suggest to move the sidemenu to the extreme left in order to give more space to the core content, as of now, on a 1900x resolution the text size is way too small and there are many gaps.

Between the blue lines, the elements should be centered, otherwise it feels tilting.
The red areas are the gaps i mentioned.

Would be nice to have these implemented :)

Beside of that, the documentations is sooooo much better than before.

[lodembeep]

Thank you guys, it is waaaay better now <3

[lodembeep]

would it be possible to center the menu items ? the blue pipes in the screenshot. My OCDs painfully hurt me whenever i see the menu.

[smolinari]

@lodembeep - I'm personally not sure of what you mean. Can you clarify some more please?

Scott

[lodembeep]

@smolinari
Since english is written from left to right, the navbar should be aligned either from left to right or centered, otherwise it makes people like me (who also write from right to left) feel a bit off.

And on another, more personal feeling, i think that navbars should always be centered.

Something like that :

[smolinari]

Ah. Ok. I see what you mean now or rather understand what you initially wrote. The centered menus looks good to me too. We'll see what the rest of the team and Razvan think.

Scott

[rstoenescu]

Another update deployed today (March 24th). If anything seems out of place, please clear cache. The cache has not been optimized yet and it's scheduled when we deploy the new website over the current one.

[guilhermeaiolfi]

The responsive width made the whole difference. That's a lot nicer now. I can see me using it. Thanks for listening to us.

[sullyD64]

Way to go folks! Thanks for listening to our feedback.
A quick one, something's off with the nested QMenus in mobile viewport (chrome for Android):

[rstoenescu]

Thanks for reporting this! Fixed it and re-deployed.

[rstoenescu]

Thank you all for your feedback!

I've just merged the new docs into quasar.dev and I'll open up a new thread in Announcements about this. Should you feel the need, please comment there instead as I will lock this thread.

You'll get the new docs as soon as your PWA updates it. If you don't want to wait, uninstall the current instance of it.

[rstoenescu]

Thank you again to ALL of you for caring and contributing with your feedback! Your involvement was key to making the docs as best as possible. And remember that this is just the first step. We will keep on improving it!

Thank you, beautiful community!