html newsletter generation module

[shanehill]

Hi folks,

We are using a newsletter generating module that lets one cruise around their drupal nodes and select them for inclusion in newsletter content.  then you create some intro text and click a button and then you get a text and html newsletter ready for sending out to your constituents via civimail.

the module is pretty nifty.

Agaric consulting created it last year for us.  thanks Agaric. :)

http://www.agaricdesign.com/

what I am wondering about is if the community thinks it would be worth the time to generalize this module and release it.  is anyone interested in this?  is there a module that exists that maybe does the same thing?  i have not looked much because we are pretty happy with our module.   what do people use for generating html newsletters for civimail usually?

-Shane
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Emily Frazier]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I for one would be extremely interested in this! It's just what my org is looking for!

On 8/2/07, Shane Hill <shane@...> wrote:

Hi folks,

We are using a newsletter generating module that lets one cruise around their drupal nodes and select them for inclusion in newsletter content.  then you create some intro text and click a button and then you get a text and html newsletter ready for sending out to your constituents via civimail.

the module is pretty nifty.

Agaric consulting created it last year for us.  thanks Agaric. :)

http://www.agaricdesign.com/

what I am wondering about is if the community thinks it would be worth the time to generalize this module and release it.  is anyone interested in this?  is there a module that exists that maybe does the same thing?  i have not looked much because we are pretty happy with our module.   what do people use for generating html newsletters for civimail usually?

-Shane
____________________________________________________________
You received this message as a subscriber on the list:
    civicrm-dev@...
To be removed from the list, send any message to:
    civicrm-dev-unsubscribe@...

For all list information and functions, see:
    http://lists.civicrm.org/lists/info/civicrm-dev

--
Emily E. Frazier
Access Technology Consultant

802 999 6553
emily.e.frazier@...

Skype :: emilyefrazier  
AIM :: emilyatretn
Gtalk :: emily.e.frazier
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Ryan Barolet-Fogarty]

We would be very very interested in this for use at our org.  Being able
to use existing Drupal nodes makes this one better than even the usual
Wysiwyg rich text editors.  If you could generalize it, we would use it!

Haven't heard of Agaric before... going to check them out now!

Ryan
Quixote Center

On Thu, 2007-08-02 at 08:31 -0700, Shane Hill wrote:

> Hi folks,
>
> We are using a newsletter generating module that lets one cruise
> around their drupal nodes and select them for inclusion in newsletter
> content.  then you create some intro text and click a button and then
> you get a text and html newsletter ready for sending out to your
> constituents via civimail.
>
> the module is pretty nifty.
>
> Agaric consulting created it last year for us.  thanks Agaric. :)
>
> http://www.agaricdesign.com/
>
> what I am wondering about is if the community thinks it would be worth
> the time to generalize this module and release it.  is anyone
> interested in this?  is there a module that exists that maybe does the
> same thing?  i have not looked much because we are pretty happy with
> our module.   what do people use for generating html newsletters for
> civimail usually?
>
> -Shane
> plain text document attachment (message-footer.txt)
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[prickeke]

I would be interested if this could scrape blog posts from a Wordpress
site instead of Drupal nodes and do all the rest.

--
Keith

On 8/2/07, Shane Hill <shane@...> wrote:

> Hi folks,
>
> We are using a newsletter generating module that lets one cruise around
> their drupal nodes and select them for inclusion in newsletter content.
> then you create some intro text and click a button and then you get a text
> and html newsletter ready for sending out to your constituents via civimail.
>
> the module is pretty nifty.
>
> Agaric consulting created it last year for us.  thanks Agaric. :)
>
> http://www.agaricdesign.com/
>
> what I am wondering about is if the community thinks it would be worth the
> time to generalize this module and release it.  is anyone interested in
> this?  is there a module that exists that maybe does the same thing?  i have
> not looked much because we are pretty happy with our module.   what do
> people use for generating html newsletters for civimail usually?
>
> -Shane
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>
>

--
Keith A. Prickett
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[msn]

Why not publish this module in Drupal.org as a module, so all of us can have advantage of it?

I am interested because of my "not payed" web and crm activities for non profit and fundraising organisations like "the Terry Fox run"" in the Netherlands. I am develloping a new website with Drupal and CiviCRM + Civimail for relation management. At this moment the newsletter devellopment is in the pre phase. The current site (not Drupal) can be found on http://www.terryfoxrungroningen.nl.

I am interested but I - and the people behind the organisation of the TF run - don't have the cash to pay for it. Our funds are for Cancer research (current project: cancer research for young-adults).

regards
Martin



 

Shane Hill wrote:

Hi folks,

We are using a newsletter generating module that lets one cruise around
their drupal nodes and select them for inclusion in newsletter content.
then you create some intro text and click a button and then you get a text
and html newsletter ready for sending out to your constituents via civimail.

the module is pretty nifty.

Agaric consulting created it last year for us.  thanks Agaric. :)

http://www.agaricdesign.com/

what I am wondering about is if the community thinks it would be worth the
time to generalize this module and release it.  is anyone interested in
this?  is there a module that exists that maybe does the same thing?  i have
not looked much because we are pretty happy with our module.   what do
people use for generating html newsletters for civimail usually?

-Shane

____________________________________________________________
You received this message as a subscriber on the list:
     [e-mail]
To be removed from the list, send any message to:
     [e-mail]

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Emily Frazier]

Hey Shane,

I was just wondering if this has gotten released yet? My org is more than eager to integrate this, as CiviMail is falling short of our needs in terms of image integration. I think this would be the best solution for us!

Let me know if/how I could help to move things along, or if I could possibly see this module in action somewhere.

Thanks!
Emily

On 8/2/07, Keith A. Prickett <keith.prickett@...> wrote:

I would be interested if this could scrape blog posts from a Wordpress
site instead of Drupal nodes and do all the rest.

--
Keith

On 8/2/07, Shane Hill <shane@...> wrote:

> Hi folks,
>
> We are using a newsletter generating module that lets one cruise around
> their drupal nodes and select them for inclusion in newsletter content.
> then you create some intro text and click a button and then you get a text
> and html newsletter ready for sending out to your constituents via civimail.
>
> the module is pretty nifty.
>
> Agaric consulting created it last year for us.  thanks Agaric. :)
>

> http://www.agaricdesign.com/

