You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wouldn't it be helpful to add a file with screenshots and gifs to each css snippet that shows what the css change actually looks like in obsidian? I find it difficult to imagine how it will look in the end from the short description alone. This would allow users to quickly browse the repository for changes they want to apply without the need for copy, paste and and save them everytime.
I'd be happy to contribute some of the recordings, just let me know if you'd be interested in that.
(Also, is this repo still actively maintained?)
The text was updated successfully, but these errors were encountered:
Lagann311
changed the title
Suggestion: Add imge/gif for each snippet that shows what the css change looks like
Suggestion: Add image/gif for each snippet that shows what the css change looks like
Jul 20, 2023
One can always make it fancy as one likes, but the question is: is it worth it?
What is easier than just trying out a snippet and seeing the result? If you like it, fine, if not, just delete the snippet and you're back to square 1.
Remember, gifs and screenshots need to be maintained. Each time there is a major Obsidian update. like e.g. with 0.16 and 1.0, some of the gifs and screenshots need to be amended.
Regarding active maintenance, I believe it has been dormant for quite a while, one reason being …… admin/maintenance.
Hi,
Wouldn't it be helpful to add a file with screenshots and gifs to each css snippet that shows what the css change actually looks like in obsidian? I find it difficult to imagine how it will look in the end from the short description alone. This would allow users to quickly browse the repository for changes they want to apply without the need for copy, paste and and save them everytime.
I'd be happy to contribute some of the recordings, just let me know if you'd be interested in that.
(Also, is this repo still actively maintained?)
The text was updated successfully, but these errors were encountered: