I read the section about skins in newsletter studio documentation before I post my topic. I discovered there is no separate skin-file (html/css) because neewsletter studio stores skins (html/css) in the database. I will proceed with backoffice interface newsletter studio provides.
Yes, that's true at the moment, would you perfer it to be stored on disk? I can see both pros and cons with that but a big plus would be that one could work in Visual Studio with the template...
at the moment we are discovering skin and template functionality in newsletter studio, and what is the best way they work together in "best practice". If you have any hints/additions to that and clarification in your documentation of newsletter studio that could be helpful for anybody who uses/intends to use your extension in umbraco.
I would say that this really depends on how skilled the editor are.
The skin can be used for css, header and footer or just for the css. While the templates makes it possible for you as a developer to predefine some layouts. This will keep the editor from having to create the same table structure over and over. Another good feature is to rightclick a newsletter in the sent folder and click "Create new newsletter this this" which will grabb all the content from that letter and create a new one.
Newsletter Studio Skins
Hi,
where can we find the css-File for a newsletter studio skin?
Hi Thomas!
Thank you for trying the package! Please let me know what you think about it and provide me your feedback!
You can download the documentation from here: http://our.umbraco.org/FileDownload?id=4797
On page 11 theres a section about the skins that you will find as a tab inside the settings-page.
// Markus
Hi Markus,
I read the section about skins in newsletter studio documentation before I post my topic. I discovered there is no separate skin-file (html/css) because neewsletter studio stores skins (html/css) in the database. I will proceed with backoffice interface newsletter studio provides.
Hi!
Yes, that's true at the moment, would you perfer it to be stored on disk? I can see both pros and cons with that but a big plus would be that one could work in Visual Studio with the template...
// M
Hi Markus,
at the moment we are discovering skin and template functionality in newsletter studio, and what is the best way they work together in "best practice". If you have any hints/additions to that and clarification in your documentation of newsletter studio that could be helpful for anybody who uses/intends to use your extension in umbraco.
Thomas
Hi!
I would say that this really depends on how skilled the editor are.
The skin can be used for css, header and footer or just for the css. While the templates makes it possible for you as a developer to predefine some layouts. This will keep the editor from having to create the same table structure over and over. Another good feature is to rightclick a newsletter in the sent folder and click "Create new newsletter this this" which will grabb all the content from that letter and create a new one.
is working on a reply...