Q&A

  • Written by Fork CMS on Wednesday 13 October 2010
  • 4 comments

Hi everyone. Thanks for the compliments and critiques. We're working hard to iron out the reported bugs. There's a few questions that keep popping up, so I thought I'd summarize the answers in a blog post.

Q: Given that the Fork CMS codebase is now open source, doesn't that make it less secure?

A: We don't believe in security by obscurity. No one knowing the code doesn't make it secure code. To the contrary, we believe by open sourcing Fork is going to become more secure. We're getting feedback from a lot of different users, with different (server) setups, who are going to do crazy things we never thought of.

Q: Is there an architecture to plug in our own modules?

A: Fork CMS is written as a modular system. The database model and directory structure is specifically architectured for module development. We're working on a system that makes custom modules installable in an easier way, so you can share your modules with the community (akin to installing Wordpress plugins).

Q: Why is the code so heavily commented?

A: We write a lot of comments, yes. When you're used to writing comments for everything, you're not going to forget when you're doing something funky code-wise. We also think new developers can learn a lot about the code by reading it: commenting helps there.

Q: Why your own CMS? Why not work on improving existing CMSes?

A: We built Fork, or should I say, we're building Fork — it's a continous development thing — with one vision: to build a very usable CMS that would enable people to manage their sites in great detail. We're not designer nor developer focused: we are end-user focused. You (as a dev/designer) should be able to hand off a website and know that whoever needs to manage the content can do so without external help. Without the need to call the web agency every few days because they couldn't change this or that. Without the developer having to hack in an endless flurry of feature requests.

That said, we're designers and developers ourselves, so we're also focusing on making it easy to design and develop for Fork CMS. Templates should be free of backend logic; we want an easy way to theme websites; we want to be able to create forms quickly; we want multi language support. We want all of this and more.

So that's why we built our own system.

If you have any other questions, please leave them in the comments - we'll discuss it there or write a second Q&A post. And if you haven't done so, download the Fork CMS public beta and give it a try!

Comments

CosmicD wrote 8 years ago

I think I found the right cms for my website that has been put off all too long, although I bump against a few things because I don't know code:

* Will it ever be possible for the user to manipulate the titlebar in any way without having to know code ? In an wysiwyg manner ?

* will it be possible to configure the colors of the site via visual design example ?, add all sorts of background images (fixed or tiled or whatever) ?

* Will it possible to manipulate site margins in a visual way ?

thx

Wolfr wrote 8 years ago

The current version of Fork CMS requires a bit of designer and developer knowledge to set up.

You can create your own theme and templates, but to be honest, without knowing HTML and/or CSS you're not going to get very far.

In the future, we're aiming to have downloadable themes so people without code knowledge can set up a website and manage it without ever having to dive in the code.

Pieter wrote 8 years ago

I see there are quiet a lot of JS files getting included (7 js files or almost 100k in total). Isn't it possible to minify and merge these to just a few? jQuery is being loaded twice. You could also load the jQuery UI from the Google libraries api. That will speed sites up too as loading parallel.

Nice work. I'll follow the development.

Tijs wrote 8 years ago

@CosmicD:

* What do you mean by manipulating the titlebar? You can alter the title in the SEO-tab when editing a page.

* Configuring a theme's colors won't be able in the near future. And as Wolfr said in the future their will be themes for download.

@Pieter:

The double loading of jQuery is a mistake. As you can see, JS-added by a module are minified so filesize is reduced. If you look at the headers you will see they expire-header is set. If you have caching enable you will see almost everything can be loaded from cache.

But we will look to implement a general minifier, but don't expect it in the near future.