Coconut Radios

I'm coding a Forms package.
Forms will have content composed of specified items such as text boxes, lists, images, etc.
At present I'm just designing it as Galleries full of Forms. All documents inside each gallery use the same form definition, as the format definition is in the content of the gallery definition.

A simple way of thinking of it is as being able to define galleries of various format. Instead of images with captions, you might have images with captions and checkboxes. Or no…

(:arrow:)Don't make TOP be the parent of global Categories.
(:idea:) The parent of global Categories should be "Categories".
When package Categories is installed, by default the content-generating packages should get a top-level category by the same name. So top categories may be be Blog, Categories, Forums, FAQ, and Wiki.

It then becomes trivial for "Categories" to provide global structure, and for all other content types (Blog,Wiki,Gallery) to have their own category trees for local stru…

ReleaseOneallows Attachments to items.
Interesting that multiple entries can attach to the same Attachment.
Wiki pages can refer to an attachment with )) ((, which can be inserted by clicking on the list below the text area.
I wonder if all a site's Attachments are shared or if permissions control access to them, and what users can upload them.

It has been a tad awkward to find out what license TP is under. Easiest to find has been the LGPL classification displayed on the SourceForge project page. I created the License page and a note at the bottom of the front page. Visitors trying to compare 300 CMS packages can now find that vital info a tad faster.

I need more structure for my data and have been looking at LibertyPackage capabilities and possibilities.

I think WikiLens Structured Data has useful concepts. A Category can have data type definitions. Some technical info is at WikiLens Structured Data Tutorial.

In that case, Category implies a data format rather than only a subject classificat…

Looks like only one new item in ReleaseOneChangelog. That should be what is different between ReleaseOneA3 and Fresh Build. I created a new section in ReleaseOneChangelog for Fresh Build to make it easier to track. Also created a Table of Contents below it so the stuff further down is more easily accessible and more visible. A3 should still be OK for my learning.

A3 feels smoother than predecessors.

ReleaseZero content types don't quite meet my needs, although Wiki could store anything. LibertyPackage looks like it can do what I need, so ReleaseOne A3 is my current focus. I can't tell if the "Get the Fresh Build!" on TP.org homepage is newer nor whether to call it A3. ReleaseOne will do as the starting point for Liberty examination.

It is a tad awkward having a row of tabs saying "bitweaver CMS", I think that label should be at the end.

Ta…