>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #500218. --> Reported by: [rsvelko](https://www.drupal.org/user/337401) >>> <p>Hi, everyone - here is what I and sun have come up with recently:</p> <p>Basically we (we - both rsvelko and sun and WE - the drupal community ) would pretty much like it if there was only one Project with a couple of submodules in it that solve "the Glossary" problem ...</p> <p>Instead we have 3 modules - This module (glossify - node based) is similar to Glossary (taxonomy term-based, usage ~1400 as of May 2009) and G2 Glossary ( node-based, usage ~20) modules.</p> <p>So here I paste our emails with sun to serve for a start of the planning:</p> <p><b>sun:</b></p> <p>"<br> Hi Vladimir,</p> <p> thanks for your response.</p> <p> I have no roadmap or clear vision of what I want to do. All I know is that I need a feature-wise complete replacement for Glossary module. I think the architectural design is trivial:</p> <p> - Nodes define glossary terms (title) and description (body).</p> <p> - A CCK textfield may be used to define synonyms. (optional)</p> <p> - A CCK nodereference may be used to define related terms. (optional)</p> <p> - The module defines a separate build mode to render the node's body in a suitable format/markup for acronym/abbr tags or tooltips.</p> <p> - A (customizable) default view is provided to output the glossary.</p> <p> - Support for hovertip, tooltip, and other paranoia.</p> <p> - Taxonomy may be used to categorize glossary term nodes. (built-in core feature ;)</p> <p> Future:</p> <p> - Check whether glossify'ing can also work on the client-side, using a client-side caching approach.</p> <p> Hrm. The more I think about it, the more I think I want to either take over the project or start a new one - because I'm not sure how much of the current module can be kept. Especially, since we would also have to rule out things like <a href="http://drupal.org/node/496646">http://drupal.org/node/496646</a>, and more importantly <a href="http://drupal.org/node/363367">http://drupal.org/node/363367</a> ;)</p> <p> Thoughts?</p> <p> Thanks,<br> Daniel<br> "</p> <p><b>rsvelko: </b></p> <p>""2. I suggest we happily co-maintain this module or start a new one.</p> <p>3. Most importantly I need you to tell me why do you want to completely rewrite the glossary module? It is the one that has about 1000 usage .... Can we not collaborate with its maintainers ?</p> <p>We definitely need to start anew but there is so much we can use from the glossary/g2/glossify triplet ...</p> <p>These 3 G-modules ( glossify/glossary/g2 ) that are present all serve a different use case while basically doing the same thing - so there is so much place for code reuse ...</p> <p>We need to carefully split features into non-intersecting areas and do them in submodules ( thus we can solve the whole problem if all are enabled and suit the specific use-cases if only some sub-parts are enabled ... ):<br> - just for example :<br> - tag based<br> - node based<br> - node-body parser and terms-links (hovertips/blabla) replacer (best if it is a input filter)<br> - term page<br> - views of terms - alphabetical ...<br> - admin UI<br> ......</p> <p>X-posting these letters into a new issue in glossify.</p> <p>Still not sure if we need a new project or we can reuse some of the old ones ...</p> <p>"</p>