>
> what I am wondering about is if the community thinks it would be worth the
> time to generalize this module and release it.  is anyone interested in
> this?  is there a module that exists that maybe does the same thing?  i have
> not looked much because we are pretty happy with our module.   what do
> people use for generating html newsletters for civimail usually?
>
> -Shane
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>
>

--
Keith A. Prickett
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

--
Emily E. Frazier
Technology Integrator

802 999 6553
emily.e.frazier@...

Skype :: emilyefrazier  
AIM :: emilyatretn
Gtalk :: emily.e.frazier
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[shanehill]

On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> Hey Shane,
>
> I was just wondering if this has gotten released yet?

no.  not  yet,   we are very busy getting ready to launch the SMTP
service.  we will get to it as soon as possible, lots of orgs want
this.  :)

we will announce when it is ready.   :)

-Shane
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[shanehill]

Folks,

I have included a description of our newsletter module below along
with the things that need to done before it can be released.

if someone or some group in the community wants to step up and
generalize the module let me know.

if anyone has a better idea than what is described below, please speak up.

if I hear nothing, at some point, when time allows, we will generalize
and release the module.

peace,

-Shane


===================
Tasks
===================
# the data and presentation layers in the code are all mixed together
which makes it impossible to use templates at the moment. so those
layers need to be abstracted from one another

# I would like to include a few templates that are known to be "safe"
in major email providers like google, yahoo and AOL.  The big
providers will strip and mess with the css and other html elements and
it can be a real pain to get things working well.  so providing some
basic vanilla templates that work well with the the big email
providers might be nice.


======================
Module Overview
======================

The module allows for certain node types to be included in a mailing.
in our system currently, this is facilitated through two categories
(vocabularies), a "newsletter" node type and custom module code
called, you guessed it, "newsletter":

newsletter issue (category)
newsletter section (category)
newsletter (node type)
newsletter (drupal module)

to make a node available in a mailing, the node type must be added to
the categories.

the process for creating a newsletter goes as follows:

   1. Add a new term to the newsletter issue category (vocabulary)
that correlates to the mailing that will be sent (we have 12
predefined that are the monthly newsletters)

   2. The user creates node content of the various types that have
been assigned to the above mentioned categories.

   3. When the node is saved, the user chooses to assign it to a
particular newsletter issue and a particular newsletter section in
that issue.  This is done for all of the nodes that will be included
in a particular newsletter.

   4. next, the user creates a newsletter node that would serve as the
actual newsletter.  when they do this they are given a list of choices
that are the terms in the category that have *not yet* been associated
with a mailing.  the user chooses the appropriate term (mailing) and
saves the node (newsletter).  when the node is accessed in the future
it aggregates all of the node content that was assigned to the
newsletter issue and displays the content (there are ways to define
article teasers, etc.)

   5. next the user will use the custom newsletter module to create
HTML and text versions of the newsletter.  the html version is "safe"
for google, yahoo. and aol such that the css ans styling are not
stripped.   the flow for this is pretty simple.

          * the user is presented with a list of newsletters in the system,
          * the user chooses a newsletter and a version(text or html)
(at some point there will be a choice for a template here)
          * the user clicks the generate button and they are presented
with a textarea that is filled with the newsletter content from start
to finish

   6. The user needs to copy the content of the two newsletter
versions (text and html) and create two files that will be loaded into
civicrm.  these two files can be tweaked as necessary for presentation
reasons.

   7. the user then goes though the standard civimail process for
sending the emails.


On 8/23/07, Shane Hill <shane@...> wrote:

> On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> > Hey Shane,
> >
> > I was just wondering if this has gotten released yet?
>
> no.  not  yet,   we are very busy getting ready to launch the SMTP
> service.  we will get to it as soon as possible, lots of orgs want
> this.  :)
>
> we will announce when it is ready.   :)
>
> -Shane
>

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Emily Frazier]

Thanks for sending this along, Shane. It sounds like just what we are looking for. I have just one question. How does this deal with images? If you have an image in a node and then copy it into your HTML file for Civimail, do the images come through in the mailings?

Thanks again,
Emily

On 8/23/07, Shane Hill <shane@...> wrote:

Folks,

I have included a description of our newsletter module below along
with the things that need to done before it can be released.

if someone or some group in the community wants to step up and
generalize the module let me know.

if anyone has a better idea than what is described below, please speak up.

if I hear nothing, at some point, when time allows, we will generalize
and release the module.

peace,

-Shane


===================
Tasks
===================
# the data and presentation layers in the code are all mixed together
which makes it impossible to use templates at the moment. so those
layers need to be abstracted from one another

# I would like to include a few templates that are known to be "safe"
in major email providers like google, yahoo and AOL.  The big
providers will strip and mess with the css and other html elements and
it can be a real pain to get things working well.  so providing some
basic vanilla templates that work well with the the big email
providers might be nice.


======================
Module Overview
======================

The module allows for certain node types to be included in a mailing.
in our system currently, this is facilitated through two categories
(vocabularies), a "newsletter" node type and custom module code
called, you guessed it, "newsletter":

newsletter issue (category)
newsletter section (category)
newsletter (node type)
newsletter (drupal module)

to make a node available in a mailing, the node type must be added to
the categories.

the process for creating a newsletter goes as follows:

   1. Add a new term to the newsletter issue category (vocabulary)
that correlates to the mailing that will be sent (we have 12
predefined that are the monthly newsletters)

   2. The user creates node content of the various types that have
been assigned to the above mentioned categories.

   3. When the node is saved, the user chooses to assign it to a
particular newsletter issue and a particular newsletter section in
that issue.  This is done for all of the nodes that will be included
in a particular newsletter.

   4. next, the user creates a newsletter node that would serve as the
actual newsletter.  when they do this they are given a list of choices
that are the terms in the category that have *not yet* been associated
with a mailing.  the user chooses the appropriate term (mailing) and
saves the node (newsletter).  when the node is accessed in the future
it aggregates all of the node content that was assigned to the
newsletter issue and displays the content (there are ways to define
article teasers, etc.)

   5. next the user will use the custom newsletter module to create
HTML and text versions of the newsletter.  the html version is "safe"
for google, yahoo. and aol such that the css ans styling are not
stripped.   the flow for this is pretty simple.

          * the user is presented with a list of newsletters in the system,
          * the user chooses a newsletter and a version(text or html)
(at some point there will be a choice for a template here)
          * the user clicks the generate button and they are presented
with a textarea that is filled with the newsletter content from start
to finish

   6. The user needs to copy the content of the two newsletter
