Beberapa macam jenis CMS Open Source

Beberapa waktu yang lalu sudah saya paparkan apa itu CMS ??? 

Lebih kurang definisi CMS sendiri adalah Sebuah sistem atau aplikasi software yang memberikan kemudahan-kemudahan kepada para penggunanya dalam mengelola, mengupload, mengedit konten untuk ditampilkan pada sebuah web dan mengadakan perubahan isi konten sebuah website tanpa perlu harus dibekali pengetahuan tentang hal-hal yang bersifat teknis tanpa harus memiliki pengetahuan tentang bahasa pemrograman web. Dengan demikian, setiap orang, penulis maupun editor maupun yang baru belajar web designer/development atau orang awam sekalipun setiap saat dapat menggunakannya secara leluasa untuk membuat, menghapus atau bahkan memperbaharui isi website tanpa campur tangan langsung dari pihak webmaster.

Berikut beberapa script web CMS Open Source yang biasa digunakan untuk membangun sebuah website, yang biasanya dipakai utk berbagai keperluan seperti :

• Untuk membuat Persoanal Website atau Company Profile
• Sebagai web Portal atau website komunitas.
• Untuk Galeri foto, video streaming, audio
• Aplikasi E-Commerce atau web toko online

Beberapa diantaranya :

1. WORDPRESS

WordPress salah satu CMS opersource yang paling digemari di dunia, biasanya digunakan untuk mesin blog(blog engine). wordpress menggunakan bahasa pemrograman php dan database mysql. WordPress termasuk cms yang user frienly dibandingkan dengan joomla dan drupal. 

Keunggulan :
* Cukup mudah digunakan
* Sederhana
* Akun gratis wordpress dapat diperoleh dengan menftar di wordpress.com
* Dapat dijalankan di websirte kita sendiri
* Dapat dijalankan di localhost
* Banyak plugin tambahan
* Template dapat dimodifikasi
* Penggunaan kompak
* Mendukung SEF[seach engine friendly]

Kelemahan :
* Fitur managemennya sedikit sehingga sebagian orang menganggap terlalu sederhana
* Jarang digunakan oleh website besar
* Pluginnya tidak sebanyak jomla.

Website : WordPress.org dan WordPress.com

2. MAMBO

Mambo pada awalnya disebut Mambo Open Source atau MOS adalah free software atau open source content managemen system yang digunakan untuk membuat dan memanagement website melalui sebuah interface yang simple. Sekarang ini mambo banyak dipilih dan digunakan kerana kemudahan yang diberikan untuk mengoperasikannya. Seperti hampir semua CMS yang digemari mambo memiliki kemampuan templating atau kemampuan untuk mengganti tampilan website tanpa harus melakukan upload / perubahan kontent.

Mambo menyediakan kemudahan dan komponen-komponen seperti shopping chart, photo gallery, forum, pools, calendars website searching, multi bahasa dan lain-lain. Hampir sebahagian besar website yang kami bangun menggunakan Mambo sebagai pilihan CMS. Sebuah kebanggaan bagi Indonesia karena salah satu CoreDev Team Mambo adalah orang Indonesia asli.

Kelebihan :
1. Digunakan oleh website sederhana sampai website profesional
2. Mudah dioperasikan
3. Dapatkan dijalankan di komputer lokal
4. Pluggin tambahan
5. Template bisa diubah dan bisa membuat sendiri

Kelemahan :
1. Plugginnya terbatas
2. Defaultnya sangat tidak mendukung mesin pencarian.
3. Krisis kepercayaan open source

Website: Mambo Foundation

  

3. JOOMLA

Kata Joomla diambil dari sebuah kata dari suku Swahili iaitu Jumla yang bermaksud “menjadi kesatuan” bisa dikatakan memiliki kemampuan sama dengan Mambo, kerana CMS ini code awalnya Joomla! 1.0.0 menggunakan code Mambo 4.5.2.3.

Banyak komponen Mambo juga boleh digunakan di sebagai Plugin Joomla begitu juga sebaliknya. Kemampuan kami memilih plugin yang tepat untuk setiap release yang dipilih memalui proses penyelidikan mengindari terjadinya konflik atau crash karena banyak plugin memerlukan penyesuaian disetiap versinya.

Website: Joomla.org

Kelebihan :
* Diklaim sebagai cms opensource dengan pengguna terbanyak.
* Digunakan untuk website sederhana sampai profesional.
* Sering update baik dari segi cms.
* Mudah dioperasikan
* Dapat dijalankan di komputer lokal
* Banyak plugin tambahan.
* Template dapat dirubah dan dapat membuat template sendiri
* Conten joomla dapat dikembangkan

Kelemahan :
* Defaultnya tidak mendukung,namun ada komponen pendukungnya baik yang gratis maupun berbayar
* Plugin yang didapatkan terkadang bug error
* Terkadang ada ketidaksesuaian anatara cms dan plugin.

Website : Joomla.org

4. DRUPAL

Drupal adalah content management system dan blogging engine yang pertama kali dikembangkan oleh Dries Buytaert sebagai sebuah sistem bulletin board. Sekarang ini Drupal banyak digunakan oleh website-website yang mempunyai traffic tinggi dan mempunyai tahap pengendalian sebuah website yang hirarki yang kompleks.

Keunggulan :
* Diklaim cms yang mengalahkan joomla.
* Digunakan untuk website sederhana hingga profesional.
* Mudah dioperasikan.
* Dapat dijalankan di localhost.
* Template dapat di ubah sekehendak kita dan bisa membuat template sendiri.
* Mendukung SEF.

Kelemahan :
* Penggunaannya tidak terlalu banyak,terutama diIndonesia
* Pluginnya tidak sebanyak joomla

Website: Drupal.org

5. AURA

AuraCMS adalah hasil karya anak bangsa yang merupakan software CMS (Content Managemen System) untuk website yang berbasis PHP4 & MySQL berlisensi GPL (General Public License).

Dan tak lupa bahwa software ini mungkin tak semuanya memenuhi harapan pemakai, oleh karena itu diharapkan adanya kritikan, sumbangan pikiran atau mungkin bentuk modifikasi dari para pengguna sekalian baik berupa modul maupun perubahan-perubahan lainnya yang dapat menjadikan auraCMS ini menjadi lebih baik.

Dengan bentuk yang sederhana dan mudah ini diharapkan dapat digunakan oleh pemakai yang masih pemula sekalipun.

Kelebihan :
- Simpel dan mudah digunakan.
- Sesuai dengan slogan-nya AuraCMS termasuk cms yang sangat simple dan mudah digunakan.

Kekurangan

1. System

• Hanya terdapat tiga level pengguna yaitu Administrator, Editor dan User.
• Meski secara default terdapat tiga level pengguna namun pemanfaatan maksimal hanya pada dua level, yaitu Administrator dan User.
• Tidak ada email pemberitahuan jika ada komentar masuk, baik bagi administrator penulis maupun pengomentar sebelum-nya.

2. Keamanan

• Nama File yang di Upload melalui system default CMS ini tidak diproteksi.
• Dengan demikian siapapun yang pernah melakukan download dan mengingat alamat file dapat melakukan download kembali dilain waktu tanpa harus login, melainkan cukup dengan mengetikan langsung alamat file yang telah didapat sebelumnya.

3. Pengembang, Konstributor dan Pengguna

• Pengembang menulis script dengan sangat tidak rapi.
• Kelakuan ini sangat menghambat perkembangan karena pengembang diluar tim utama membutuhkan waktu lebih untuk merapikan hingga menjadi sulit dalam mempelajari AuraCMS.
• Dokumentasi sangat minim.
• Baik untuk system maupun sekedar deskripsi singkat tentang sebuah modul yang terdapat di daftar download terasa sekali sangat minim dan informasi yang diberikan sangat jauh dari kata cukup.
• Konstributor Pelit.Para pengembang modul diluar tim utama pengembang AuraCMS adalah orang-orang yang pelit dan mata duitan, mereka tidak rela membagikan modul-modul yang telah mereka buat kepada pihak lain secara cuma-cuma.
• Pengguna Manja. Pengguna langsung AuraCMS didominasi oleh orang-orang yang manja, hanya bisa mengeluh mengeluh dan mengeluh tanpa konstribusi positif yang membangun.

