Flexible Content Management System


The Future: Where is PN going?

Contributed by on Feb 11, 2003 - 02:16 AM

<font face="Verdana" size=2><font size="3" color="#990000">Introduction</font>

PN has grown both in core logic and in modules/blocks available, the lines
between the core logic and the modules and/or extensions have blurred at times,
forcing 3rd party developers to impose upon the core, creating incompatibilities,
delaying upgrades, and slowing response times from the system (pnCore).</font>

<font face="Verdana" size=2>So we'll get to the point in the
beginning, what can you look forward to in the next release of PN? A modularized
core, plug and play architecture, short URL's, admin redesign, a templating
engine (get
more info here
), better security, caching, and a visual editor. Some
may be asking, "How is this going to be accomplished?" and "Who is going
to do it?" Read on and you'll discover who has volunteered their time, how
it is organized and how you can contribute.</font>

<font face="Verdana" size=2>Modularizing the core is key to separating
core logic and presentation layers. And the work on modularizing pnAPI, and
key core components is well under way and means you will see this change
in the next release 0.8 (code named: adam_baum). As a result of this modularization
future PN releases will include the following packages, (i.e. Core, Modules,
Languages, Docs, & Themes) and are reflected in the current CVS as main
categories which in turn hold the components belonging to it, (i.e. Modules:
Content, Legacy, Miscellaneous, ResourcePack and Utility).</font>

<font face="Verdana" size=2>Some of you may be asking yourself, "How
do these changes help me as a module dev, webmaster, or user?" First for
module devs, the categorization of data provides you with the ability to
group your module in a logical way within the current module structure already
available in PN. It will also provide a webmaster with the ability to better
use and manage their site, targeting their site to specific use or tastes.
For example, you can create and tailor your installations based on your personal
tastes, needs, or target audiences, i.e., site focusing on community, content,
e-commerce, or education. For users this won't make much difference to you
other than the site you are using will provide you with a richer user experience.</font>

<font face="Verdana" size=2>Also, webmaster/admin's can look
forward to new and enhanced core functionality. PN will now be able to categorize
modules, blocks, and content. Furthermore it will be able to resolve module
dependencies; for example, if you want to install the "News" module it would
require the installation of dependent modules that provide additional functionality.
The new installer will detect those dependencies and guide you in the set-up
process of customizing and installing PN. For example, a request for the "News" module,
requires the following additional modules: Submit_News, Topics and NS-AddStory,
so the installer will prompt the user to install these dependent modules
at the time of installation. Once all the demands are met the Wizard will
continue with the installation.</font>

<font face="Verdana" size=2>Of course in order to accomplish
the above successfully, another technology is needed that we will call the "Custom-Wizard".
The "Custom-Wizard" is a low level tool with the ability to handle the dreaded
Unix permissions, create, delete, set permissions and ownership among many
other things and will even work under "SAFE MODE" installations. So where
ever PHP runs the "Custom-Wizard" will work regardless of the ownership and
host system restrictions. This extended functionality will cut down almost
98% of the installation/customization issues present today in support requests.</font>

<font face="Verdana" size=2>The new and improved core will also
cater a solution for 3rd party developers who wish to hook directly into
the pnCore, to extend it in a safe and efficient way. This new plug & play
architecture will also be made available allowing module devs to tap into
the resources without the need of modifying core files. These changes alone
will provide certainty and unparalleled power and flexibility to all devs.
Also, new CMS importers will be available in order to convert from other
systems (i.e., PHPNuke, Xoops, Envolution) with as much accuracy as possible.</font>

<font face="Verdana" size=2>Also, another valuable tool, the
pnAntiCracker will become a module that will allow greater flexibility. By
doing this webmasters will be able to finer control its operation and general

<font face="Verdana" size=2>The visual editor will also become
a module with cross browser/platform capabilities in the latest generation
browsers. Along with this last point PN will be able to automatically detect
browser type versions and current rendering capabilities aiding in the creation
of themes and templates, which will be possible to enable in a per module

