å skriva for web

det er annleis å skriva for lesing på web enn for lesing på papir.

dette er for oss som treng litt råd og “hugselapp” når det gjeld å skriva noko som er lett å lesa på web.

viktigaste fyrst

folk skummar ofte websider.  skumlesing gjer at den viktigaste informasjonen bør koma fyrst – start gjerne med konklusjonen.

avgrensning: skriv korte avsnitt, kortfatta setningar – mykje kortare enn på papir.  ha ein idé per avsnitt.

bruk gjerne overskrifter og lister

  • bruk gjerne lister for å ramsa opp fleire poeng
  • bruk gjerne overskrift – primært som hjelp til skumlesing
  • teksten skal gi meining på papir – unngå “klikk her” o.l., og bruk heller lenker med meining
  • det er lettare å legga merke til feit skrift enn kursiv skrift
  • skriv gjerne direkte til lesaren – slik får du lettare kontakt
  • anekdoter heller enn kompakte data

nøkkelord, søk

få fram nøkkelord – gjerne i overskrifter og i starten på avsnitt, som blikkfang.  tenk også på kva folk søker etter når dei ynskjer å finna innhald som det du skriv – og bruk slike ord i tekst og overskrifter.

som på papir

det som er smart når ein skriv på papir er også smart på web:

  • tenk på målgruppe
  • tenk på sjanger – kva vil du med teksten?
  • la konklusjon/ samandrag/ innleiing svara på kven, kva, når, kor, korleis

kjelder

lesetips

which cms?

so you’re starting up a web site, and would like an easy way to manage it.  there’s a lot of systems available to manage form and content of a web site.

first off, i would like you to take any proprietary systems off the list – there’s no reason to get your content locked-in and get dependent on only one vendor.  that doesn’t mean you shouldn’t look at commercial offers – just make sure your content can be backed up and migrated relatively easy when you should need it.  in practice, i would consider products containing open source tools and commercial, technical service and maintenance.

there’s several types of content tools out there.  there’s the traditional type of CMS – in my opinion joomla (JO) and drupal (DR) are two of the best examples of this type.  and there’s the blog type, like movable type (MT) and wordpress (WP) – in my opinion two of the best of this type.  

if you’re not a big news organisation, e.g., like a newspaper or PR department of a multi-national company,  with complex and specific demands on the workflow of publishing, chances are that your needs can be met by MT or WP.  while these started out as blog tools, they are pretty good for managing other content, too.

non-blog use of blog tools

here’s a nice summary of non-blog use of tools like WP and MT, by a guy called Abhijit Nadgouda.  it’s focus is on WP, but many of the arguments are valid for MT as well. 

WordPress Makes Sense For Many Non-Blog Websites

(my italics…)

WordPress makes a lot of sense for many simple web sites, including the non-blog ones. … WordPress provides good infrastructure of web publishing and gives you tools to build an interactive web site.

….
Pages and Posts

WordPress supports two basic types of content – Pages and posts. Pages are used to hold information that is valid for a bigger span of time. For such content, a change overwrites the earlier content. Posts are used for content which is more dynamic, like news and updates. In stead overwriting with changes, such content builds an archive.

Now, any web site that represents an entity – company, product, educational institution or an individual, at least in today’s age, has both such types of content. Providing news and updates and their helps keep the readers and customers uptodate through subscriptions.

The recent versions of WordPress also lets you set one of the pages as the homepage.

….
Feed is one of the most used techniques by readers to keep themselves updated.
….
you can reach out to the web, feedreader and email users by just publishing the content once.

….
The templating system of WordPress supports a lot of customization

….
administration of a web site is one of the biggest hurdles in maintaining it. WordPress provides an easy to use administration interface for writing and managing content, and configuration of the web site.

….
WordPress also sports a simple but effective roles and capabilities system. This is extremely useful if you appoint different people for managing the web site configuration, managing content or adding the content.

….
Interaction

Comments is something I believe all web sites should borrow from blogging. Comments can be used to interact with the readers and customers. They can contact you or contribute to the content or report problems using them. Comments are supported for pages as well as individual posts.

