-
Notifications
You must be signed in to change notification settings - Fork 9
Support for themes #3
Comments
I would suggest that allowing for custom styles should maybe be on the roadmap before templates. |
Hmm. I never really thought about custom styles, but yeah, you're right. That would make a lot of people happy, for little cost. That seems a pretty straightforward implementation: add a |
I dive into the codebase of pastel. I think this the part where we can customize it? Maybe we can add a config file and put there a list of custom css styles paths [
'css' => [
get_css_link_tag('highlight-darcula'),
'path-to-my-custom2.css',
]
] This way we can disable the Related: knuckleswtf/scribe#113 |
Is there any progress on CSS styling? |
No, it's not been a priority. I'm working on Scribe v3, which will likely include that support directly. |
Identical to knuckleswtf/pastel-js#1
Our templates are written in Blade, but other than that, it's the same requirement. If a new theme is added to one library, it can easily be ported to the other.
The text was updated successfully, but these errors were encountered: