Redvant: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 33: | Line 33: | ||
Various services are integrated by DCP in the process of domain content definition and maintenance. De novo domains and the unification of CMSes mentioned in the next ¶. In general, where possible integration means operation of the received CMS as is at the code level via its LDAP integration and running under MCP. At the detail level this is mediated by domain for codegen of models, beam for abstraction of the rdbmses, and compdata. | Various services are integrated by DCP in the process of domain content definition and maintenance. De novo domains and the unification of CMSes mentioned in the next ¶. In general, where possible integration means operation of the received CMS as is at the code level via its LDAP integration and running under MCP. At the detail level this is mediated by domain for codegen of models, beam for abstraction of the rdbmses, and compdata. | ||
<br><br> | <br><br> | ||
Acknowledging <html><a href=https://wiki.haskell.org/Web/Content_Management>clckwrks, et al.</a></html> as suggestions for hs CMS, have taken a different route based on generalization and pass thru of the function of PHP and python CMSes such as | Acknowledging <html><a href=https://wiki.haskell.org/Web/Content_Management>clckwrks, et al.</a></html> as suggestions for hs CMS, have taken a different route based on generalization and pass thru of the function of PHP and python CMSes such as WP, mediawiki, Cliu/D7, and django-cms. The design intent is for recovery of the function of contained CMSes as an abstracted and separately maintained bulk with their original and subsequent live code absorbed as is. | ||
</blockquote> | </blockquote> | ||
</blockquote> | </blockquote> | ||