versions (text and html) and create two files that will be loaded into
civicrm.  these two files can be tweaked as necessary for presentation
reasons.

   7. the user then goes though the standard civimail process for
sending the emails.


On 8/23/07, Shane Hill <shane@...> wrote:

> On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> > Hey Shane,
> >
> > I was just wondering if this has gotten released yet?
>
> no.  not  yet,   we are very busy getting ready to launch the SMTP
> service.  we will get to it as soon as possible, lots of orgs want
> this.  :)
>
> we will announce when it is ready.   :)
>
> -Shane
>

--
Emily E. Frazier
Technology Integrator

802 999 6553
emily.e.frazier@...

Skype :: emilyefrazier  
AIM :: emilyatretn
Gtalk :: emily.e.frazier
____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Matt Chapman-7]

I think I could put a bounty of $800 or so on this project, if that
would help...

-m

Shane Hill wrote:

> Folks,
>
> I have included a description of our newsletter module below along
> with the things that need to done before it can be released.
>
> if someone or some group in the community wants to step up and
> generalize the module let me know.
>
> if anyone has a better idea than what is described below, please speak up.
>
> if I hear nothing, at some point, when time allows, we will generalize
> and release the module.
>
> peace,
>
> -Shane
>
>
> ===================
> Tasks
> ===================
> # the data and presentation layers in the code are all mixed together
> which makes it impossible to use templates at the moment. so those
> layers need to be abstracted from one another
>
> # I would like to include a few templates that are known to be "safe"
> in major email providers like google, yahoo and AOL.  The big
> providers will strip and mess with the css and other html elements and
> it can be a real pain to get things working well.  so providing some
> basic vanilla templates that work well with the the big email
> providers might be nice.
>
>
> ======================
> Module Overview
> ======================
>
> The module allows for certain node types to be included in a mailing.
> in our system currently, this is facilitated through two categories
> (vocabularies), a "newsletter" node type and custom module code
> called, you guessed it, "newsletter":
>
> newsletter issue (category)
> newsletter section (category)
> newsletter (node type)
> newsletter (drupal module)
>
> to make a node available in a mailing, the node type must be added to
> the categories.
>
> the process for creating a newsletter goes as follows:
>
>    1. Add a new term to the newsletter issue category (vocabulary)
> that correlates to the mailing that will be sent (we have 12
> predefined that are the monthly newsletters)
>
>    2. The user creates node content of the various types that have
> been assigned to the above mentioned categories.
>
>    3. When the node is saved, the user chooses to assign it to a
> particular newsletter issue and a particular newsletter section in
> that issue.  This is done for all of the nodes that will be included
> in a particular newsletter.
>
>    4. next, the user creates a newsletter node that would serve as the
> actual newsletter.  when they do this they are given a list of choices
> that are the terms in the category that have *not yet* been associated
> with a mailing.  the user chooses the appropriate term (mailing) and
> saves the node (newsletter).  when the node is accessed in the future
> it aggregates all of the node content that was assigned to the
> newsletter issue and displays the content (there are ways to define
> article teasers, etc.)
>
>    5. next the user will use the custom newsletter module to create
> HTML and text versions of the newsletter.  the html version is "safe"
> for google, yahoo. and aol such that the css ans styling are not
> stripped.   the flow for this is pretty simple.
>
>           * the user is presented with a list of newsletters in the system,
>           * the user chooses a newsletter and a version(text or html)
> (at some point there will be a choice for a template here)
>           * the user clicks the generate button and they are presented
> with a textarea that is filled with the newsletter content from start
> to finish
>
>    6. The user needs to copy the content of the two newsletter
> versions (text and html) and create two files that will be loaded into
> civicrm.  these two files can be tweaked as necessary for presentation
> reasons.
>
>    7. the user then goes though the standard civimail process for
> sending the emails.
>
>
> On 8/23/07, Shane Hill <shane@...> wrote:
>  
>> On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
>>    
>>> Hey Shane,
>>>
>>> I was just wondering if this has gotten released yet?
>>>      
>> no.  not  yet,   we are very busy getting ready to launch the SMTP
>> service.  we will get to it as soon as possible, lots of orgs want
>> this.  :)
>>
>> we will announce when it is ready.   :)
>>
>> -Shane
>>
>>    
> ____________________________________________________________
> You received this message as a subscriber on the list:
>      civicrm-dev@...
> To be removed from the list, send any message to:
>      civicrm-dev-unsubscribe@...
>
> For all list information and functions, see:
>      http://lists.civicrm.org/lists/info/civicrm-dev
>  

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[shanehill]

On 8/23/07, Matt Chapman <Matt@...> wrote:
> I think I could put a bounty of $800 or so on this project, if that
> would help...

it certainly does help.  I am investigating this further.

thx matt!

-S