Namun terlepas dari kelebihan dan kekurangan AURA, kita tetap harus bangga karena itu merupakan karya Anak Bangsa....
website : www.auracms.org

iklan gratis hotel malang lab bahasa

Read More

Apa itu CMS ???

Selama ini ternyata banyak di antara sobat-sobat yang belum paham apa itu CMS... maaf, mungkin tulisan ini sedikit terlambat.. :D .. Baiklah, di sini akan kita bahas sedikit apa itu CMS..

CMS (Content Management System) adalah suatu sistem yang digunakan untuk mengelola dan memfasilitasi proses pembuatan, pembaharuan, dan publikasi content secara bersama (collaborative content management). Content mengacu pada informasi dalam bentuk teks, grafik, gambar maupun dalam format-format lain yang perlu dikelola dengan tujuan memudahkan proses pembuatan, pembaharuan, distribusi, pencarian, analisis, dan meningkatkan fleksibilitas untuk ditransformasikan ke dalam bentuk lain. Terminologi CMS sendiri cukup luas, di antaranya mencakup software aplikasi, database, arsip, workflow, dan alat bantu lainnya yang dapat dikelola sebagai bagian dari mekanisme jaringan informasi suatu perusahaan maupun global.

CMS (Content Management System) terbukti merupakan sebuah aset penting bagi perusahaan untuk mengelola content situs web dan portal secara efisien dan efektif. Saat ini, berbagai perusahaan mengkombinasikan content tak berstruktur dengan transaksi tradisional dan application logic untuk membangun aplikasi berbasis Web. Web application ini mewujudkan interaksi yang lebih personal dengan para user-nya, dan meningkatkan kinerja perusahaan dengan menyediakan layanan mandiri bagi para karyawan, partner, penyedia barang dan pelanggan. Aplikasi berbasis Web yang semakin berdaya, secara tidak langsung meningkatkan peranan dan pentingnya CMS sebagai bagian dari infrastruktur aplikasi perusahaan. Alhasil, pemilihan CMS yang akan diterapkan di perusahaan tidak bisa dianggap remeh.

Dengan adanya CMS yang terintegrasi dengan sebuah WebSite akan memberikan suatu nilai lebih yang akan meningkatkan fungsionalitas dan fleksibiltas dari Web Site tersebut, terlebih pada WebSite yang tujuan pemanfaatannya sebagai media promosi dan membangun citra konsumen, dimana kontinuitas dan inovasi dalam pemasaran produk-produk secara berkala dan berkesinambungan sebagai suatu hal yang memegang peranan penting dalam tercapainya target pemasaran.

CMS (Content Management System) adalah aplikasi web yang siap pakai. Ini merupakan istilah untuk pemilik website mengupdate websitenya tanpat bantuan pengembang web. Yang dilakukan pengembang web hanya installasi awal dan konfigurasi awal saja. Selanjutnya untuk pengisian artikel, gambar, dan konten-konten lainnya bisa dilakukan oleh pemilik website tanpa harus mengetahui kode-kode HTML ataupun pemrograman web seperti PHP atau ASP .NET

CMS sangatlah berguna dan handal untuk memisahkan tangungjawab antara penulis konten dan desainer web. Dengan demikian, desainer web dapat berkonsentrasi pada tugasnya terutama  masalah desain tampilan dan penempatannya. Sementara itu, siapapun  yang tidak memiliki kemampuan teknis dapat bertanggujawab atas masalah konten, misalnya menuliskan kalimat dan meletakkan gambar di situs web. Jadi, cara kerja CMS melibatkan desainer web dan penulis konten.

CMS membuat halaman web menjadi dinamis. Artinya, halaman web belum benar-benar ada sampai kita memastikan untuk memublikasikannya. Dengan demikian, konten dapat di perbaharui dan hasilnya dapat dilihat terlebih dahulu tanpa harus di publikasikan. Halaman web dinamis berguna saat pengembangan konten, tetapi pengembangannya belum seluruhnya selesai.

