Drupal integration: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(New page: Notes about creating a publishing platform with Scribus and Drupal == Requirenments * running Drupal6 * external connection to Mysql database or a shell == Drupal backend Articles are pr...)
 
No edit summary
Line 1: Line 1:
Notes about creating a publishing platform with Scribus and Drupal
Notes about creating a publishing platform with Scribus and Drupal (DRAFT)
 
 
== Requirenments ==


== Requirenments
* running Drupal6
* running Drupal6
* external connection to Mysql database or a shell
* external connection to Mysql database or a shell


== Drupal backend
 
== Drupal backend ==
 
Articles are prepared to publish within the complete workflow system. The workflow system is build with help of: CCK, Views2, Workflow and Diff modules.
Articles are prepared to publish within the complete workflow system. The workflow system is build with help of: CCK, Views2, Workflow and Diff modules.


Done
=== Done ===
* workflow (from Draft state to Published state), revisioning included
* workflow (from Draft state to Published state), revisioning included
* input format -- html, with help of BueEditor and custom button set
* input format -- html, with help of BueEditor and custom button set
* a special dashboard for listing articles in different states (Views2), includes a tab with articles prepared for publishing
* a special dashboard for listing articles in different states (Views2), includes a tab with articles prepared for publishing


ToDo
=== ToDo ===
* Drupal module that allows you to create article presets (i.e. main article, editorial etc.) and informs if your article pass the layout (char counter)
* Drupal module that allows you to create article presets (i.e. main article, editorial etc.) and informs if your article pass the layout (char counter)


== Scribus backend
== Scribus backend ==
Articles are fetched by a simple python script and converted to html readable by Scribus.
Articles are fetched by a simple python script and converted to html readable by Scribus.


ToDo
=== ToDo ===
* script works outside Scribus. As a proof of concept we can create a similar script which imports articles directly to Scribus, unfortunately, text formatting is lost in this case...
* script works outside Scribus. As a proof of concept we can create a similar script which imports articles directly to Scribus, unfortunately, text formatting is lost in this case...
== Possible extensions ==
* use of markdown syntax

Revision as of 12:05, 20 November 2009

Notes about creating a publishing platform with Scribus and Drupal (DRAFT)


Requirenments

  • running Drupal6
  • external connection to Mysql database or a shell


Drupal backend

Articles are prepared to publish within the complete workflow system. The workflow system is build with help of: CCK, Views2, Workflow and Diff modules.

Done

  • workflow (from Draft state to Published state), revisioning included
  • input format -- html, with help of BueEditor and custom button set
  • a special dashboard for listing articles in different states (Views2), includes a tab with articles prepared for publishing

ToDo

  • Drupal module that allows you to create article presets (i.e. main article, editorial etc.) and informs if your article pass the layout (char counter)

Scribus backend

Articles are fetched by a simple python script and converted to html readable by Scribus.

ToDo

  • script works outside Scribus. As a proof of concept we can create a similar script which imports articles directly to Scribus, unfortunately, text formatting is lost in this case...

Possible extensions

  • use of markdown syntax