Along with the screenshot, if the config file or parts of it could shared that would be great. So others can copy things they like instead of spending time figuring out. For instance, what is the theme used above.

@milindnirgun FYI that's the default theme from core/style.lua.

And I just noticed the text overlapping on the left instance's status bar. Sounds like something that could use a fix :)

so now we gonna rice lite-xl now? hold my beer.

Cool! I guess it is from macOS but I didn't know the OS can be customized to this extent.

Otherwise the syntax highlighting for tsx is not really working well, we have the same problem than with jsx. We have some progress to make in this direction.

I was also thinking that we should make the default font size bigger. I think everyone is increasing them as one of the first thing they do.

here's where you're wrong! that's KDE and i3-gaps.

LOL I was sure I was going to be wrong!

@franko Indeed, it is not MacOS, gotcha xD It is KDE + i3-gaps :)
And yes, the color syntax for tsx/js is not really present, and for me, it is quite important !
The default size is something that could be easily modified (Ctrl + Scroll), so, for me, it is not a priority :)

Here is another screenshot for your website/docs if you want !
Cheers

I thought that's the original point of this discussion? for it to be used in readme (or in website)

I wanted to use it in the readme and also see what people was doing in term of customization. What font they was using etc.

For example I personally love FiraSans and FiraCode but also found JetBrainsMono nice.

There's no problem for me ! You can use my screenshots wherever you want ! I'd be honored !

You are right that people contribute what they want to but I expect that contributors that are in the organization use a fraction of their time to do important but boring things and the rest of their time doing the fancy things they love.

Yes, that's what we've doing! Over the span of last two days, we've been filling up the Features and FAQ pages because the number of "how to do X or Y" questions are increasing in Discord. We also setup CI to use some custom plugins that would make keys look good. We're planning to add more docs (I was going to write a API overview).

Now we're just discussing the possibility of filling screenshots page. We're not writers, we don't just sit down and suddenly have ideas. I for example only knows Views and some core things. If I were to write an API overview, I would need to dig into other places as well (Highlighter, Doc). The process isn't immediate.

There's literally two of us working to update the website. People are constantly asking for docs and it has been tiring for us. Please cut us some slack.

@adamharrison made a great job implementing multi-cursors and it would be nice if some of the contributors took the time to write at least a paragraph in the documentation or the landing page about that. I would do that myself I just lack the time unfortunately.

You're looking at the wrong place. Multi cursor is currently only documented in Features page. We haven't work on the landing page yet.

he said or the landing pageso it's fine, it's a feature so it's where it should be IMO, maybe someone could make a post in the blog about it and also on each release eventually.
The site was made to show just a gallery in the home page and the blog news, which I think is more than fine as is.

You are right that people contribute what they want to but I expect that contributors that are in the organization use a fraction of their time to do important but boring things and the rest of their time doing the fancy things they love.

Give them time, I was expecting that too but also I know it bother people to spend time for docs instead to code or else.
I did the site also for fun, it's more fun to make a gallery than write technical stuff...
Documentation is the most important thing, if something is complicated and the author doesn't explain how to use it then people will simply not use it, in my case I wrote a wiki for the website and adding stuff while people like Takase help out.

OT: (sorry but while at it): not to mention that nobody is payed here, so I think there should be some rule about contributions and related documentation, or you have to maintain stuff that people will not without knowing how it works (thinking on other contexts where it is a source of pain).

Yes, that's what we've doing! Over the span of last two days, we've been filling up the Features and FAQ pages because the number of "how to do X or Y" questions are increasing in Discord. We also setup CI to use some custom plugins that would make keys look good. We're planning to add more docs (I was going to write a API overview).

Apologies, my bad, I was not aware of the work you have been doing on the website. This is not an excuse but I was looking at the landing page and I thought there was no new content. I guess I should also add notifications to see when some modifications are done in the website, just to be informed.

I thought we may include the gruvbox dark and light themes with the default provided color themes.

Yeah, we already include the dark variant. A PR to the colors repo of the light variant would be good.

As for the mononoki font, I don't think we are going to change the JetBrains default font but in theory we may include the mononoki font with the release package so that people may easily test it.

I don't think adding fonts we don't actually use is a good idea.
We could suggest to download the font as an example of how to change the font used in the editor tho.