>
> -m
>
> Shane Hill wrote:
> > Folks,
> >
> > I have included a description of our newsletter module below along
> > with the things that need to done before it can be released.
> >
> > if someone or some group in the community wants to step up and
> > generalize the module let me know.
> >
> > if anyone has a better idea than what is described below, please speak up.
> >
> > if I hear nothing, at some point, when time allows, we will generalize
> > and release the module.
> >
> > peace,
> >
> > -Shane
> >
> >
> > ===================
> > Tasks
> > ===================
> > # the data and presentation layers in the code are all mixed together
> > which makes it impossible to use templates at the moment. so those
> > layers need to be abstracted from one another
> >
> > # I would like to include a few templates that are known to be "safe"
> > in major email providers like google, yahoo and AOL.  The big
> > providers will strip and mess with the css and other html elements and
> > it can be a real pain to get things working well.  so providing some
> > basic vanilla templates that work well with the the big email
> > providers might be nice.
> >
> >
> > ======================
> > Module Overview
> > ======================
> >
> > The module allows for certain node types to be included in a mailing.
> > in our system currently, this is facilitated through two categories
> > (vocabularies), a "newsletter" node type and custom module code
> > called, you guessed it, "newsletter":
> >
> > newsletter issue (category)
> > newsletter section (category)
> > newsletter (node type)
> > newsletter (drupal module)
> >
> > to make a node available in a mailing, the node type must be added to
> > the categories.
> >
> > the process for creating a newsletter goes as follows:
> >
> >    1. Add a new term to the newsletter issue category (vocabulary)
> > that correlates to the mailing that will be sent (we have 12
> > predefined that are the monthly newsletters)
> >
> >    2. The user creates node content of the various types that have
> > been assigned to the above mentioned categories.
> >
> >    3. When the node is saved, the user chooses to assign it to a
> > particular newsletter issue and a particular newsletter section in
> > that issue.  This is done for all of the nodes that will be included
> > in a particular newsletter.
> >
> >    4. next, the user creates a newsletter node that would serve as the
> > actual newsletter.  when they do this they are given a list of choices
> > that are the terms in the category that have *not yet* been associated
> > with a mailing.  the user chooses the appropriate term (mailing) and
> > saves the node (newsletter).  when the node is accessed in the future
> > it aggregates all of the node content that was assigned to the
> > newsletter issue and displays the content (there are ways to define
> > article teasers, etc.)
> >
> >    5. next the user will use the custom newsletter module to create
> > HTML and text versions of the newsletter.  the html version is "safe"
> > for google, yahoo. and aol such that the css ans styling are not
> > stripped.   the flow for this is pretty simple.
> >
> >           * the user is presented with a list of newsletters in the system,
> >           * the user chooses a newsletter and a version(text or html)
> > (at some point there will be a choice for a template here)
> >           * the user clicks the generate button and they are presented
> > with a textarea that is filled with the newsletter content from start
> > to finish
> >
> >    6. The user needs to copy the content of the two newsletter
> > versions (text and html) and create two files that will be loaded into
> > civicrm.  these two files can be tweaked as necessary for presentation
> > reasons.
> >
> >    7. the user then goes though the standard civimail process for
> > sending the emails.
> >
> >
> > On 8/23/07, Shane Hill <shane@...> wrote:
> >
> >> On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> >>
> >>> Hey Shane,
> >>>
> >>> I was just wondering if this has gotten released yet?
> >>>
> >> no.  not  yet,   we are very busy getting ready to launch the SMTP
> >> service.  we will get to it as soon as possible, lots of orgs want
> >> this.  :)
> >>
> >> we will announce when it is ready.   :)
> >>
> >> -Shane
> >>
> >>
> > ____________________________________________________________
> > You received this message as a subscriber on the list:
> >      civicrm-dev@...
> > To be removed from the list, send any message to:
> >      civicrm-dev-unsubscribe@...
> >
> > For all list information and functions, see:
> >      http://lists.civicrm.org/lists/info/civicrm-dev
> >
>

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Benjamin Melançon-3]

Hello all,

Agaric Design Collective reporting in.  It's been a hard summer!
Thank you, Shane, for generous credit.  We always intended to start
using the module on our own site, and to try to generalize it for
release, but never got a chance to get back to our own work.

It's good to know the time spent testing and rejecting newsletter
modules a year ago was not misspent, but I'm nonetheless surprised
nothing was suggested.  I haven't seriously reviewed the options since
then.

We would contribute to the proposed pot an additional $500 for a very
well-generalized Drupal 5 solution, or with sponsorship (as has
started to be offered) could take on this project ourselves in the
near future– completion in November.  Regardless, we'd like to work
closely with whoever does work on this.

Shane and UAS' SMTP service for CiviMail makes this module that much
more attractive!

http://civicrm.org/node/237
http://www.uas.coop/civismtp-application

ben

Agaric Design Collective
Open Source Web Development and DJing
http://AgaricDesign.com/

~ In living, loving memory:  http://mlncn.com/john-melancon-life ~

On 8/23/07, Shane Hill <shane@...> wrote:

> Folks,
>
> I have included a description of our newsletter module below along
> with the things that need to done before it can be released.
>
> if someone or some group in the community wants to step up and
> generalize the module let me know.
>
> if anyone has a better idea than what is described below, please speak up.
>
> if I hear nothing, at some point, when time allows, we will generalize
> and release the module.
>
> peace,
>
> -Shane
>
>
> ===================
> Tasks
> ===================
> # the data and presentation layers in the code are all mixed together
> which makes it impossible to use templates at the moment. so those
> layers need to be abstracted from one another
>
> # I would like to include a few templates that are known to be "safe"
> in major email providers like google, yahoo and AOL.  The big
> providers will strip and mess with the css and other html elements and
> it can be a real pain to get things working well.  so providing some
> basic vanilla templates that work well with the the big email
> providers might be nice.
>
>
> ======================
> Module Overview
> ======================
>
> The module allows for certain node types to be included in a mailing.
> in our system currently, this is facilitated through two categories
> (vocabularies), a "newsletter" node type and custom module code
> called, you guessed it, "newsletter":
>
> newsletter issue (category)
> newsletter section (category)
> newsletter (node type)
> newsletter (drupal module)
>
> to make a node available in a mailing, the node type must be added to
> the categories.
>
> the process for creating a newsletter goes as follows:
>
>    1. Add a new term to the newsletter issue category (vocabulary)
> that correlates to the mailing that will be sent (we have 12
> predefined that are the monthly newsletters)
>
>    2. The user creates node content of the various types that have
> been assigned to the above mentioned categories.
>
>    3. When the node is saved, the user chooses to assign it to a
> particular newsletter issue and a particular newsletter section in
> that issue.  This is done for all of the nodes that will be included
> in a particular newsletter.
>
>    4. next, the user creates a newsletter node that would serve as the
> actual newsletter.  when they do this they are given a list of choices
> that are the terms in the category that have *not yet* been associated
> with a mailing.  the user chooses the appropriate term (mailing) and
> saves the node (newsletter).  when the node is accessed in the future
> it aggregates all of the node content that was assigned to the
> newsletter issue and displays the content (there are ways to define
> article teasers, etc.)
>
>    5. next the user will use the custom newsletter module to create
> HTML and text versions of the newsletter.  the html version is "safe"
> for google, yahoo. and aol such that the css ans styling are not
> stripped.   the flow for this is pretty simple.
>
>           * the user is presented with a list of newsletters in the system,
>           * the user chooses a newsletter and a version(text or html)
> (at some point there will be a choice for a template here)
>           * the user clicks the generate button and they are presented
> with a textarea that is filled with the newsletter content from start
> to finish
>
>    6. The user needs to copy the content of the two newsletter
> versions (text and html) and create two files that will be loaded into
> civicrm.  these two files can be tweaked as necessary for presentation
> reasons.
>
>    7. the user then goes though the standard civimail process for
> sending the emails.
>
>
> On 8/23/07, Shane Hill <shane@...> wrote:
> > On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> > > Hey Shane,
> > >
> > > I was just wondering if this has gotten released yet?
> >
> > no.  not  yet,   we are very busy getting ready to launch the SMTP
> > service.  we will get to it as soon as possible, lots of orgs want
> > this.  :)
> >
> > we will announce when it is ready.   :)
> >
> > -Shane
> >

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[shanehill]