<font face="Verdana" size=2>Last but not least, this brings us
to templates. Yes, finally the 0.8 version of PN on top of the previous points
will bring you the Phoenix template-rendering engine. The work in the global
implementation of the Phoenix rendering engine will engage in parallel tasks
associated with it, as the complete compliance of all system and core modules
with the pnAPI. With the templating system short URL's are implemented and
all modules will be fully template based. The administration module will
have a new and improved design and new database back ends (i.e. postgreSQL)
with enhanced caching technologies for queries and content will be added
as well, a new logging mechanism will track trends and use of your site in
a friendly and powerful new ways.</font>

<font face="Verdana" size=2>This will be a next generation CMS
that includes a slim core, is extensible, modular and smart. And will support
several backend database servers taking full advantage of ADODB and will
finally provide a complete separation of core logic and presentation layers,
becoming an N-Tier application. (For those non-developers an N-Tier application
architecture is a model for developers to create a flexible and reusable
application. By breaking the application into tiers, developers only have
to modify or add to specific layers to change or scale up a tool.) </font><font face="Verdana" size=2></font>

<font face="Verdana" size=2>The benefits will be astounding. Developers can
focus on code; designers can work on layout and presentation; and writers
can focus on content.</font>

<font face="Verdana" size=2>This provides a solid foundation
to extend the users management area, abstraction of reusable code and much,
much more.</font>

<font face="Verdana" size=2>You may ask who will do this and

It is with great pleasure that I introduce you to, the newly elected Task
Force Team Leaders and Members along with its responsibilities and Tasks definitions.</font>

<font face="Verdana" size=2><font size="3" color="#990000">PostNuke Development
Task Force Teams</font>

<font face="Verdana" size=2>In order to streamline our efforts
and efficiently organize the work we are dividing the development into different
teams. Each team in addition to the responsibilities listed below will also
be responsible for keeping their specific tasks up to date in the NOC and
maintain any team related</font>

<font face="Verdana" size=2>PostNuke_Security</font>

<font face="Verdana" size=2>The security task team will primarily
be responsible for overall security of the PN core as well as responding
to the security mailing list. They will be the front line for all security
concern with PostNuke. They will also be responsible for the permissions
system found in PostNuke.</font>

<font face="Verdana" size=2>Team Leader: Tanis

Team Members: larsneo, markwest</font>

<font face="Verdana" size=2>PostNuke_Research</font>

<font face="Verdana" size=2>The research task team will primarily
be responsible exploring and testing new and fresh ideas and technologies
that could possibly be used in PostNuke. As new technologies are identified
they will be slated for inclusion in a future PostNuke release. Analyzing
the current needs of admins and conducting suability research to improve
the current state of PN</font>

<font face="Verdana" size=2>Team Leader: bharvey42

Team Members: Tanis, elgranazul, <a href=""target="_blank">vworld, class007, <a href=""target="_blank">spliffster, <a href=""target="_blank">Neo, pnCorps</font>

<font face="Verdana" size=2>PostNuke_Modules</font>

<font face="Verdana" size=2>The module task team will primarily
be responsible for the non-core (with the exception of 3rd party modules)
modules and blocks found in a PostNuke release.</font>

<font face="Verdana" size=2>Team Leader: <a href=""target="_blank">magicx

Team Members: <a href=""target="_blank">skooter, <a href=""target="_blank">nunizgb, class007, markwest, spliffster</font>

<font face="Verdana" size=2>PostNuke_Themes</font>

<font face="Verdana" size=2>The themes task team will primarily
be responsible for the core themes as well as the Phoenix rendering engine.</font>

<font face="Verdana" size=2>Team Leader: Neo

</font><font face="Verdana" size=2>Team Members: magicx, vworld, bharvey42</font>

