Finally standardizing on the DTP Component definition:
{
logId: 'my-service',
index: 'myService',
className: 'MyService',
}
And I'm not too far from using UUIDs in there, too, so I have one (1)
standard way of referencing them.
- Make pages drop-down and display children when applicable
- Make pagination work in mutiple views
- Author route author/posts
- Author route author/drafts
- Others such as author page views
- Added pagination to admin/post
- Author pages at /post/author/:username
- Post timestamp rendering in local time
- Post tags at /post/tag/:tagSlug
- Changing site icon and default post image
- Integrated EventEmitter2 for async event processing
- Changed jshint reporter module URL to avoid use of SSH
- Core can disconnect a service node, generates many events
- Service Node can disconnect a Core, generates many events
Nothing yet processes those events. Many things need to be cleaned up
and removed based on a Core Node disconnection. The Core itself needs to
remove all Kaleidoscope events and other data received from the Service
Node, and the Service Node needs to remove all CoreUser records (and
everything they did while there).
That's going to take a minute to implement throughout all the systems.
- Multi-channel support for Venue
- Venue channel editor and management for Admin
- Venue UI components for channel card, channel list item, and channel
grid
- Home page fixes and updates
- Image display and responsiveness for home page down to mobile
- SiteLink model, service, etc., for adding links to your Site
- Many navbar enhancements and fixes
- RSS, ATOM, and JSON feed generators
rob
CyberShell