heh,

well, the first rev is going to be released later today actually
thanks to matt chapman and ninjitsu hosting.
htp://www.ninjitsuhosting.com  :)

if there are some improvements that you want done, let us know, or
make it better yourself and submit a patch.  :)

more inna bit,

-Shane



On 9/4/07, Benjamin Melançon <pwgdarchive@...> wrote:

> Hello all,
>
> Agaric Design Collective reporting in.  It's been a hard summer!
> Thank you, Shane, for generous credit.  We always intended to start
> using the module on our own site, and to try to generalize it for
> release, but never got a chance to get back to our own work.
>
> It's good to know the time spent testing and rejecting newsletter
> modules a year ago was not misspent, but I'm nonetheless surprised
> nothing was suggested.  I haven't seriously reviewed the options since
> then.
>
> We would contribute to the proposed pot an additional $500 for a very
> well-generalized Drupal 5 solution, or with sponsorship (as has
> started to be offered) could take on this project ourselves in the
> near future– completion in November.  Regardless, we'd like to work
> closely with whoever does work on this.
>
> Shane and UAS' SMTP service for CiviMail makes this module that much
> more attractive!
>
> http://civicrm.org/node/237
> http://www.uas.coop/civismtp-application
>
> ben
>
> Agaric Design Collective
> Open Source Web Development and DJing
> http://AgaricDesign.com/
>
> ~ In living, loving memory:  http://mlncn.com/john-melancon-life ~
>
> On 8/23/07, Shane Hill <shane@...> wrote:
> > Folks,
> >
> > I have included a description of our newsletter module below along
> > with the things that need to done before it can be released.
> >
> > if someone or some group in the community wants to step up and
> > generalize the module let me know.
> >
> > if anyone has a better idea than what is described below, please speak up.
> >
> > if I hear nothing, at some point, when time allows, we will generalize
> > and release the module.
> >
> > peace,
> >
> > -Shane
> >
> >
> > ===================
> > Tasks
> > ===================
> > # the data and presentation layers in the code are all mixed together
> > which makes it impossible to use templates at the moment. so those
> > layers need to be abstracted from one another
> >
> > # I would like to include a few templates that are known to be "safe"
> > in major email providers like google, yahoo and AOL.  The big
> > providers will strip and mess with the css and other html elements and
> > it can be a real pain to get things working well.  so providing some
> > basic vanilla templates that work well with the the big email
> > providers might be nice.
> >
> >
> > ======================
> > Module Overview
> > ======================
> >
> > The module allows for certain node types to be included in a mailing.
> > in our system currently, this is facilitated through two categories
> > (vocabularies), a "newsletter" node type and custom module code
> > called, you guessed it, "newsletter":
> >
> > newsletter issue (category)
> > newsletter section (category)
> > newsletter (node type)
> > newsletter (drupal module)
> >
> > to make a node available in a mailing, the node type must be added to
> > the categories.
> >
> > the process for creating a newsletter goes as follows:
> >
> >    1. Add a new term to the newsletter issue category (vocabulary)
> > that correlates to the mailing that will be sent (we have 12
> > predefined that are the monthly newsletters)
> >
> >    2. The user creates node content of the various types that have
> > been assigned to the above mentioned categories.
> >
> >    3. When the node is saved, the user chooses to assign it to a
> > particular newsletter issue and a particular newsletter section in
> > that issue.  This is done for all of the nodes that will be included
> > in a particular newsletter.
> >
> >    4. next, the user creates a newsletter node that would serve as the
> > actual newsletter.  when they do this they are given a list of choices
> > that are the terms in the category that have *not yet* been associated
> > with a mailing.  the user chooses the appropriate term (mailing) and
> > saves the node (newsletter).  when the node is accessed in the future
> > it aggregates all of the node content that was assigned to the
> > newsletter issue and displays the content (there are ways to define
> > article teasers, etc.)
> >
> >    5. next the user will use the custom newsletter module to create
> > HTML and text versions of the newsletter.  the html version is "safe"
> > for google, yahoo. and aol such that the css ans styling are not
> > stripped.   the flow for this is pretty simple.
> >
> >           * the user is presented with a list of newsletters in the system,
> >           * the user chooses a newsletter and a version(text or html)
> > (at some point there will be a choice for a template here)
> >           * the user clicks the generate button and they are presented
> > with a textarea that is filled with the newsletter content from start
> > to finish
> >
> >    6. The user needs to copy the content of the two newsletter
> > versions (text and html) and create two files that will be loaded into
> > civicrm.  these two files can be tweaked as necessary for presentation
> > reasons.
> >
> >    7. the user then goes though the standard civimail process for
> > sending the emails.
> >
> >
> > On 8/23/07, Shane Hill <shane@...> wrote:
> > > On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> > > > Hey Shane,
> > > >
> > > > I was just wondering if this has gotten released yet?
> > >
> > > no.  not  yet,   we are very busy getting ready to launch the SMTP
> > > service.  we will get to it as soon as possible, lots of orgs want
> > > this.  :)
> > >
> > > we will announce when it is ready.   :)
> > >
> > > -Shane
> > >
>

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Emily Frazier]

Hi Shane,

Was just wondering if this was released? Couldn't find it on drupal.org....

Thanks!

On 9/4/07, Shane Hill <shane@...> wrote:

heh,

well, the first rev is going to be released later today actually
thanks to matt chapman and ninjitsu hosting.
htp://www.ninjitsuhosting.com  :)

if there are some improvements that you want done, let us know, or
make it better yourself and submit a patch.  :)

more inna bit,

-Shane



On 9/4/07, Benjamin Melançon <pwgdarchive@...> wrote:
> Hello all,
>
> Agaric Design Collective reporting in.  It's been a hard summer!
> Thank you, Shane, for generous credit.  We always intended to start
> using the module on our own site, and to try to generalize it for
> release, but never got a chance to get back to our own work.
>

> It's good to know the time spent testing and rejecting newsletter
> modules a year ago was not misspent, but I'm nonetheless surprised
> nothing was suggested.  I haven't seriously reviewed the options since
> then.
>
> We would contribute to the proposed pot an additional $500 for a very
> well-generalized Drupal 5 solution, or with sponsorship (as has
> started to be offered) could take on this project ourselves in the
> near future– completion in November.  Regardless, we'd like to work
> closely with whoever does work on this.
>
> Shane and UAS' SMTP service for CiviMail makes this module that much

