Mailing-List: contact allura-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: allura-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jsteele@geek.net designates
 74.125.149.151 as permitted sender)
Date: Thu, 9 Aug 2012 18:14:01 -0400
From: Jenny Steele <jsteele@geek.net>
To: allura-dev@incubator.apache.org
Message-ID: <200881DEA7694C0781E1FD7FCE4BCCA1@geek.net>
Subject: What about changing allura's css to use sass?
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="50243629_12e685fb_a26f"

--50243629_12e685fb_a26f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Right now, Allura's css is mostly in one big file. At about 2700 lines, it =
isn't very friendly to work with. The css that's currently in there was act=
ually generated from a closed source package using Sass. What do you guys t=
hink about putting the .scss files in Allura and making that a part of the =
package?

Originally, we decided not to use Sass in Allura because it would be an ext=
ra dependency to install and maintain. The benefit is it would make working=
 with the theme or creating custom themes for new installations a lot easie=
r.
--=20
=3D=3D=3D=3D
This e- mail message is intended only for the named recipient(s) above. It=
=20
may contain confidential and privileged information. If you are not the=20
intended recipient you are hereby notified that any dissemination,=20
distribution or copying of this e-mail and any attachment(s) is strictly=20
prohibited. If you have received this e-mail in error, please immediately=
=20
notify the sender by replying to this e-mail and delete the message and any=
=20
attachment(s) from your system. Thank you.


--50243629_12e685fb_a26f--