-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR add support for metadata #15
Comments
This would have to be customizable, as not everyone will want the same metadata. Maybe it makes more sense to add support for plugins like Templates and Templater, so you can template out anything you want? And you could insert it anywhere you want in the CSS file? |
I'm still voting for a simple way to add basic metadata such as author and source. We want to encourage users to add that information. It could be on/off setting, on by default. See Modal form plugin. |
What kind of metadata are we talking about here? Just a fixed text to be inserted into every new CSS file? Or some other kind of template stuff asking/querying for values? Thinking out loud this would require a setting section for the plugin having:
This could possibly require a simple template engine, where we defined:
And one could then choose in the settings whether to use a fixed value, or ask for values when creating the new files. Am I way off, or is it something like this you're imagening @maggaou ? |
From implementation point of view that would suffice however life would be slightly easier with keyboard navigation between input fields and possibly with some predetermined values like date. Modal form may provide the desired functionality. In more general point of view the idea is to promote describing source information. This would in turn promote github repositories, subreddits, discord servers, other discussion forums and individual users. This one simple feature would do a favor to various parties. |
I don't think it's realistic to have a modal form within a CSS editor, that's what the rest of Obsidian is for, so the question should rather be what would truly be the necessity to contain within the CSS file itself and what should be kept on the outside. And possibly a better extension, which I'm not sure if it can be done, would be to create a working link from within the CSS file back into the vault where one could have all the information in the world about this given CSS file. |
Metadata for author, date and source link. This could be implemented by comments (I'm not sure about the native properties feature). Ask these details when running create css command. Providing additional command to add/edit metadata could be other choice but this adds more clutter to the general command pool.
The text was updated successfully, but these errors were encountered: