Add to template

meetdilip

How about using an input box in ACP ( just like customCSS box in wordpress ) where people could input CDN /JS / CSS file links so that it is directly included in the relevant template ? For example you to add AngularJS, you can simply do it by adding Angular's CDN link to the box. Would handy in my opinion.

jordanjay29

I think it'd be better practice to add angular at the extension level. An extension could even be written to allow common libraries to be added with a single click. But I think allowing it in a generic input box is asking for trouble.

luceos

csf using my own .css file

i hope you mean .less file, otherwise all styles by extensions will be thrown out of the window or you'll have a difficult task maintaining your stylesheet.

In general I agree with jordanjay29 , allowing things like Angular is asking for trouble.

meetdilip

Someone at some point is going to ask help to include js or css file to add more features to Flarum. Instead of going to template and edit it to add those links, we can simply give a box in ACP. Just my opinion.

Davis

I was actually thinking about this the other day. There's a box for custom CSS, why not a box for header links? It could make things easier for minor changes.

meetdilip include js or css file to add more features to Flarum

This is a dangerous statement. Features should be added with extensions. I could imagine linking a CSS document or Google Analytics, but anything past that isn't the best option.

csf

Davis I could imagine linking a CSS document

Yes!

I would much prefer being able to override CSS using my own .css file — (edited in the comfort of my editor of choice and managed via our repo) — instead of having to use the somewhat cumbersome override field. :{

csf

Related to the .css file field, I would also like to see a field for overriding typeface selection. For example, if someone wanted to use Google Fonts, there should be a way to add those links in the head.

csf

luceos What I mean is something just like the "Customize CSS" feature, but instead of a window in the admin-side, make it a field where we can upload a .css file instead. Or maybe it pulls from a new folder/file, (/assets/custom/override.css), where we can work on CSS with more comfort than the clumsy override panel that exists. Flarum can then do whatever it wants with the override.css file, just like it does now with our raw CSS overrides. Same idea. The nice thing about this is it gives use the ability to use whatever editor we want for CSS overrides, and can easily see the override file in a GitHub repo, for example.

(I've mentioned it elsewhere, but I'm one of the few souls, apparently, that thinks CSS compilers are just a solution to no problem that ever existed. They just add a layer of complexity. Nothing wrong with regular CSS files.)

I don't know what @jordanjay29 is talking about, but it didn't have anything to do with my suggestion. Or at least I didn't write my suggestion knowing what Angular is. ?

luceos

csf compilers allow you to use variables and other dynamic things like shadow generators. The less compiler allows you to use the primary and secondary colors defined in the admin area all over your installation, including all extensions. Using raw css you'd lose all that.

csf

If you say so. "Shadow generators" sound like designer candy, not essential, and I find all the auto-coloring a little hard to work with in terms of being able to customize. And that's kind of my point... The tool should allow easy customization of presentation, and probably more people know how to do that with regular CSS than compilers. There are some colors that are hard coded now that I can't seem to override without effecting something else in relation. A minor annoyance, but I know it won't change so we can live with it. Functionally, we love the system. ?