With the exception of the sheet1.css file is it possible to modify the names of the other stylesheets FW creates e.g. main.css, index.css, 2column.css etc.?
Six writes three CSS files - the specific page styles, the master page
styles, and the user styles. Page styles depend on the page name and user
styles are set in the Inspector, but you know that already.
You can create more than one user sheet that you can write an extended
reference to, but you must force FWP to publish it - by creating a dummy
page which invokes it.
I think some actions make their own external css files - Walter would know
more I think as I’m thinking he has a couple which do that.
I have no credible intel yet on how 7 works, though I bet master pages
still drive me bonkers.
–
Ernie Simpson
On Wed, Sep 10, 2014 at 5:01 PM, Todd email@hidden wrote:
With the exception of the sheet1.css file is it possible to modify the
names of the other stylesheets FW creates e.g. main.css, index.css,
2column.css etc.?
It seems I’m SOL. At first blush it looks like I need more control over all these ‘sheets than FW is capable of providing, or so it would seem. I don’t want to waste a lot of time on this as I have nothing to gain so please return to your regular programming.
Todd
Six writes three CSS files - the specific page styles, the master page
styles, and the user styles. Page styles depend on the page name and user
styles are set in the Inspector, but you know that already.
You can create more than one user sheet that you can write an extended
reference to, but you must force FWP to publish it - by creating a dummy
page which invokes it.
I think some actions make their own external css files - Walter would know
more I think as I’m thinking he has a couple which do that.
I have no credible intel yet on how 7 works, though I bet master pages
still drive me bonkers.
–
Ernie Simpson
On Wed, Sep 10, 2014 at 5:01 PM, Todd email@hidden wrote:
With the exception of the sheet1.css file is it possible to modify the
names of the other stylesheets FW creates e.g. main.css, index.css,
2column.css etc.?
Hi Todd,
As Dave suggests you could use the Externalize Action to give you much of what you want but you will have to ‘get out and push’ for part of the way. The workflow looks like this;
Set the site to use internal CSS styles
Attach the Externalize Action to your page(s) or master page(s)
Once your site is done manually consolidate the external CSS files into a single (or multiple stylesheets)
Tell the Action to disable all of Freeway’s own CSS styles
Attach the sheets created in step 3 back into the site
Thanks Tim, the Externalize action is damn useful.
I was to a large extent able to achieve my initial goal (Woo-hoo!), though I was hoping for (expecting) more native control over ‘sheet names and publish locations. I was pleasantly surprised to see that what I’m trying to do is in some ways a more robust extension of what Externalize does. Interesting.
Ultimately, although it works I’m not sure this is worth pursuing simply because the workflow is so non-WYSIWYG. Personally I have no problem with that but then I’m not a FW user. At best it might only appeal to that minority group of adventurous FW users (I’m thinking single-digits) who like to get more hands-on with their projects. I don’t want to waste time writing a tutorial and making videos for what’s essentially 2 people who I’m sure could figure this out on their own if they really wanted to.
Hi Todd,
As Dave suggests you could use the Externalize Action to give you much of what you want but you will have to ‘get out and push’ for part of the way. The workflow looks like this;
Set the site to use internal CSS styles
Attach the Externalize Action to your page(s) or master page(s)
Once your site is done manually consolidate the external CSS files into a single (or multiple stylesheets)
Tell the Action to disable all of Freeway’s own CSS styles
Attach the sheets created in step 3 back into the site
Hey Tim, have you tried this action with Perch? There are a few Perch stylesheets that I have to remember not to screw around with or it’ll break some of the Perch enabled pages—primarily Perch Gallery and Blog. This sounds like it could be a good solution for me.
I rather doubt I’ll be taking this any further (videos etc.). Your action seems a more FW-friendly approach anyway. If you’re curious contact me off list.
Todd
Totally understood Todd. Be sure to share your video when you are done. I’d be interested in seeing what you have to offer.
I’ve not had a chance to try Perch yet although I keep meaning to give it a go. If you try the Action with Perch and get stuck feel free to get in touch.
Regards,
Tim.
On 11 Sep 2014, at 16:05, RavenManiac wrote:
Hey Tim, have you tried this action with Perch? There are a few Perch stylesheets that I have to remember not to screw around with or it’ll break some of the Perch enabled pages—primarily Perch Gallery and Blog. This sounds like it could be a good solution for me.