Firstpage
Firstpage

We help you communicate your brand with good visual

Selanjutnya

Tutup

Bisnis

Mau Bikin Website? Pastikan Kamu Tidak Salah Pilih

14 September 2018   12:24 Diperbarui: 14 September 2018   13:27 307 0 0

Ketika seseorang ingin membuat sebuah website pada umumnya terdapat 2 jenis website melalui proses pembuatannya, yaitu : Menggunakan Prebuilt CMS (Wordpress) atau menulis baris kode dari awal menggunakan PHP Framework (Codeigniter, Laravel, Etc). Pemangku kepentingan non-teknologi terkadang tidak begitu yakin manakah pilihan yang tepat.

Prebuilt CMS mungkin tampak menghemat uang / waktu dan alat yang lebih jelas untuk menyelesaikan tugas bisnis mereka. Namun, kapankah saat yang tepat untuk menggunakan Prebuilt CMS atau PHP Framework ? Mari kita lihat perbandingan WordPress sebagai CMS yang paling banyak digunakan dengan Codeigniter.

KEUNGGULAN WORDPRESS

Sebenarnya, hanya ada satu kasus di mana menggunakan WordPress dianggap sebagai keputusan bisnis yang baik : jika memenuhi spesifikasi persyaratan kebutuhan dari proyek web yang diberikan.

Secara umum, WordPress biasanya adalah pilihan no.1 jika:

  1. Proyek ini termasuk dalam kategori portal berbasis konten seperti blog / surat kabar.
    Pasar telah menyediakan plugin WordPress dengan kualitas / keamanan dan fungsionalitas yang diperlukan untuk memenuhi persyaratan perangkat lunak.
  2. Pendiri startup ingin menguji pasar dan membuat versi pertama dari situs web dengan cepat / murah dengan fungsionalitas yang dilucuti. Dalam hal ini, WordPress bisa bermanfaat sebagai prototipe dan platform untuk produk yang layak minimal.
  3. Beberapa manajer non-teknologi percaya WordPress lebih baik daripada kerangka kerja apapun karena WordPress sebagai CMS pra-dibangun memiliki panel admin yang hebat (antarmuka yang user-friendly), sehingga setiap anggota staf non-teknologi dapat memperbarui situs web tanpa pengembang. Yang benar adalah jika perlu memiliki panel admin seperti WordPress, maka akan mudah dikembangkan dengan PHP Framework. Juga tidak menjadi masalah untuk menemukan pengembang PHP Framework cukup luas.

KEAMANAN WORDPRESS

Saat membuat keputusan tentang penggunaan WordPress, kerentanan keamanan dari inti WordPress dan plugin harus dipertimbangkan. Ikutilah gambaran singkat tentang kasus yang dikenal secara luas:

Sangat penting untuk memilih plugin yang aman dalam menggunakan wordpress, tidak hanya itu Website harus di update cukup sering ( ketika ada update) dengan tujuan menjaga kode tetap up-to-date sehingga kemanan lebih terjamin. Namun tingkat update dapat dilakukan 1 minggu / 2 minggu / 1 bulan sekali.

BATASAN WORDPRESS

Ada batasan kustomisasi yang disertakan dengan sistem yang dibangun dengan WordPress CMS. Jika proyek berbasis WordPress berkembang (pengguna yang lebih terdaftar, lebih banyak operasi per detik, dll.), Pada titik tertentu tidak ada pilihan selain menciptakannya kembali dengan PHP Framework (seperti Codeigniter atau Laravel) atau (jika mungkin) untuk migrasikan situs web ke kerangka kerja Codeigniter.

Berikut merupakan kasus yang diambil di beberapa forum :

Gizamo: Asking a web developer to modify a CMS can significantly increase developmental costs. It may also create complications in core functionalities, such as updating, theming, etc. And, it can require a darn good programmer, depending on the platform (which will further increase the costs).

Developer: I have been developing with WordPress for a while now. I have been using WordPress outside of its element and been developing web application that aren't necessarily blogs. I loved all the functions they have, and the security it provides.  But I'm starting to work with more complex applications, applications that are starting to not fit in the WordPress model. I need to find a framework that's similar to WordPress in the developmental aspect. I just need a powerful framework that is lightweight and well documented. So I need a framework that can handle user management, template engine, security updates, and has good documentation for development.

Ekaitzastiz: I have done a lot of things with WordPress: custom themes, widgets, plugins... And for news web and blog web portfolio, it was enough. However, Laravel is a framework that can be used to do exactly what you want and how you want; you can do a custom backend, a REST API, a SPA app, an intranet, a CRM... Big effort is needed in WordPress to do big changes like that. WordPress is not as customizable as an app that you build from scratch with a custom design and focusing on your needs. It's not as flexible when changing anything. Moreover, very important, is the weakness of most plugins and widgets in WordPress: they aren't tested with PHPUnit, or aren't build applying TDD.

Masiorama: After months developing and using WordPress-based solutions for my clients I noticed that the start of every single project was very fast (easy to install, lots of materials available for free or cheap) and satisfactory enough, but the hell arrived each time there were some more-than-little modifications (logics and design). Using a framework with a pattern like MVC (I use Yii) may be more difficult at the beginning, but to write, debug, and organize your code is far more fluid and satisfactory, on the long run. Even a module (CMS) can be easily extended or rewritten with lesser effort than packed CMS solutions like WordPress.

Steven Richardson: I just built the whole thing in Laravel, including the blog. I got my app response time down to 35ms with a total page load time of 1.02s from the original 4.3s.  I believe if you can build something that will perform faster, even on a mobile connection over a bloated CMS then build it. Your readers and users will thank you for it.

Milan Lesichkov: I have moved several slow WordPress sites to Laravel. Speed improvement is about 700%. 10s (WordPress) - 1.5 s. (Laravel).

Gravy: I am moving my website from WordPress to Laravel as the website has moved away from being a blog and requires more enterprise and custom functionality. The website has outgrown WordPress.

Raffworks: I decided to consider moving away from WordPress and into using a lightweight framework for building my sites and web apps. I went for CodeIgniter 2.1.3, but got a surprise insight into Laravel as I was doing so, and have decided to go for that instead.

Milan Lesichkov: My experience starting with WP and moving it later to Laravel was a nightmare. I have moved many web sites away from WordPress to Laravel. The benefits are great security, speed improvements, full flexibility of what can be done, development speed, great model layer for working with databases, and many more. So my advice, stay away from WordPress. It was meant to be a simple blogging engine that is "hacked" to do much more. Everything in WordPress is a "hack" but most of all, the database. The "blog post" is a post, "image" is a post, "page" is a post and what-ever-you-think-of is a post. All additional data is added in metas, which have to be joined multiple times to get related data. Once your database grows even just a little bit, it gets slow as a turtle. Development speed. It takes me 5--10 times less time to do the same features with Laravel than WordPress. Every time you develop for WordPress you have to "hack" something to get it working. With Laravel it's all modular and reusable. For instance, what if you want to have a blog on your website? Well it took me about 2 days to do a blogging module for Laravel---fully flexible, that can be added anywhere, reused many times after this.

HALAMAN :
  1. 1
  2. 2