> more attractive!
>
> http://civicrm.org/node/237
> http://www.uas.coop/civismtp-application
>
> ben

>
> Agaric Design Collective
> Open Source Web Development and DJing
> http://AgaricDesign.com/
>
> ~ In living, loving memory:   http://mlncn.com/john-melancon-life ~
>
> On 8/23/07, Shane Hill <shane@...> wrote:
> > Folks,
> >
> > I have included a description of our newsletter module below along
> > with the things that need to done before it can be released.
> >
> > if someone or some group in the community wants to step up and
> > generalize the module let me know.
> >
> > if anyone has a better idea than what is described below, please speak up.
> >
> > if I hear nothing, at some point, when time allows, we will generalize
> > and release the module.
> >
> > peace,
> >
> > -Shane
> >
> >
> > ===================
> > Tasks
> > ===================
> > # the data and presentation layers in the code are all mixed together
> > which makes it impossible to use templates at the moment. so those
> > layers need to be abstracted from one another
> >
> > # I would like to include a few templates that are known to be "safe"
> > in major email providers like google, yahoo and AOL.  The big
> > providers will strip and mess with the css and other html elements and
> > it can be a real pain to get things working well.  so providing some
> > basic vanilla templates that work well with the the big email
> > providers might be nice.
> >
> >
> > ======================
> > Module Overview
> > ======================
> >
> > The module allows for certain node types to be included in a mailing.
> > in our system currently, this is facilitated through two categories
> > (vocabularies), a "newsletter" node type and custom module code
> > called, you guessed it, "newsletter":
> >
> > newsletter issue (category)
> > newsletter section (category)
> > newsletter (node type)
> > newsletter (drupal module)
> >
> > to make a node available in a mailing, the node type must be added to
> > the categories.
> >
> > the process for creating a newsletter goes as follows:
> >

> >    1. Add a new term to the newsletter issue category (vocabulary)

> > that correlates to the mailing that will be sent (we have 12
> > predefined that are the monthly newsletters)
> >
> >    2. The user creates node content of the various types that have
> > been assigned to the above mentioned categories.
> >
> >    3. When the node is saved, the user chooses to assign it to a
> > particular newsletter issue and a particular newsletter section in
> > that issue.  This is done for all of the nodes that will be included
> > in a particular newsletter.
> >
> >    4. next, the user creates a newsletter node that would serve as the
> > actual newsletter.  when they do this they are given a list of choices
> > that are the terms in the category that have *not yet* been associated
> > with a mailing.  the user chooses the appropriate term (mailing) and
> > saves the node (newsletter).  when the node is accessed in the future
> > it aggregates all of the node content that was assigned to the
> > newsletter issue and displays the content (there are ways to define
> > article teasers, etc.)
> >
> >    5. next the user will use the custom newsletter module to create
> > HTML and text versions of the newsletter.  the html version is "safe"
> > for google, yahoo. and aol such that the css ans styling are not
> > stripped.   the flow for this is pretty simple.
> >
> >           * the user is presented with a list of newsletters in the system,
> >           * the user chooses a newsletter and a version(text or html)
> > (at some point there will be a choice for a template here)
> >           * the user clicks the generate button and they are presented
> > with a textarea that is filled with the newsletter content from start
> > to finish
> >
> >    6. The user needs to copy the content of the two newsletter
> > versions (text and html) and create two files that will be loaded into
> > civicrm.  these two files can be tweaked as necessary for presentation
> > reasons.
> >
> >    7. the user then goes though the standard civimail process for
> > sending the emails.
> >
> >
> > On 8/23/07, Shane Hill <shane@...> wrote:
> > > On 8/23/07, Emily E Frazier <emily.e.frazier@...> wrote:
> > > > Hey Shane,
> > > >
> > > > I was just wondering if this has gotten released yet?
> > >
> > > no.  not  yet,   we are very busy getting ready to launch the SMTP
> > > service.  we will get to it as soon as possible, lots of orgs want
> > > this.  :)
> > >
> > > we will announce when it is ready.   :)
> > >
> > > -Shane
> > >
>

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[rastarr]

There doesn't seem to be much proress on this one despite there being a real need for an alternate newsletter component in the Drupal community with it's functionality.

I was wondering what stage this module was at and whether you've considered implementing CiviMail's 'mail send throttling' feature as well ?

Cheers
Martin

Emily Frazier wrote:

Hi Shane,

Was just wondering if this was released? Couldn't find it on drupal.org....

Thanks!

