Giter Site home page Giter Site logo

Comments (4)

argenos avatar argenos commented on June 7, 2024 1

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?

from obsidian-hub.

SlRvb avatar SlRvb commented on June 7, 2024 1

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

from obsidian-hub.

konhi avatar konhi commented on June 7, 2024

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?

from obsidian-hub.

konhi avatar konhi commented on June 7, 2024

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.

from obsidian-hub.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.