Sebenarnya CMS sangatlah rumit, berisi ribuan file dan script yang saling bekerjasama, berpadu dengan basis data untuk menghasilkan situs web. Intinya CMS di desain dan di ciptakan oleh tenaga ahli yang mempunyai kemampuan teknis, tetapi dapat digunakan, di atur, dan dijalankan oleh orang awam, sekalipun tidak mempunyai kemampuan teknis.

semoga bermanfaat... :)

Read More

10 Things To Consider When Choosing The Perfect CMS

Choosing a content management system can be tricky. Without a clearly defined set of requirements, you will be seduced by fancy functionality that you will never use. What then should you look for in a CMS?

I have written about content management systems before. I have highlighted the their hidden costs, explained the differentiators behind the feature list and even provided advice for CMS users. However, I have never actually asked what features you should look for in a content management system. And that is what I will address here.

When I left home for university my mother taught me a valuable lesson. If you want to save money, never go grocery shopping when you are hungry, and always write a list. If you don’t, you’ll be tempted to buy things you don’t need.

The same principle is true when it comes to selecting a content management system. Without a clearly defined set of requirements, you will be seduced by fancy functionality that you will never use. Before you know it, you’ll be buying an enterprise-level system for tens of thousands of dollars when a free blogging tool would have done the job.

How then do you establish your list of requirements? Although your circumstances will vary, here are ten things that are particularly important.

[Offtopic: By the way, did you know that Smashing Magazine has a mobile version? Try it out if you have an iPhone, Blackberry or another capable device.]

1. Core functionality

When most people think of content management, they think of creating, deleting, editing and organizing pages. They assume all content management systems do this and so take that functionality for granted. However, that is not necessarily the case. Nor is there any guarantee that such functionality will be presented in an intuitive way.

Not all blogging platforms, for example, allow the owner to manage and organize pages in a tree hierarchy. Instead, individual “posts” are automatically organized by such criteria as date and category. In some cases, this is perfectly adequate. In fact, this limitation in functionality keeps the interface simple and easy to understand. However, in other circumstances, the limitation can be frustrating.

Consider carefully the basic functionality you need. Even if you do not require the ability to structure and organize pages now, you may in future. Be wary of any system that does not allow you to complete these core tasks.

Also ask yourself how easy it is to complete these tasks. There are literally thousands of content management systems on the market, the majority of which offer this core functionality. However, they vary hugely in usability. Always test the system for usability before making a purchase.

2. The editor

The editor is one core feature worth particular attention. The majority of content management systems have a WYSIWYG editor. Strangely, this editor is often ill-conceived, despite the fact that it is the most used feature within the system.

The editor is the interface through which content is added and amended. Traditionally, it has also allowed the content provider to apply basic formatting, such as font and color. However, developers have recently moved away from this type of editor to something that reflects best practice.

The danger of traditional WYSIWYG editors is two-fold. First, content providers are given too much control over the design. They are able to customize the appearance of a page so much that they undermine the consistency of the design and branding. Secondly, in order to achieve this level of design control, the CMS mixes design and content.

The new generation of editors takes a different approach. Content providers use the editor to mark up headings, lists, links and other elements, without specifying how they should appear.

Ensure your list of requirements includes an editor designed on this principle and that does not give content providers control over the appearance. At the very least, look for content management systems that allow the editor to be replaced with a more appropriate solution.

The editor should also be able to handle external assets, including images and downloadable files. That brings us to our next point: management of these assets.

3. Managing assets

Management of images and files is badly handled in some CMS’. Badly designed systems can frustrate users with poor accessibility and usability. Images in particular can cause problems. Ensure that the content management system you select forces content providers to add attributes to images. You may also want a CMS that provides basic image editing tools, such as cropping, resizing and rotating. However, finding one that does this can be a challenge.

Also, consider how the content management system deals with uploading and attaching PDFs, Word documents and other files. How are they displayed to end users? Can descriptions be attached to the files, and is the search function capable of indexing them?

4. Search

