The first PalmX release packages a standard Classic Theme with a companion plugin, a Palm OS-inspired visual system, native WordPress menus and templates, and a P2-style front-end workflow.
Release quality means the source, package scope, activation path, public route, and runtime rendering all agree.
PalmX keeps stable information pages separate from the chronological feed. About, installation, design notes, and changelog content belongs to Pages; short-lived conversation belongs to Posts.
The top navigation exposes both kinds of content without collapsing them into one stream.
A thread has a publication time and an activity time. PalmX stores activity separately so a new reply can bring a conversation back to the top without rewriting when the original post was published.
This keeps archive history honest while making live conversation discoverable.
PalmX treats P2 as a publishing pattern, not a separate database model. Posts stay in wp_posts, comments stay in wp_comments, and users remain WordPress users.
The companion plugin adds the small amount of workflow state needed for front-end posting, inline editing, reply actions, and activity ordering.
The notification path is also native: @horsepress is referenced from this reply, while the thread and activity timestamp remain WordPress data.
PalmX gives a WordPress feed the feeling of a small, legible personal organizer. The physical shell is decorative, but the content underneath remains native WordPress.
The feed is designed for short notes, links, quotes, images, and the replies that make a P2 community useful.
A native WordPress comment can bring this thread back to the top without changing the original post date. @horse this is the activity-time example.
The nested reply stays in WordPress comment_parent, so the thread remains native while the activity time updates.