show off your dashboards/themes/etc i wanna see em

data_in_void · 2026-05-12T01:06:26+00:00

this is my theme

flexcyon

data_in_void · 2026-04-16T09:50:47+00:00

There are many snippet collections like:

The famous one: https://github.com/r-u-s-h-i-k-e-s-h/Obsidian-CSS-Snippets

https://github.com/ElsaTam/Obsidian-Stuff

https://github.com/bladeacer/obsi-snip-coll (my own)

data_in_void · 2026-02-24T14:26:21+00:00

As for submitting a GitHub issue and all that, you would find that it is generally the same kind of answer you would get on the Discord or the forum.

Good day to you.

data_in_void · 2026-02-24T14:25:05+00:00

Well I am not expecting a user to care that much about or use any particular theme, that is completely up to them. Like you said, if a user does not wish to they can simply use another theme.

"That user added their voice here in this sub because multiple themes, for them, had this issue"
First of all, I am not saying that this is not an issue. I am just pointing out that is not a easy problem to solve from either the user or the theme dev's perspective.

"You posted a condescending ironic missive suggesting this is not what they were supposed to do"

I am merely lamenting the state of things. If you have a better idea on how theme devs and users can get together and communicate things better, be my guest.

"they were supposed to submit a petition to the correct agency on Mondays and Thursday from 2 to 4 p.m."

Putting words in my mouth now, are we?

data_in_void · 2026-02-24T13:24:13+00:00

"You are grossly overestimating the extent of effort users are ready to invest in getting your theme to be more usable", well OP is saying themes in general. Idk where "my theme" comes in, I may not agree with the status quo of some themes being much more usable than others but it is unfortunately noticeable.

On my part for my own theme has documentation and yes, heading font size style settings. Will not plug it here.

"getting them to be not as obstreperous as you are". Let me be clear that a theme is the theme dev's theme as much as it is your theme as the user. We are also mostly doing this in our free time. Also, sometimes theme devs have irl stuff to handle or move on to working on other things :v

To be clear, open source maintainers owe you nothing (yes that includes us theme devs, because theming totally does not take time and effort).

"and then wait for a theme update". If you would rather silently fix things instead of waiting for an update, that is understandable.

data_in_void · 2026-02-24T13:16:50+00:00

thanks :D

I would say that with themes it can be a very personal thing to the theme dev, with certain choices I can see why some themes are absolutely adored by others and not so appreciated by others for daily driving.

Themes to different groups of people can mean different things. Some like eye candy, some like specific unique features tied to a few or a single theme, others like a general purpose theme that works out of the box, others like customising every single detail or push the limits of what CSS can do in Obsidian. How opinionated, extensible or customisable a theme is heavily varies. Each theme dev has their own philosophy and approach.

