Decoupled architecture: Difference between revisions
Created page with "thumb|Authors|left|link=thumb|Audience|right|link= A decoupled architecture is one that separates the publishing from the c..." |
m removed Category:Architecture; added Category:System Architecture using HotCat |
||
| Line 4: | Line 4: | ||
== Example == | == Example == | ||
One very interesting example is with the MediaWiki system. The user interface is very difficult to "skin" or customize in a way that is desirable and blends with your company's brand. Also, many of the features of the system that are great for authors do not mix well with the delivery of the content in another system. However, since MediaWiki has a strong API, it's easy to grab and reuse content from a "backend" wiki system and present it in a totally un-related front-end website. For example, we use the [[Wiki report]] page as a "backend" authoring environment for delivery to the "frontend" company website: https://equality-tech.com/content/wiki-report-now-available | One very interesting example is with the MediaWiki system. The user interface is very difficult to "skin" or customize in a way that is desirable and blends with your company's brand. Also, many of the features of the system that are great for authors do not mix well with the delivery of the content in another system. However, since MediaWiki has a strong API, it's easy to grab and reuse content from a "backend" wiki system and present it in a totally un-related front-end website. For example, we use the [[Wiki report]] page as a "backend" authoring environment for delivery to the "frontend" company website: https://equality-tech.com/content/wiki-report-now-available | ||
[[Category:Architecture]] | [[Category:System Architecture]] | ||
