Customisation: Self-hosted CSS
I understand why you guys have taken the approach that you have for Tender customisation in restricting the declarations that you can make, but I find it pretty restrictive and a pain to work with. Ideally, I would just just @import a CSS file that we host in order to make the customisations that we need. I think there are a couple of advantages to this:
- It keeps it in our version control, without the annoyance of wondering if the version pasted into Tender is in fact the latest, and vice-versa.
- It makes actually making customisations much easier since you can much more easily work in your own editor without having to hack around with the likes of the Web Developer toolbar.
As I say, I do understand the difficulty, but perhaps this could be extended to paying accounts who you have details for (ie. not trial accounts)?
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Tony on 05 May, 2010 04:02 PM
Oh, one other related thing I meant to mention: quotes in CSS currently get turned into HTML entities, so something like:
font-family: "Lucida Grande", sans-serif;
...ends up as
"Lucida Grande", sans-serif;
Or similar. I presume it's down to the text filter.
2 Posted by Justin on 06 May, 2010 11:45 PM
Hey Tony,
The quote escaping looks like a bug. Thanks for the report.
In regards to your first question, we've talked allowing external stylesheets, but we're still on the fence. Custom CSS, while a great feature, has been the source of a lot of pain and frustration for us and our customers. Tender is a constantly evolving application and it's hard for us to make updates to the frontend without breaking sites that use custom CSS. So we end up rolling out frontend changes a lot less as a result. We have to solve this problem first. We need a better way to allow those who want to use custom CSS to preview upcoming changes before they happen. Once we get that in place, then we want to consider allowing external styles.
Will closed this discussion on 18 Aug, 2010 10:15 PM.