Gnome + pop shell extension. Normal i3 tiling keybinds. All the following bindings include super. w for tabbed layout, f1 for calculator, f2 for Firefox, f3 for nautilus, f4 for settings, f5 for package manager. D for search which I can use like dmenu but much better. Shift+s for screenshot. Shift+q to quit application. I program with in the terminal so I need tiling for keyboard-only use. when I first used i3 I underrated tabbing. It solved nearly all of my problems with tiling.

Kwin: meta+left, meta+right, meta+screenup

Thats it. For the rest I use a taskbar and buttons

sway with tabs (i usually dont use actual tiling)+4-5 workspaces

waybar for status display and on mobile also for menu access

rofi as the app launcher (i also plan to write a proper rofi menu for my phone for quick access to useful commands/config but it’s heavily wip)

i patched sway for push to talk because wayland spec doesnt support keybindings in a way required for push to talk for now

i also plan to patch it on the phone to completely forbid fullscreen apps (as they hide the menu which i use for workspace/window switching) and show the window bar on all windows (for example, firefox extension/downloads popups)

I have an binding for my terminal, my Emacs and a general fuzzy selector for apps or SSH hosts. I generally operate with everything full screen with windows sorted across 10 named workspaces across 3 monitors.

Sway config: https://raw.githubusercontent.com/stsquad/dotfiles/master/dotconfig/sway/config

I have a very unusual workflow. In addition to not stacking windows, I don’t minimize them either. Instead, I spread them out over many workspaces. Per workspace, I usually only have 1 or 2 windows, but I ‘group’ workspaces to keep semantically related windows together.
And I do that, by having all workspaces in a column and just placing windows in neighboring workspaces + leaving workspaces empty between the groupings. I also have a minimap for my workspaces in my panel, to just keep track of all of this.

I like this workflow a lot, because it maps semantics to location. It feels like a desk where you just place related documents next to each other and might place some documents more in the middle, others in a faraway corner.

This is in contrast to the traditional Windows workflow or the workflow that many tiling folks use, where the first workspace is for web browsing etc…
Those use groupings based on the kind of task you do in them (often effectively being tabs in an application), like web browsing. They don’t group by the topic, e.g. you might frantically research ants and use a separate browser window, separate text editor etc., all grouped up for ants.

Now, traditional use of workspaces does allow this grouping by topics, by just assigning each workspace a topic. But personally, I found that too static.
Like, yeah, I have some larger, completely distinct topics, but often I’ll just quickly research bees and that’s kind of ant-related, but doesn’t need to be fully mixed with that either. I’d rather just place it to the side of the ant stuff.

deleted by creator

Former Xmonad user here.

I had two 5 screens and two columns. One screen was for terminal emulators, one was for writing code and software development, one was for my web browser, 2 others were for miscelaneous things, but most often were for working with files a GUI file browser like Nautilus or Thunar, or for reading PDF files in Evince, or reading PowerPoint or Excel documents in LibreOffice.

On each screen the tiles were always in 2 columns. The left for doing work, writing code, prose, drawing graphics and charts, interacting with the CLI, and so on. On the right was documentation: manual pages, PDF files, HTML documents, sometimes the MPV video player window when watching a tutorial that I was able to download from YouTube.

The right column usually had no more than 3 windows open, they started to get too narrow to be useful if more than that were open. I would occasionally horizontally split the left column as well, usually when going back and forth between two documents I was editing.

However…

I did not use this workflow once I started using Tmux, and then I continued not using this workflow when I switched to Emacs. The reason is of course because Tmux and Emacs both provide their own tiling windowing system that operate within a single application window. So my main workflow was always in a single maximized terminal window, or a single maximized Emacs window, or a single maximized GIMP window. Only occasionally would I un-maximize these windows, but then to keep it from getting too small, I would set it in “floating window” mode. Also my web browser, PDF reader, GIMP, LibreOffice, all worked better in full-screen (maximized window) mode. Even Thunar (GUI file browser) has multiple tabs, and a multi-column mode which was useful for the very few times I ever needed a GUI file browser.

At one point, I actually changed my tiling window manager configuration to always open windows maximized, except for Thnuar (GUI file browser) which would open in floating mode, not tiling mode. At that point I finally realized that I don’t really using a tiling window manager at all, it is just there managing windows the same as a non-tiling window manager would do.

I switched back to the Xfce default window manager, and quit worrying about window managers all together.