Appendix C. Glossary of Terms


Add Story

A module used to add news articles to PostNuke. It provides the ability to publish without prior authorization.



Application Programming Interface (API)

A set of functions used to abstract the lower level operations from the upper. With regard to PostNuke, the functions and conventions used by modules to consistently access the core functionality of PostNuke. Modules written with the pnAPI will work with future versions of PostNuke without needing to be upgraded themselves.



Article

Usually the news stories displayed on the front page of a PostNuke site. Articles also refer to any publication content in general.



Author

A person responsible for the writing of content. In PostNuke, a content author can be a site user who submits new content or someone who is responsible for the approval and publishing of submitted content.



Back end

The feature of PostNuke that allows you to feed your news to other sites for display.



Banners

A form of web page advertising. Banners are usually wide rectangular images placed at the top or bottom of a page.



Block

A small, self-contained interface that performs a specific function, such as the display of PostNuke module content. Some blocks are very simple and can exist without a parent module, but most are tied specifically to the module application with which they were made to work.



Blog

A shortening of weblog. A blog is an online journal in which dated user entries are logged. Blog content is usually written informally and sometimes formed through the efforts of multiple posters.



Category

In PostNuke, a grouping mechanism for content. Categories that are defined by their labels and content can then be assigned to a given category. PostNuke 0.8 will include a global category system hooked into all modules.



Client

The user's browser that receives and displays web page content.



Content Management System (CMS)

The software designed to organize and manage content, usually in environments with multiple authors and/or managers of the data. The term is now primarily associated with website content.



End user

The person using a product. Visitors to PostNuke sites are end users, and, in some cases, they might also be content authors.



Feed

The imported content from other websites, usually using a format like RSS.



Fork

A split in the development of an open source development project, such as PostNuke forking off from PHP-Nuke. Some forks remain very similar to their parent applications, and others quickly become unique.



General Public License (GPL)

An open source license. The GNU General Public License (http://www.fsf.org/licenses/gpl.html) was created by the GNU Project in 1988 to allow programmers the ability to distribute their work for use, modification, and redistribution while ensuring the work will continue to be freely available after release.



Hack

A change to original PostNuke source code to alter the functionality of the application or the display of its content. Hacks usually add additional features not available in the stock release.



Hook

A feature of PostNuke that is available to all modules compatible with pnHooks. Common hooks include comments, ratings, and Autolinks.



Intranet

An internal network used within a company or organization that is usually restricted from external access. The term also refers to the main internal website.



Layout

The arrangement of content on a web page designed to provide an effective interface for accessing the content.



Module

A component of PostNuke. PostNuke is essentially made up of a group of modules. Each module performs a set of tasks, and all have ways of interfacing with other PostNuke core modules. Modules display their content through blocks.



News

The article stories displayed on a website, usually on the front page.



Open source

The software that is public domain or copyrighted under an open source license, such as the GPL. The software's code is usually freely available and can be modified, usually with the requirement that changed versions are also released as open source.



PHP-Nuke

The CMS from which PostNuke originated. PostNuke forked from PHP-Nuke in the Spring of 2001. PostNuke's original code was identical to PHP-Nuke at the time, but has since undergone major rewrites.



pnRender

A module that wraps the standard Smarty functions so that they are accessible to other PostNuke modules. pnRender is a subclass of the Smarty Engine and replaces the older pnHTML functionality.



Portal

A website that provides extensive information and content related to a specific topic or interest. Traditionally, portals are very large sites and not personal or focused on a specific organization or group. Portals also commonly provide personalization options to their users.



Really Simple Syndication (RSS)

A syndication format for web content that is derived from XML. Using RSS websites can import content from other sites.



Section

A PostNuke module designed to manage relatively static articles that do not appear as news.



Smarty Template Engine

A template and presentation framework for PHP that provides the tools needed to separate application logic from presentation code. It makes it easy to modularize the form and function components in your PHP application. XTE uses Smarty.



Story

A news article displayed on a website, usually on the front page.



Submit News

A module used to submit potential news articles to PostNuke. Stories submitted through this module go into a queue where they must be approved before they go live. The approval system is part of the Add Story module.



Template

A file that describes the way content should be displayed. Templates are usually simple XHTML files that use variable calls to place integrated dynamic content.



Theme

The visual appearance, layout, and interface of PostNuke page content. Themes can contain both PHP and XHTML code, but are always concerned with the layout of content and not what the content itself might be. Xanthia themes include separate XHTML template files for different blocks, modules, and pages. Themes are also sometimes known as "skins."



Topic

The identifying label attached to a news story. Topics usually have graphics icons that are displayed with an article to make it clear what type of article it is, or to what subject the story will relate.



Wiki

A CMS system of web pages that are written with "Wiki Words" instead of HTML. The Wiki tags are more simplified than HTML, but they also have less formatting options. Wiki pages can usually be edited by anyone reading the page. Wiki is the Hawaiian word for quick.



WYSIWYG

An acronym for What You See Is What You Get. The term usually applies to an editor with a graphical interface that makes writing easier. For example, a button within a programming editor would write out predefined code with each use. WYSIWYG interfaces also often hide the codes they generate to maintain a simplified interface.



Xanthia Templating Environment (XTE)

A theme engine built using pnRender Smarty functions that manages the template interface to PostNuke. Xanthia themes contain template files for each independently designed component and store display settings in the PostNuke database.



XHTML

The acronym stands for Extensible Hypertext Markup Language, but it is almost never referred to by its full name. When the HTML 4.0 specification was combined with the more-current XML 1.0 specification, the result was XHTML. XHTML is essentially "HTML version 5." XHTML is generally backward compatible with existing HTML standards, and all website development should use as much of the XHTML specifications as possible.



Zone

A specifically defined layout area. A Xanthia theme zone can be applied to modules or blocks to allow the association of themes. Block zones describe areas where blocks can be assigned.





    PostNuke Content Management
    PostNuke Content Management
    ISBN: 0672326868
    EAN: 2147483647
    Year: 2003
    Pages: 207
    Authors: Kevin Hatch

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net