I note this in my local staticpages-todo-wikiSirRobert wrote:For a future version, I wish the Plugin to be compatible with the multilingual Plugin, that allows the user to write each entry in multiple languages. When this would be implemented, the static Pages Plugin would make Serendipity to a real Content Management System with even more freedom and more international...
. It's a interesting feature.
Thank you,SirRobert wrote:Great Work!
The idea behind the "aboutpage" is a list of all childpages with a little image and the first sentences. So now you have not a normal linklist, you have a little preview, too.Wizard wrote:Not sure what/how the Article and AboutPage types are to be used. I noticed when I changed one of my article static pages to an about page the data contained in the page was truncated.
Have you a little example what you meen with "group static pages" please? I think you can group pages to use parents and childs.Wizard wrote:The ability to group static pages would be nice. Not every static page should link to the next. Perhaps it should stop when it reaches the last child.
Okay. It is in the next or nextnext realease.Wizard wrote:The ability to "hide" static pages. Not every static page should be linked. You will call out by the permalink explicitly.
Okay. It is in the next or nextnext realease.Wizard wrote:The ability to have the either the name of the static page or the words (top, next, previous) to be used instead. Could be a toggle switch.
Thank you very mutch.Wizard wrote:Other than these off the top of my head, I think the static page upgrade was a good thing. Thanks Falk
I have many static pages in total. The first 5 have a common subject matter. The remaining are other subjects. Perhaps broken into sub groups. Rather than having one large page which might make it hard to read, I break it up into the 5 separate pages. The first page would be the parent, while the remaining 4 would be children pages. You want the reader to click next or previous to read the appropriate page. Once you reach the "last" page then the next would be removed, similarly as you are "reading" the first page the previous is removed. In other words, only when you have children would you want the next/previous feature to be available. You wouldn't want the the last child to be able to call the next parent of series of parent/child relationships. If you take a look at the static pages on my blog, I have few such groupings. This one, http://www.socalwizard.com/serendipity/ ... motes.html is one subject , but if you notice the previous page has nothing to do with the subject. The next page is fine, but the "last" page of the article is calling for the first page of the next series of articles. I used HTML code to make a next/previous feature plus number of pages and total at the bottom of the pages. It's similar to the concept of categories for articles entries, but a date is not required or used since you may want to add a page or move pages around as chapters in a book. The ability to re-order static pages gives you this flexability. That is good. This is what I thought static pages are used for.falk wrote:Have you a little example what you meen with "group static pages" please? I think you can group pages to use parents and childs.Wizard wrote: The ability to group static pages would be nice. Not every static page should link to the next. Perhaps it should stop when it reaches the last child.