<font face="Verdana" size=2>PostNuke_Core</font>

<font face="Verdana" size=2>The core task team will primarily
be responsible for the PostNuke API, the Install/Upgrade scripts and other
core logic of the PostNuke.</font>

<font face="Verdana" size=2>Team Leader: larsneo

</font><font face="Verdana" size=2>Team Members: Neo, <a href=""target="_blank">magicx, nunizgb, skooter, lcabrera, spliffster, cybersliver</font>

<font face="Verdana" size=2>PostNuke_Languages</font>

<font face="Verdana" size=2>The language task team will primarily
be responsible for all things related to language within the structure of

<font face="Verdana" size=2>Team Leader: nunizgb

</font><font face="Verdana" size=2>Team Members: elgranazul, class007</font>

<font face="Verdana" size=2>PostNuke_Database</font>

<font face="Verdana" size=2>The database task team will primarily
be responsible for the main database access found within PostNuke. Currently
that will be with the pnADODB logic, as well as moving the code forward to
be used with any database engine.</font>

<font face="Verdana" size=2>Team Leader: <a href=""target="_blank">lcabrera

Team Members: skooter, Tanis, xaplo, cybersliver</font>

<font face="Verdana" size=2>PostNuke_Releases</font>

<font face="Verdana" size=2>The releases task team will primarily
be responsible for the versioning, packaging, and posting new releases to
the appropriate locations. They will be the packaging experts and will provide
many various packages, including but not limited to *.tar, *.zip, *.deb and
possibly others like *.rpm.</font>

<font face="Verdana" size=2>Team Leader: magicx

</font><font face="Verdana" size=2>Team Members: larsneo, nunizgb, class007, bharvey42</font>

<font face="Verdana" size=2>PostNuke_Docs</font>

<font face="Verdana" size=2>The docs task team will primarily
be responsible for documentation found within the released PostNuke package.
That could be their own developed documentation or documentation from 3rd

<font face="Verdana" size=2>Team Leader: infopro

Team Members: jim
, pnCorps, class007</font>

<font face="Verdana" size=2>All Task Force Team leaders where
elected among their peers in an open vote in the IRC meeting. After these
elections a final vote was taken for the following: Lead Developer and Communications

<font face="Verdana" size="2">The elected individuals where:

Lead Developer: <a href=""target="_blank">Neo

Communications Officer: vworld</font>

<font face="Verdana" size=2>Last but not least, project manager
is HZink</font>

<font face="Verdana" size="3" color="#990000">Conclusion</font><font face="Verdana" size=2>

This summarizes the results of the meeting, presents us with the goals and
objectives for this 1st quarter and allows us to see clearly into the future.
All of these new developments and implementations will, be performed in
such a way that existing modules, themes and blocks will work flawlessly
while new generations of them will be able to do as much and more. These
new developments will also allow you to leverage your current and future
faith in PostNuke to be safeguarded and extended exponentially.</font>

<font face="Verdana" size=2>We invite you all to help us, because
together go even farther than we could if we worked alone. And we'd like
to thank everyone involved in the community for your support you are the
reason this project is unique and different from every other CMS out there!</font>

<font face="Verdana" size=2>This is the road, this is the
vision, and future of PostNuke.

<font face="Verdana" size=2>The PostNuke development team</font>

<font face="Verdana" size=2><font size="3" color="#990000">Related
Links:<font size="2">

IRC meeting log

</font><font face="Verdana" size=2>

<font face="Verdana" size=2>(Look under IRC Meeting logs document

<font face="Verdana" size=2>Organizational chart:

</font><font face="Verdana" size=2></font>

<font face="Verdana, Arial, Helvetica, sans-serif" size="2">pnDev
Profiles</font><font face="Verdana, Arial, Helvetica, sans-serif" size="2"></font>

<font face="Verdana, Arial, Helvetica, sans-serif" size="2">Phoenix
Rendering Engine Info</font>