On 9/4/07, Shane Hill <[e-mail]> wrote:
>
> heh,
>
> well, the first rev is going to be released later today actually
> thanks to matt chapman and ninjitsu hosting.
> htp://www.ninjitsuhosting.com  :)
>
> if there are some improvements that you want done, let us know, or
> make it better yourself and submit a patch.  :)
>
> more inna bit,
>
> -Shane
>
>
>
> On 9/4/07, Benjamin Melançon <[e-mail]> wrote:
> > Hello all,
> >
> > Agaric Design Collective reporting in.  It's been a hard summer!
> > Thank you, Shane, for generous credit.  We always intended to start
> > using the module on our own site, and to try to generalize it for
> > release, but never got a chance to get back to our own work.
> >
> > It's good to know the time spent testing and rejecting newsletter
> > modules a year ago was not misspent, but I'm nonetheless surprised
> > nothing was suggested.  I haven't seriously reviewed the options since
> > then.
> >
> > We would contribute to the proposed pot an additional $500 for a very
> > well-generalized Drupal 5 solution, or with sponsorship (as has
> > started to be offered) could take on this project ourselves in the
> > near future– completion in November.  Regardless, we'd like to work
> > closely with whoever does work on this.
> >
> > Shane and UAS' SMTP service for CiviMail makes this module that much
> > more attractive!
> >
> > http://civicrm.org/node/237
> > http://www.uas.coop/civismtp-application
> >
> > ben
> >
> > Agaric Design Collective
> > Open Source Web Development and DJing
> > http://AgaricDesign.com/
> >
> > ~ In living, loving memory:  http://mlncn.com/john-melancon-life ~
> >
> > On 8/23/07, Shane Hill <[e-mail]> wrote:
> > > Folks,
> > >
> > > I have included a description of our newsletter module below along
> > > with the things that need to done before it can be released.
> > >
> > > if someone or some group in the community wants to step up and
> > > generalize the module let me know.
> > >
> > > if anyone has a better idea than what is described below, please speak
> up.
> > >
> > > if I hear nothing, at some point, when time allows, we will generalize
> > > and release the module.
> > >
> > > peace,
> > >
> > > -Shane
> > >
> > >
> > > ===================
> > > Tasks
> > > ===================
> > > # the data and presentation layers in the code are all mixed together
> > > which makes it impossible to use templates at the moment. so those
> > > layers need to be abstracted from one another
> > >
> > > # I would like to include a few templates that are known to be "safe"
> > > in major email providers like google, yahoo and AOL.  The big
> > > providers will strip and mess with the css and other html elements and
> > > it can be a real pain to get things working well.  so providing some
> > > basic vanilla templates that work well with the the big email
> > > providers might be nice.
> > >
> > >
> > > ======================
> > > Module Overview
> > > ======================
> > >
> > > The module allows for certain node types to be included in a mailing.
> > > in our system currently, this is facilitated through two categories
> > > (vocabularies), a "newsletter" node type and custom module code
> > > called, you guessed it, "newsletter":
> > >
> > > newsletter issue (category)
> > > newsletter section (category)
> > > newsletter (node type)
> > > newsletter (drupal module)
> > >
> > > to make a node available in a mailing, the node type must be added to
> > > the categories.
> > >
> > > the process for creating a newsletter goes as follows:
> > >
> > >    1. Add a new term to the newsletter issue category (vocabulary)
> > > that correlates to the mailing that will be sent (we have 12
> > > predefined that are the monthly newsletters)
> > >
> > >    2. The user creates node content of the various types that have
> > > been assigned to the above mentioned categories.
> > >
> > >    3. When the node is saved, the user chooses to assign it to a
> > > particular newsletter issue and a particular newsletter section in
> > > that issue.  This is done for all of the nodes that will be included
> > > in a particular newsletter.
> > >
> > >    4. next, the user creates a newsletter node that would serve as the
> > > actual newsletter.  when they do this they are given a list of choices
> > > that are the terms in the category that have *not yet* been associated
> > > with a mailing.  the user chooses the appropriate term (mailing) and
> > > saves the node (newsletter).  when the node is accessed in the future
> > > it aggregates all of the node content that was assigned to the
> > > newsletter issue and displays the content (there are ways to define
> > > article teasers, etc.)
> > >
> > >    5. next the user will use the custom newsletter module to create
> > > HTML and text versions of the newsletter.  the html version is "safe"
> > > for google, yahoo. and aol such that the css ans styling are not
> > > stripped.   the flow for this is pretty simple.
> > >
> > >           * the user is presented with a list of newsletters in the
> system,
> > >           * the user chooses a newsletter and a version(text or html)
> > > (at some point there will be a choice for a template here)
> > >           * the user clicks the generate button and they are presented
> > > with a textarea that is filled with the newsletter content from start
> > > to finish
> > >
> > >    6. The user needs to copy the content of the two newsletter
> > > versions (text and html) and create two files that will be loaded into
> > > civicrm.  these two files can be tweaked as necessary for presentation
> > > reasons.
> > >
> > >    7. the user then goes though the standard civimail process for
> > > sending the emails.
> > >
> > >
> > > On 8/23/07, Shane Hill <[e-mail]> wrote:
> > > > On 8/23/07, Emily E Frazier <[e-mail]> wrote:
> > > > > Hey Shane,
> > > > >
> > > > > I was just wondering if this has gotten released yet?
> > > >
> > > > no.  not  yet,   we are very busy getting ready to launch the SMTP
> > > > service.  we will get to it as soon as possible, lots of orgs want
> > > > this.  :)
> > > >
> > > > we will announce when it is ready.   :)
> > > >
> > > > -Shane
> > > >
> >
>

____________________________________________________________
You received this message as a subscriber on the list:
     [e-mail]
To be removed from the list, send any message to:
     [e-mail]

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev

[Emily Frazier]

Shane,

I know it's been about 6 months since we last spoke, but I wanted to give you and the dev-list and update since this thread originated on the mailing list. My org finally upgraded to D5 and I have successfully configured your module and just started using it. It is AWESOME. I love that we can edit the template files and it makes sending newsletters soooooo slick.

I think the trouble area before was understanding how Smarty integrates with it all and creating a directory here and there. I guess I got a little smarter in the last 6 months (pun intended). In any case, it is a robust module. I think it would be fabulous to release it officially on drupal.

I was also thinking about how it could be even more closely integrated with CiviCRM. This would be a great thing for a later release, so that CiviMail could essentially do the "newsletter generation" piece as part of its functionality instead of generating in Drupal, pasting, and uploading to CiviMail. Now that would just be freakin amazing. If there is other interest in that, I would start up a thread on the forum.

Again, thanks so much for your hard work on this. It's really good stuff. Keep me updated as things go forward, and let me know what I can do to help.
Emily

------P.S.-------
For anyone who needs a refresher or didn't follow this post originally, here is how it started:

Hi folks,

We are using a newsletter generating module that lets one cruise around their drupal nodes and select them for inclusion in newsletter content.  then you create some intro text and click a button and then you get a text and html newsletter ready for sending out to your constituents via civimail.

the module is pretty nifty.

Agaric consulting created it last year for us.  thanks Agaric. :)

http://www.agaricdesign.com/

what I am wondering about is if the community thinks it would be worth the time to generalize this module and release it.  is anyone interested in this?  is there a module that exists that maybe does the same thing?  i have not looked much because we are pretty happy with our module.   what do people use for generating html newsletters for civimail usually?


-------------------------------------------

>http://uascoop.googlecode.com/svn/trunk/drupal/modules/ninjitsu_newsletter

>I'd be curious to hear how you're using it, and any modifications you make.
>
>All the Best,
>
>Matt

Emily E Frazier wrote:
> Hi Shane,
>
> Was just wondering if this was released? Couldn't find it on
> drupal.org....
>
> Thanks!
>

> On 9/4/07, *Shane Hill* < shane@... <mailto:shane@...>> wrote:
>
>     heh,
>
>     well, the first rev is going to be released later today actually
>     thanks to matt chapman and ninjitsu hosting.
>     htp://www.ninjitsuhosting.com  :)
>
>     if there are some improvements that you want done, let us know, or
>     make it better yourself and submit a patch.  :)
>
>     more inna bit,
>
>     -Shane
>
>
>
>     On 9/4/07, Benjamin Melançon <pwgdarchive@...

