obsidian-hub
obsidian-hub copied to clipboard
Central place for css snippets
As discussed on Discord, it might be a good idea to create a central place for CSS snippets, which would be:
- consistent
- containing examples
- organized
- tested
As suggested by @SlRvb, it could be done in this repo. Naming convention could be needed (@argenos).
I suggest that structure:
📁 05 - CSS snippets/
├── 📄 05 - CSS snippets.md
└── 📁 Bullet Point Relationship Lines
├── 📄 Bullet Point Relationship Lines.md
└── ⚙️ bullet-point-relationship-lines.css
@SlRvb @argenos what do you think about that?
- on Discord chat you said that it might be good to contain id in filename, but I'm personally not sure if it's really needed! Let me know what do you think.
- it was also said that we might need a way to keep name unique for different version of snippets, but is it really needed if we use git? Or maybe you mean different variations/customizations of these snippets?
I'm still unsure if we should be keeping CSS files under the hub. It feels like these would belong in a different repo. Perhaps we can bring those markdown files from the other repo via a script?
Yeah, a separate repo for the css files seems like the best way to go about it, but I think the MD files should stay on the hub repo not in the css one. Maybe on the css repo, a pull request should link to the md pull request on the hub?
Or maybe just a folder under the 05 - CSS Snippets called CSS for the css files so this wouldn't require multiple mini folders or wild scripting/pull requests to sort through?
📁 05 - CSS snippets/
├── 📁 CSS
| └── ⚙️ bullet-point-relationship-lines.css
├── 📄 05 - CSS snippets.md
└── 📄 Bullet Point Relationship Lines.md
It seems that we have an agreement that it would be best to create a separate repository for CSS Snippets, then!
I also agree that the .mds should be in obsidian-hub.
I suggest creating something like css-snippets.json that would be alike to jsons from obsidian-releases, so we would have a consistent workflow, e.g. with scripts.
If you find this idea good, we could discuss about needed fields!
Maybe on the css repo, a pull request should link to the md pull request on the hub?
Do we need a note to every snippet in the moment of uploading it to the second repo? I think that if it wouldn't be mandatory, contributors could first gather snippets and then other things would be progressively added.