Skip to main content

Some notes from work..

Some thoughts from the early planning at P...


Clarification on the component model

We need to define the components with all their properties, relations and functions. Perhaps some patterns from the JSF model can be used.

How is Content stored in the repository? Same way as in View? Should we seperate the Content-objects from Areas until they are published? This is related to workflow and document process routines, I guess. Note that it is important to maintain a modifiable workflow in the tools. Some smaller business will require a 1-step towards publishing an article, larger enterprises will need an x-step process involving collaboration from several stakeholders (author, publisher, editor).


Area is a meta-wrapper for content which describes how the Content will appear live (online).

Different sorts of Areas include Site, Page, Frame, Category, and so on. Literally all sorts of seperating folders that show up in the site map.

Traditionally, an object in a CMS (an article) is defined with meta-data which defines the graphical View of the object. This is per MVC, wrong! A news-article is usually put in a news-folder. This adds meta-data to the object, saying "This object is part of the News-category.". This wouldn't be a problem if it wasn't directly connected to the View of the site. If you're article is independant of View, then how come it is lying in the news-folder? What if you want to publish the same article in another folder? You could fix it by inserting a reference, but that would be a hack.

TODO: Clarify the point above :)

An Area contains other Areas and/or a reference to Content (a content object. We used to call these components, but still haven't figured out a better name for them).


A Content object is independant of the view and the Area(s) in which it resides.

Typical content objects: Article, Post, Comment, Webshop-item, Announcement

Attributes: Privilegie[], Action[], MetaTag[], language, Text[], WorkflowStatus, Dates

Operations: search, syndicate, modify, publish, crudImage, crudText, , move, reference

Template (is applied through a renderer on a Content object, resulting in a live object. The result will typically be an XML-snippet, like HTML or WML, or perhaps pure text):

Types: Article (title, subtitle, ingres, main, images), ArticlePreview (title, subtitle, ingres, thumbnail)

Images

Types: Thumbnail, NormalImage, ResizedImage, Logo

Attributter: title, MetaTag[]


Text

Types: title, subtitle, ingres, preview, mai, date

Attributes: Text (er meta-data i seg selv)

Operations: Rename, edit, internationalize


Requirements

These could resolve in a couple of user stories that will affect the component model. We don't need to model stories for obvious and primitive CRUD operations, but nifty stories that are required by the uses.

Elaborate the use of modules and how we will combine Actions and Components. How many of the data object should be predefined?

Typical CMS features

User/privilege/credentials/DRM/group and role-management

User interface - Usability

Authoring/editing - Core functiona

Integration of content - The jig-zaw

Meta-data - Adding value to information

Work process - Gate-setting

Templates - The dresses of a CMS

Version management - PĂ„literlighet

Globalization - Internationalization (i18n)

Rendering (page-generation) - Dynamics

Searching - Searchability/Findability

Personalization - Portals

Privileges - Access to the CMS

Syndication - Sharing content

Cross-media-publishing - Variation of access


Typical roles:

Author - composes articles, posts pictures

Manger - Check, confirm and submit new content

Adminstrator - Manage users, groups, user settings and order of authorization

Web-desinger - Design web layouts, pictures and styles

Sys-integrator - System components, object linkings


Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some