Search is an important aspect of any website. Approximately half of all users start with search when looking for content. However, the search functionality in content management systems is often inadequate.

Here are a few things to look for when assessing search functionality:

• Freshness: how often does the search engine index your website? This is especially important if your website changes regularly.
• Thoroughness: does it index the entire content of each page? What about attached files, such as PDFs and Word, Excel and PowerPoint documents?
• Speed: some search engines can take ages to return results. This is especially common on large websites.
• Scope: can you limit the scope of the search function to a particular section of the website or refine search results once returned?
• Ranking: how does the search engine determine the ranking of results? Can this be customized by either the website owner or user?
• Customization: can you control how results are displayed and customize the design?

The issue of customization, of course, goes far beyond search.

5. Customization

I have had the misfortune of working with content management systems that are completely inflexible in their presentation.

Your content’s presentation should not be dictated by technology. It is simply not necessary now that we have techniques to separate design and content. Unfortunately, like some Web designers, many CMS developers have not adopted best practices and have created systems that produce horrendous code. This puts unreasonable constraints on the design and seriously impacts accessibility.

You need a content management system that allows flexibility in the way content is retrieved and presented. For example, can you retrieve news stories in reverse chronological order? Can you display events in a calendar? Is it possible to extract the most recent user comments and display them on the home page? Flexibility makes a CMS stand out.

Speaking of user comments, all forms of user interaction are worth mentioning.

6. User interaction

If you intend to gather user feedback, your CMS must provide that functionality or allow a third-party plug-in to provide it. Equally, if you want to host a community on your website, then you will require functionality such as chat, forums, comments and ratings.

At a minimum, you will need to be able to post forms and collect responses. How easy does the CMS make this process? Can you customize fields or does that require technical expertise? What about the results? Can you specify who they are emailed to? Can they be written to a database or outputted as an Excel document? Consider the kind of functionality you need and look for a CMS that supports it.

Also ask what tools exist for communicating with customers. Can you send email newsletters? Can recipients be organized into groups that receive different mailings? What about news feeds and RSS?

Finally, consider how you want to manage users. Do you need to be able to reset passwords, set permissions or export user information to other systems?

But user permissions are not the only things that need managing. You should also consider permissions for those editing the website.

7. Roles and permissions

As the number of content providers on your website increases, you will want more control over who can edit what. For example, one group may need to be able to post job advertisements but not add content to the home page. This requires a content management system that supports permissions. Although implementation varies, permissions normally allow you to specify whether users can edit certain pages or even entire sections of the website.

As the number of contributors grows still further, you may require one person to be able to review content being posted to ensure accuracy and consistency in tone. Alternatively, content may be inputted by a junior staff member who requires the approval of a more senior person before making it live.

In both cases, you’ll need a CMS that supports multiple roles. This can be as simple as having one “Editor” and one “Approver” role, or more complex with customized roles and different levels of permission.

Finally, enterprise-level content management systems support entire workflows in which page updates have to go through a series of checkpoints before going live. These complex scenarios require the ability to roll back pages to previous versions.

8. Versioning

Being able to revert to a previous version of a page allows you to quickly recover if something is posted by accident.

Some content management systems have complex versioning functionality that allows you to roll back to a specific date. However, in most cases, this is overkill. The most common use of versioning is simply reverting to the last saved state.

Although this sounds like an indispensable feature, in my experience it is rarely used expect in complex workflow situations. That said, although versioning was once a enterprise-level tool, it is becoming available in more and more content management systems.

The same can be said of of multi-website support.

9. Multiple website support

With more content management systems allowing you to run multiple websites from the same installation, I would recommend this as a must-have feature.

Although you may not currently need to be able to manage more than a single website, that could easily change. You may decide to launch a new website to target a narrower audience.

And with the growth of the mobile Web, you may want to create a separate website especially for mobile devices. Whatever the reason, having the flexibility to run multiple websites is important.

Another feature you might not require immediately but may in future is multilingual support.

10. Multilingual support

It is easy to dismiss support for multiple languages. Your website may specifically target the domestic market, or you may sell a language-specific product. But think twice before dismissing this functionality.

