Fork me on GitHub

List of features for future releases  Bottom

  • is there a list anywhere of features and enhancements that will be added to future releases of PN? I've looked and haven't found such a list anywhere. Occasionally I see individual features mentioned in discussion, such as a templating engine by 7.2.5, format stabilization in .8, the data bridge passed on by Neo, etc. What I haven't seen is a list anywhere of the planned features.

    I would like to know what is planned, and I suspect many others would as well. I wouldn't deign to ask when any feature might be implemented, I understand they will be ready when they are ready. I wnat to know what, not when. Any chance of that happening or does it exist somewhere and is just not easily found ?
  • you can check the postnuke roadmap in the documentation area at http://sf.net/projects/post-nuke

    --
    regards from germany
    ..::[Zikula Application Framework]::.. ..::[SEO-Blog]::.. ..::[CMS Sicherheit]::..
  • Thank you. That was a bit sketchy on details, though helpful. I hope a list of features that will be included will be added at some point. I see a lot of suggestions made and the fate of most is indeterminate. It's nice to know what one can look forward to.

    It would be helpful as well to explain some of the planned features, for instance, shorter URLS. I know what shorter means, and I know what a URL is. I don't know what the context of shorter URL is. Does it mean that instead of http://mydomain.com/modules.php?op=modload&name=Sections&file=index we'll have something like http://mydomain.com/Sections/index.php ? Is the purpose so that people can remember the shorter URLs (a practce I follow with my HTML sites)?

    Please keep in mind that some of us do other things than eat, breathe and drink PN and don't know exactly what is meant. That said, I'm having a lot of fun leanring how best to use it and integrate my site into it. It's really a nifty program and system.
  • see RFC 23 - Short URL Support

    Quote

    2. List of requirements for Short URL Support:
    Short URL support should cover 2 important (but slightly different)
    goals :
    * user-friendly URLs : for exchanging URLs, manual linking and more
    intuitive navigation inside a Postnuke site
    * search engine-friendly URLs : for facilitating crawling/spidering
    by robots, and automated linking by search engines, newsfeeds etc.

    In both cases, it should be possible to convert the current URL
    format http://www.mysite.com/index.php?module=...(&type=...)&func=...&pid=...
    into a virtual URL in the style http://www.mysite.com/index.php/.../.../...(?...)

    For user-friendly URLs, the resulting virtual URLs should also be
    "semantically meaningful" where possible. [2]

    In addition, the following technical requirements apply :
    * not only for Apache webservers
    This means that short URL support shouldn't require mod_rewrite
    * minimal impact on performance
    This means that short URL support shouldn't rely on some global
    search & replace of any URLs found in the HTML output buffer right
    before it's sent to the browser
    * site administrators should be able to turn on/off short URLs
    This means providing configuration settings for the site admins


    --
    regards from germany
    ..::[Zikula Application Framework]::.. ..::[SEO-Blog]::.. ..::[CMS Sicherheit]::..
  • Thanks again. That was most informative. You all might want to include a link to it from the road map article you referred me to earlier. For those of us who do take the time to search for answeres rather than asking again, it is difficult to find answers, or meaningful ones. This is an area PN should improve on. The proper conveyance of information is one of the most critical elements of any site.

    I don't want to sound overly critical and I hope I don't. Even some fine commercailly supported programs lag behind in the area of their documentation. I've grown accustomed to it and would rather they allocate their time to furthering development of the software than spend time writing docs, especially when those docs will be outdated due to continued development. Even so, the PN website does a poor jog of promoting PN, a discussion that has been held before and recently. That's why I submitted some revisions and suggestiosn that better convey what PN can do and why someone might want to use it. I can't write code (yet), but I can communicate effectively and will help the PN project when and where I can.
  • Quote

    but I can communicate effectively and will help the PN project when and where I can

    then you should consider to contact 'Infopro' about joining the pnCorps team wink
    all efforts to enhance the docs/site/whatsoever are welcome - and critical voices are heard (and important), too...

    --
    regards from germany
    ..::[Zikula Application Framework]::.. ..::[SEO-Blog]::.. ..::[CMS Sicherheit]::..
  • I think I'll do that. I had already sent him both proposed revisions for the site with a greater description of PN's capabilities as well as revised installation instructions based on my recent experiences (also posted here). It hadn't occured to me to be a member of the team since I don't code. However, I can write effectively and I'm sure I can make many things clear to others. I've already helped a few with installing PN.

This list is based on users active over the last 60 minutes.