- Show quoted text -

>     <mailto:pwgdarchive@...>> wrote:
>     > Hello all,
>     >
>     > Agaric Design Collective reporting in.  It's been a hard summer!
>     > Thank you, Shane, for generous credit.  We always intended to start
>     > using the module on our own site, and to try to generalize it for
>     > release, but never got a chance to get back to our own work.
>     >
>     > It's good to know the time spent testing and rejecting newsletter
>     > modules a year ago was not misspent, but I'm nonetheless surprised
>     > nothing was suggested.  I haven't seriously reviewed the options
>     since
>     > then.
>     >
>     > We would contribute to the proposed pot an additional $500 for a
>     very
>     > well-generalized Drupal 5 solution, or with sponsorship (as has
>     > started to be offered) could take on this project ourselves in the
>     > near future– completion in November.  Regardless, we'd like to work
>     > closely with whoever does work on this.
>     >
>     > Shane and UAS' SMTP service for CiviMail makes this module that much
>     > more attractive!
>     >
>     > http://civicrm.org/node/237
>     > http://www.uas.coop/civismtp-application
>     >
>     > ben
>     >
>     > Agaric Design Collective
>     > Open Source Web Development and DJing
>     > http://AgaricDesign.com/
>     >
>     > ~ In living, loving memory:   http://mlncn.com/john-melancon-life ~
>     >

>     > On 8/23/07, Shane Hill <shane@... <mailto:shane@...>>

- Show quoted text -

>     wrote:
>     > > Folks,
>     > >
>     > > I have included a description of our newsletter module below
>     along
>     > > with the things that need to done before it can be released.
>     > >
>     > > if someone or some group in the community wants to step up and
>     > > generalize the module let me know.
>     > >
>     > > if anyone has a better idea than what is described below,
>     please speak up.
>     > >
>     > > if I hear nothing, at some point, when time allows, we will
>     generalize
>     > > and release the module.
>     > >
>     > > peace,
>     > >
>     > > -Shane
>     > >
>     > >
>     > > ===================
>     > > Tasks
>     > > ===================
>     > > # the data and presentation layers in the code are all mixed
>     together
>     > > which makes it impossible to use templates at the moment. so those
>     > > layers need to be abstracted from one another
>     > >
>     > > # I would like to include a few templates that are known to be
>     "safe"
>     > > in major email providers like google, yahoo and AOL.  The big
>     > > providers will strip and mess with the css and other html
>     elements and
>     > > it can be a real pain to get things working well.  so
>     providing some
>     > > basic vanilla templates that work well with the the big email
>     > > providers might be nice.
>     > >
>     > >
>     > > ======================
>     > > Module Overview
>     > > ======================
>     > >
>     > > The module allows for certain node types to be included in a
>     mailing.
>     > > in our system currently, this is facilitated through two
>     categories
>     > > (vocabularies), a "newsletter" node type and custom module code
>     > > called, you guessed it, "newsletter":
>     > >
>     > > newsletter issue (category)
>     > > newsletter section (category)
>     > > newsletter (node type)
>     > > newsletter (drupal module)
>     > >
>     > > to make a node available in a mailing, the node type must be
>     added to
>     > > the categories.
>     > >
>     > > the process for creating a newsletter goes as follows:
>     > >
>     > >    1. Add a new term to the newsletter issue category (vocabulary)
>     > > that correlates to the mailing that will be sent (we have 12
>     > > predefined that are the monthly newsletters)
>     > >
>     > >    2. The user creates node content of the various types that have
>     > > been assigned to the above mentioned categories.
>     > >
>     > >    3. When the node is saved, the user chooses to assign it to a
>     > > particular newsletter issue and a particular newsletter section in
>     > > that issue.  This is done for all of the nodes that will be
>     included
>     > > in a particular newsletter.
>     > >
>     > >    4. next, the user creates a newsletter node that would
>     serve as the
>     > > actual newsletter.  when they do this they are given a list of
>     choices
>     > > that are the terms in the category that have *not yet* been
>     associated
>     > > with a mailing.  the user chooses the appropriate term
>     (mailing) and
>     > > saves the node (newsletter).  when the node is accessed in the
>     future
>     > > it aggregates all of the node content that was assigned to the
>     > > newsletter issue and displays the content (there are ways to
>     define
>     > > article teasers, etc.)
>     > >
>     > >    5. next the user will use the custom newsletter module to
>     create
>     > > HTML and text versions of the newsletter.  the html version is
>     "safe"
>     > > for google, yahoo. and aol such that the css ans styling are not
>     > > stripped.   the flow for this is pretty simple.
>     > >
>     > >           * the user is presented with a list of newsletters
>     in the system,
>     > >           * the user chooses a newsletter and a version(text
>     or html)
>     > > (at some point there will be a choice for a template here)
>     > >           * the user clicks the generate button and they are
>     presented
>     > > with a textarea that is filled with the newsletter content
>     from start
>     > > to finish
>     > >
>     > >    6. The user needs to copy the content of the two newsletter
>     > > versions (text and html) and create two files that will be
>     loaded into
>     > > civicrm.  these two files can be tweaked as necessary for
>     presentation
>     > > reasons.
>     > >
>     > >    7. the user then goes though the standard civimail process for
>     > > sending the emails.
>     > >
>     > >
>     > > On 8/23/07, Shane Hill <shane@...

>     <mailto:shane@...>> wrote:
>     > > > On 8/23/07, Emily E Frazier < emily.e.frazier@...

- Hide quoted text -

>     <mailto:emily.e.frazier@...>> wrote:
>     > > > > Hey Shane,
>     > > > >
>     > > > > I was just wondering if this has gotten released yet?
>     > > >
>     > > > no.  not  yet,   we are very busy getting ready to launch
>     the SMTP
>     > > > service.  we will get to it as soon as possible, lots of
>     orgs want
>     > > > this.  :)
>     > > >
>     > > > we will announce when it is ready.   :)
>     > > >
>     > > > -Shane
>     > > >
>     >

____________________________________________________________
You received this message as a subscriber on the list:
     civicrm-dev@...
To be removed from the list, send any message to:
     civicrm-dev-unsubscribe@...

For all list information and functions, see:
     http://lists.civicrm.org/lists/info/civicrm-dev