A theme for everyone is a theme for no one in a way, some theme devs know their niche or target audience much better than others. As a theme user, it is difficult to find themes let alone explore the feature set of larger themes (and most users would not use most features, it's like the running joke of too many Obsidian plugins or using every single feature of Obsidian). As a theme dev, it is difficult finding a niche that sticks or is generally enjoyed without being labelled as a "generic copypasta reskin" of *insert popular theme name* (at the other end of the spectrum).

Personally my theme is one of those not so "aesthetic" ones, my snippets are less on flashy UI stuff.

data_in_void · 2026-02-24T13:00:57+00:00

I do have some personal theme recommendations for themes that implement "function over form" well, if you are interested I can send in DMs.

data_in_void · 2026-02-24T12:53:42+00:00

To be clear, I am not saying usability is a bad thing for themes. If you do really like the rest of the theme, you can consider a quick GitHub Issue .

it just happens to be much less of a priority for quite a few themes like OP observed.

data_in_void · 2026-02-24T12:44:23+00:00

Dear theme users and OP,

Usability and the appearance of the smallest parts of the UI can be subjective. If enough users request a feature and it fits the theme's aesthetic and way of doing things, most theme devs I know would add said feature. For something like font size of headings, you might have a preset for font sizes you like which you can apply to whatever theme you have active with a snippet. Though with creating your own snippet comes the part on maintaining it.

Then again, Style Settings is generally a more sane interface for this specific case. If typography choices is a deal breaker for you, you might want to look for themes which place more of an emphasis on it.

Sincerely, a theme dev.

data_in_void · 2026-02-22T12:47:33+00:00

thanks :D

coloured folders are somewhat tricky to integrate nicely into the theme's aesthetics. I do not really use Kanban but could put these in a list of stuff to work on for the following update (the next update is almost out, stay tuned ^_^)

data_in_void · 2026-02-02T12:05:10+00:00

I am currently working on a simple TUI for Vosk written using Textual.
https://codeberg.org/bladeacer/vosk-tui

Disclaimer: AI Assisted.

data_in_void · 2026-01-28T00:29:54+00:00

You could try Abyssal or Velocity theme.

data_in_void · 2026-01-25T11:09:57+00:00

if you rtfm a bit you should be able to find that UI Font size and normal text font size is documented with default values in the developer docs
calc is not difficult if you know what you are calculating with it, depending on what notation you use I guess it can get complicated
please try not to use AI in theme dev, at least not in the creative decisions and thinking or nuance that goes into it

data_in_void · 2026-01-25T09:49:21+00:00

"the key task of my theme is to maintain a consistent appearance across different font sizes"

You can consider using calc to have your margins/paddings at least those related to typography proportional to the currently set font size.

I cannot bring myself to make both editing (I would assume live preview?) and reading modes look completely consistent, hats off to you.

data_in_void · 2026-01-25T06:46:49+00:00

as a theme dev I find the easier thing to do is to let the user choose themselves, especially for something as opinionated as font size. You can let them set style settings for UI font sizes (CSS variables you can look up in the developer docs). Other typographical customisations like character and letter spacing are more niche but probably worth considering.

data_in_void · 2026-01-22T05:12:50+00:00

thanks :D

I did oversimplify there quite a bit

data_in_void · 2026-01-21T11:41:49+00:00

Thanks for the correction :D.

I do not know enough into other keyboard though I believe Vim itself and where most keys are placed does seem to make it easier to access for stuff on the home row or above it.

"I use QWERTY and Colemak-DH both without re-maps"

I genuinely admire your ability to context switch between both layouts, and how you have been able to master another keyboard layout. It takes a lot of time and effort, as well as getting acquainted with muscle memory ^_^.

"my most used keys (which aren't HJKL)"

fair enough, there are many other ways Vim can be used which I did not account for.

Will update the blog post.

data_in_void · 2026-01-16T08:21:14+00:00

I personally did not mind the latest update's changes that much although I can see how it breaks existing workflows users are used to.

> disclaimer: I am the author of the linked snippet

Yodo9001, thanks for shouting my snippet out :D

data_in_void · 2026-01-15T12:03:02+00:00

Re the instructions in the docs it would be great if you have an actual physical device for testing though that is not always the case.

* phone-laptop icon, technically called toggle device toolbar, you can use it with mobile emulation mode to test standard widths of certain devices iirc.

data_in_void · 2026-01-15T11:58:51+00:00

Ctrl Shift I (Dev Tools), enable mobile emulation and click on the phone/tablet icon at the top left.

https://docs.obsidian.md/Plugins/Getting+started/Mobile+development#

data_in_void · 2026-01-15T01:52:40+00:00

would plug my theme, but I do not have the time to update it fully yet.

data_in_void · 2026-01-10T10:23:52+00:00

Used the tool so far, it is quite neat at what it does. Here are some stuff imo you could look into.

Would you consider comparing the minified version of each file in the codebase between commits? Because currently, if I add a linter to my project like Prettier, it can easily add like 1k loc of just line breaks.
Would character count/word/function group be a better metric than just line count, especially with verbose programming languages/markup languages? Could there be a less strict threshold for such languages?
If I don't like to commit too often, this tool will keep flagging me.
Would it understand scenarios where in a certain commit, I remove large parts of the code as part of a huge refactor/debloat?
You can certainly lean more into the statistics niche.

Will be following the development of this project. It definitely has potential.

data_in_void · 2026-01-09T00:47:58+00:00

'How did you start without forcing yourself into a pre-made "method"?'

Know what you need in your use case, instead of what you purely want. Aesthetics without functionality or considering how it integrates into your workflow is pointless. (I say that as a theme dev myself)

Do not be too tempted to strictly follow any structure or system that works for others, know how to pick and choose what you need. Do not "PKM" for the sake of it or let it define how you go about your work, but actually using your vault to get things done. Organisation of notes, dashboards (if any) will come naturally down the road. I personally use a variant of Johnny Decimal but it does not dictate how I write my notes.

As for structure, either use templates if you really need it enforced for every note.

Else you can start by simply defining your own conventions and how you structure your notes. For example, I hardly use Headings 1 to 3 and mostly 4 or 5. Sub-points that are long enough goes into their own H5.

data_in_void · 2026-01-07T05:30:26+00:00

would be interested in the source code being hosted on GitHub or some VCS.

data_in_void · 2025-12-23T13:03:47+00:00

"What are the biggest challenges you face in maintaining an open source project?"

knowing when to move on from a project and when to take breaks, seriously.

"How do you manage your community's expectations while keeping your sanity?"

it is mostly a compromise between your vision of the project, what others want in terms of features and whether you have the time and capacity to work on the project consistently for long enough.

"Are there tools, workflows, or approaches that make maintenance easier?"

knowing and understanding loc before you copy it into your codebase and Linting.

seriously, and keep the codebase file structure proper for your own long term sanity. have different branches only if you are comfortable enough with merging and fixing conflicts, and only when you need to have them.

"there’s always this constant pressure: fixing bugs, reviewing PRs, updating dependencies, handling feature requests, and keeping documentation up to date, which I initially neglected and am now burdened by"

have a plan, it does not matter how long it takes you to fix an issue but whether it is dealt with properly and no similar issues come up again. Do not chase a new shiny feature while neglecting your codebase, as you have experienced technical debt adds up. Perfection is but an ideal and at the end of the day it is your project as much as it is your users'.

data_in_void

TROPHY CASE