We are creating a module for generating HTML email newsletters. We examined several other modules (SimpleNews, MailChimp, among others), but due to various requirements it will be easier and better for us to create our own solution.
As a new Drupal developer, I am a little worried about handling this non-Drupal method. My plan, however, is to set up a dictionary with newsletters as a term and actual newsletters as sub-terms, for example:
Newsletters (term)
- Newsletter A (sub-term)
- Newsletter B (sub-term)
This gives an additional advantage, allowing you to organize the publication of articles (among other things, on the site.)
The question, however, is how to handle the various questions of the newsletter. I could go even deeper in the dictionary, for example:
Newsletters (term)
- Newsletter A (sub-term)
- Issue - 2010-03-01
- Issue - 2010-03-02
- Newsletter B (sub-term)
- Issue - 2010-03-01
- Issue - 2010-03-08
But I wonder if this adds too much complexity. As soon as I have such a taxonomy system, when the user sets out to add new newsletters, he will also create a node (content type: newsletter), and when he / she sets out to add new problems, he will also create a node (content type: problem.) Then these will be the landing pages for this content.
So the question is, is there a better way to handle this structure? Is this a Drupal-like solution?
source
share