Even if your product is language-specific, that could change. It is important that your CMS be able to grow with your business and evolving requirements.

Also, just because you are targeting the domestic market doesn’t mean you can ignore the issue of language. We live in a multicultural society in which numerous languages are spoken. Being able to accommodate these differences gives you a significant edge over the competition.

That said, do think through the ramifications first. Having the ability to add multiple languages doesn’t mean you have the content for them. Too many of my clients have insisted on multilingual support and yet never used it because they neglected to consider how they were going to get their content translated or pay for it.

Conclusion

Consideration of features is an important part of the process of selecting a CMS, but it is not everything. It is also important to consider issues such as licensing, support, accessibility, security, training and much more.

I leave you with a word of warning: don’t let your list of requirements become a wish list. Keep your requirements to a minimum, but at the same time keep an eye on the future. It’s a fine line to walk. On the one hand, you don’t want to pay for functionality you will never use. On the other, you don’t want to be stuck with a content management system that no longer meets your needs.

Read More

Content Management System (CMS)

Content management system (CMS) can be defined as a system used to organize and create documents and other content. In terms of web applications a CMS is used for managing websites and web content which in many cases requires a backend system for editing and creating documents.

There are several types of content management systems available:

• Web Content Management System (W-CMS) assists an organization in automating various aspects of web (publishing newsletters).
• Transactional content management system (T-CMS) assists an organization to manage e-commerce transactions (changing the pricing structure of your product range).
• Integrated content management system (I-CMS) assist an organization in managing enterprise documents and content.
•  Publications management system (P-CMS) assists an organization in managing the publications (manuals, books, help, guidelines, references) content life cycle.
• Learning management system (L-CMS) assists an organization in managing the web-based learning content life cycle. See also managed learning environment.

To implement a CMS requires a server to run the system, Additional requirements are needed to store the content that has been created, and a content management application to handle the user interaction.

In web based application these systems mostly rely on systems developed for the client by the web development company (proprietary solution), which implies that it’s limited in scope and very specific to the requirements of the user.

The next couple of solutions described in this document are based on commercial or open-source solutions.

The first one is Microsoft Content Management Server 2002. Powered by .NET–connected technology, Microsoft Content Management Server 2002 enables companies to build quickly, and efficiently deploy and maintain content-rich Web sites. By streamlining the Web publishing process, Content Management Server can reduce the need for costly site maintenance, empowering users to manage their own content. This in turn enables organizations to reduce the cost of online communication while increasing productivity by providing:

    * A comprehensive solution for managing Web content.
    * Faster time to deploy and lower total cost of ownership.

   

Content Management Server 2002 also integrates bleeding-edge internet technologies like XML and Web-services, extending the functionality of your website. Being a more generalized solution it also proves more costly than proprietary solution.

Open-source solution mainly focus on using PHP, as it provides a server side scripting language to manage the dynamic content of websites.

One such solution is PostNuke. PostNuke is a free, open source content management system released under the GNU General Public License. The PostNuke project was started because some PHP-Nuke users believed there should be a more open development environment. They felt the only way this could be done was to develop their own fork of the PHP-Nuke code. PostNuke is now a separate project sharing very little code (if any) with the original project.

Another solution is Mambo (formerly named Mambo Open Source or MOS) which is an open source content management system (CMS) for creating and managing websites through a simple web interface. It has attracted many users due to its ease of use. Mambo also includes more advanced features such as page caching to improve performance on busy sites, advanced templating techniques, and a fairly robust API. Mambo can provide RSS feeds, printable versions of pages, news flashes, blogs, forums, polls, calendars, website searching, language internationalization, and other possibilities.

Mambo won the Best Free Software Project of the Year from UK magazine Linux Format in 2004 and the Best Open Source Solution award from the editors of LinuxWorld Magazine in 2005.

To summarize the market for content management systems remains fragmented, with many open-source and proprietary solutions available. As we all know, managing a dynamic Web site can turn to a real nightmare. Make sure that your requirements are met when choosing a solution. Whether it is a simple freeware product or a complex system that requiring a substantial investment in infrastructure and maintenance.

Read More