….
completely open source … huge community

for me, two of the most important keywords here are “pages” and “feeds”. 

when you think blog, you might not think about web pages, but MT and WP inherently support the creation and maintenance of web pages.

web feeds might not be on your radar, but the phenomenon is gaining momentum.  it’s useful in the following ways:

  • it alerts people who use a feed reader that you’ve got new content on your website
  • you don’t have to do anything extra, like an email or newsletter – publish once, read everywhere…

a few differences

here’s a few central differences between movable type (MT), wordpress (WP), drupal (DR), joomla (JO).

(among the) sources:
http://www.alledia.com/blog/general-cms-issues/joomla-and-drupal-%11-which-one-is-right-for-you?/
http://www.cmsmatrix.org

  • multi-site, i.e., run several web sites/ domains from one installation
    • yes: MT, DR
    • adaption: WP MU
    • plugin: JO
  • plug-ins
    • many: MT, DR
    • a whole lot: WP, JO
  • publish content – differences is especially clear on high server load
    • MT: publish to static pages (takes a little more time after changes, but is faster)
    • WP, JO, DR: interpreted, i.e., dynamic pages, reads content from database every time.  (change is published right after save, but takes more time)
  • public mailing lists
    • yes: WP, MT, DR
    • no: Joomla

what others think

i’ve taken a look at what some other people think.  (i agree with much of the cited text…)

Comparing Joomla vs Drupal Content Management Systems – Part I/II

[on joomla and drupal]

The CMS Report claims these are considered the top two open source CMS programs, with Drupal excelling in program architecture, and Joomla excelling at function (while some say style).

MovableType 4 vs. WordPress 2.2

two of today’s premier content management systems
….
WordPress is famous for its “5 minute installation”
….
All in all, both WordPress and Movable Type were built with the end-user in mind and thus are continually improving their interfaces. Both are similarly equipped with intuitive admin areas, and neither have much of a learning curve.
….
The WordPress community is both large and talented. Themes and plugins are easily located on their respective directory pages on the WordPress site. The variety and quality in both categories is difficult to surpass. Even if you’re not content with something you find, enterprising web developers and newbies alike can easily create themes and plugins with the easy to use and well implemented Codex.
….
Movable Type is a comparably customizable system. Its community has also been proactive in the creation of plugins and themes can easily be found in their respective directories. … Six Apart’s done a great job of documenting all of the Developer info
….
There are a few things in WordPress that I’d like to see in MT in the near future: combining trackbacks and comments, RSS for comments, and permalinks for comments, for example.
….
Movable Type 4 introduces some features which take it beyond the call of duty. These include: OpenID, Admin XML Feeds, cross-blog aggregation, and more.
Virtually anything can be done with WordPress plugins, of course, but with Movable typ
e it’s all built in.

from the comments:

MT [is] good for larger sites especially where finer template control is required.
(Christen)

Joomla etc. can’t touch WP for sheer architectural elegance. …. I create small business sites, and I haven’t created one without WordPress as its CMS in a year now.
(Matt)

MT … is able to generate completely static HTML pages that do not require DB transactions as part of serving pages.
(aks)

Drupal is .. kinda like big beast working in the corner. It’s not pretty and it’s not friendly, but it gets the job done. Still, as far as competition goes – WordPress is still the current lead dog in all my development.
(Sofie)

MT offers both static and dynamic publishing, while you can only use dynamic publishing with WP.
(Dave)

Choosing an appropriate CMS

I use Joomla on very large sites when I have no choice.
….
Joomla spits out a lot of tables and non-standard code and has a complex back end that requires, on average, about an hour of training time with the client. I end up doing a lot of hacking on modules to make them fit into templates
….
Drupal is ideal for “organic” sites, or community based sites. If you want a site where the content grows from blogs, forums and comment discussions, this is a decent choice.
….
it’s a far simpler system to customize than Joomla.
….
I’m currently in love with WordPress. It’s a blog, but with a little work can become a CMS. If I’m doing a site with 5-10 static pages and a news page and gallery, this is the way I go. A simple back end and easy to use editor. No overkill and it’s easy to template.

