May I suggest to save user defined css to a file saved in a specific path?

for example if user John_Doe submits a customized css, save it in /<server_path_to_static_files>/css/users/john_doe/override.css

then in the head of the html file load the user defined css always after the default one.

this way is always static, and the result is cleaner than any <style> tag...

my two cents.

regards

Giulio.

Il 26/08/2013 18:42, Chris Lawlor ha scritto:
The simplest solution is probably to keep all of the CSS that users can't customize in an external file (to be served as a static asset), but move anything that's user customizable to the <head> of your base template, in a <style> tag. You'd probably want to implement some sort of caching for user style preferences, assuming these won't be changing often.

On Sunday, 25 August 2013 22:08:11 UTC-4, Robin Lery wrote:

    Oh! I am sorry. What I meant was, how do I let users customize
    their page if they wanted to? I suppose I could have done this
    without using external stylesheet, but yes, CSS is served fastest
    if it's static. I hope, I made myself clear. Please guide me if
    there's a way to achive this


    On Mon, Aug 26, 2013 at 5:39 AM, Andy McKay <an...@clearwind.ca
    <javascript:>> wrote:

        Any string can be rendered as a template. This is covered
        pretty well in the docs:

        https://docs.djangoproject.com/en/dev/ref/templates/api/
        <https://docs.djangoproject.com/en/dev/ref/templates/api/>

        For example:

        >>> from django.template import Context, Template
        >>> t = Template("body { background-color: {{ bgcolor }} }")
        >>> c = Context({'bgcolor': '#999'})
        >>> t.render(context=c)
        u'body { background-color: #999 }'

        However, CSS is served fastest if it's static and on a CDN and
        not using a template and CPU resources to render.
-- You received this message because you are subscribed to the
        Google Groups "Django users" group.
        To unsubscribe from this group and stop receiving emails from
        it, send an email to django-users...@googlegroups.com
        <javascript:>.
        To post to this group, send email to
        django...@googlegroups.com <javascript:>.
        Visit this group at
        http://groups.google.com/group/django-users
        <http://groups.google.com/group/django-users>.
        For more options, visit
        https://groups.google.com/groups/opt_out
        <https://groups.google.com/groups/opt_out>.


--
You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.


--
 Giulio Calacoci - 2ndQuadrant Italia
 PostgreSQL Training, Services and Support
 giulio.calac...@2ndquadrant.it | www.2ndQuadrant.it

--
You received this message because you are subscribed to the Google Groups "Django 
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to