Why pay for what’s free?
 

Almost everyone I know in magazines is using some sort of overpriced dinosaur to put their stories on the Web. And when I suggest that it may be time to dump their existing CMS and use a free system, people tend to freak out.
….
So I’m just thrilled to have an example of a gorgeous site with millions of page views that runs on WordPress, which happens to be my all-time favorite piece of publishing software. [XXL]

from the comments:

We dumped a proprietary system for Joomla… It’s far more powerful than what we had before, and it’s supported by an active development community. Even better, I’m not beholden to one vendor. All I need to do is type “Joomla developer” in to google. For smaller sites, we use Movable Type, which I imagine is similar to WordPress.
The days of publishers paying $50K just for CMS software is over.
(Dave Newcorn)

Ten reasons Joomla!/Mambo is an outdated CMS

The layout is based on tables. It is also very cluttered
….
The administrative interface is slow and not very user friendly.
….
There is a plethora of templates and plugins, but it’s very hard to find good ones. Many plugins are badly developed, very specialized or cost money.
….
This is very different from the WordPress community, where most plugins are of high quality, and where you quite easily can find the plugins thanks to the blogging community.
….
The code base is huge and the API is complicated and often inconsequent.
….
The whole CMS package is big and bulky, and so is the system itself.
….
The category system is inconseqent
….
Development is very slow.
….
Bad support for user content creation

from the comments:

I’ve taken the step to actually use WordPress as a CMS instead of the ones out there, since I have way more control over Wp than over Joomla.
….
With a couple of plugins I got the same functionality out of my Wp as I did from a vanilla installation of Joomla!.
(Yyy)

WordPress compared to Joomla

compare them as personal publishing platforms
….
As for potential, WordPress is a winner. Being aimed from the beginning on publishing as a priority task, it is still (at v2.0) simple and fast when it comes to publishing.
….
Joomla is more powerful as a CMS, but …. [WP] may outperform Joomla as a CMS.
….
WordPress built around writing content and publishing that content. Joomla from the beginning built around presentation of content

WordPress is Infinitely Extensible

from the comments:

Straight to the point: This is exactly the same I recently thought when building a rather complex website for the first time with WordPress – used as a CMS!
(Michael)

I’ve used countless CMS before. … Joomla, Mambo … and a slew of others that I can’t even remember their names – but WordPress is probably the best, and most accessible package I’ve ever used.
(Tadd)

As someone who almost exclusively uses WordPress as a framework for all my site work I do, I’d have to disagree about how great Drupal/Joomla are. I’m speaking strictly from the client -side of the park with this statement. … clients would never be able to make their way around the admin sections of Drupal/Joomla comfortably.
… for me it comes down to ease of use for the client and you can’t get much easier than WordPress
(Pop)

my conclusion

i’d go for a solution with movable type or wordpress, perhaps included in a package with commercial, technical support and maintenance.

(i definitely wouldn’t go for any proprietary solution!)

in WP and MT, it’s easy to get started with the core process – i.e., write and publish content – and there’s plenty of available plugins and templates.  and since WP and MT are open source and have decent developer communities, it should be possible to hire someone to do tailored functionality or design when needed.

which one, MT or WP?  it’s down to personal preferences, if there’s commercial support available, if you like PHP or Perl, etc.  below is some more resources to help you decide.

some resources

wordpress: http://wordpress.org/
plugins:
http://wordpress.org/extend/plugins/
http://mashable.com/2007/08/16/wordpress-god300-tools-for-running-your-wordpress-blog/
themes: http://themes.wordpress.net/
a few non-blog examples: http://blog.pixelita.com/10/10-non-blog-wordpress-sites/

movable type: http://www.movabletype.org/
plugins: http://plugins.movabletype.org/
on themes: http://wiki.movabletype.org/Main_Page#Templates.2C_Themes_and_Designs

drupal: http://drupal.org/

joomla: http://www.joomla.org/