I will create a LMS site. But I don't know Is it possible in drupal? or in Joomla?
I want only these system core, And I don't need to a portal (I need to some page with my special theme, for admin, teachers and students and I don't need to these CMS pages).
Can I do my idea with Drupal? or with Joomla? Or I must start a new project from base??
(Sorry for my bad English)
Thanks ...
What do you need from the LMS and what CMS features do you need? Drupal or Joomla may be a stretch if you need full SCORM functionality and/or sophisticated LMS features. Moodle may be a better fit in that case.
It's very possible in either Drupal or Joomla. I personally like Drupal more than Joomla, and would encourage you to look in that direction. There is an actual tool called JoomlaLMS, which would probably give you a better out of the box solution, but you will have to shell out quite a bit of cash.
If you're willing to spend quite a bit of time building your own system in Drupal, you could have a very good free solution. You could also end up with a huge mess if you don't know your way around Drupal.
I'd go with Joomla. The reason is that Joomla is a much bigger project with many more people involved, so developers build many more addons, as Jimmy said. I was able to put together an impressive website, www.shattergames.com with a very limited amount of work, just because so much has been done with Joomla. That said, why not just use Moodle?
Related
I'm trying to find a relatively simple solution to deploy a website that allows someone to select an orphan and donate to that orphan. Each orphan would be a part of a orphanage...
I looked into Drupal and Ubercart but I didn't know enough about it at the time... felt kinda lost. Could someone point in the right direction? I'd like to use an open-source solution and as many pre-built modules as possible.
Definately drupal - you are right when you say drupal is a bit much to take in, but with the right links, it's not so bad
http://diasporan.net/content/drupal-and-ngos-dango-modules-and-install-profile
That's everything you need, all packaged in a nice install profile. An install profile is like a C make file, it "compiles" drupal for you for a specific use case. Google "drupal install profiles" for more info (Hint, if you see pages explaining "Drush make" you're on the right track)
This can be done in both ways.
I would do it with joomla though, in my opinion it is much more powerful than drupal, has a bigger community behind, and there are many free add-ons.
You can use hikashop as your shopping cart solution. It is is simple shopping cart solution that works very well with joomla.
I made this e-shop using joomla & hikashop recently.
Well, I'm sorry but the best way would be simple and fast with Prestashop.
See you!
Note: I like Joomla! and Drupal but when it comes to ecommerce well... Lets hope that soon prestashop can be integrated with joomla and drupal.
You can use drupal because its a very powerful cms.
The best part is that manages the database very effectively so, if in future your data size increases, then you don't have to worry about it.
The installation is very easy. just visit drupal.org.
The community of drupal is very supportive.
For about a year and a half I used Codeigniter to build my sites. Then a client begged me to build theirs in Wordpress. I soon found the joy of using a CMS (if Wordpress can be called that). So for about the last 8 months I have been using Wordpress as much as possible to buld my sites - I made the content fit the design.
Well, I began to grow very tired of the limitations of Wordpress - I needed more control and flexibility over my sites. So, I have recently started using Drupal 7 (not 6.x - I really like the admin panel).
After working with Drupal now for a little under two months - I have begun to feel like I'm using Stone Age Tools to build Space Age equipment.
So my question is: does Drupal get any better? Do you really have to use Views to display your content? Asking for help on the forums is just a shake better than asking a wall. I feel like to do anything requires a module. Why? Is one better off sticking to a framework?
"After working with Drupal now for a little under two months - I have begun to feel like I'm using Stone Age Tools to build Space Age equipment."
Well, my intiial reaction is that this is what you're going to feel like you're doing when you're working with Drupal 7, which isn't out of alpha yet. A good number of the folks who maintain modules haven't started upgrading to 7 yet, and that means that you're missing out on one of the great features of Drupal, which is it's wide and deep space of premade modules.
Try 6.
Do you need to use views to display all content? No, not at all. You can go in, create a new module, and write the sql and presentation that you want. Or you can find a module that will display things for you. Or, depending, you might be able to get the effect you want just by adjusting the theme you're using.
(As a side note, using an admin theme really pretties up the Drupal experience. I'm fond of rootcandy, although Rubik is nice too. Problem with Rubik is that it's not on drupal.org.)
The strength of Drupal is that by using modules, you don't have to re-write code that someone else has written - you can instead take that code and modify it (with hooks) to do what you want. This means you don't have to write an authentication/autherization system again - it's there in core. You don't need to write up openid handlers - it's in core. You don't need to write code to integrate with twitter directly - there's a module that contains an api that helps out. You don't have to write an xmlrpc server from scratch - you can use the services module.
You don't need to write a website from scratch. Instead, you can start with Drupal, add most of the functionality you need, and then spend your time making it fit what your client wants.
Firstly, you can install the Admin module to pretty up Drupal 6 admin. You don't have to use 7. 7 is still in alpha, by the way. Garland sucks, but, Garland is just a theme- its not 'the' admin itself. The Drupal admin can take the form of any Drupal theme, which is useful in its own right, depending on the use-case.
In Drupal, you can create content types clicking through the interface in Drupal 6 or 7. As far as I can see in WP3, you have to script it. A few clicks vs scripting, the choice for me is not hard there. The first way is a lot more efficient, and a task you can hand off to a non coder to get done.
You don't HAVE to use Views to display content.
You -can- use Views to make the display of content easier, by telling Drupal to gather data and provide a Page, Block, or Feed to display . This lets you create specific sections of content for areas of the site. Otherwise, you would have to create a node, and hijack its template, run a direct sql query yourself AND write the pager functions just to show something easy like the latest 10 "Press Releases" content type. Then, if someone added a new field to that content type, you have to update all that SQL code and display code. Views makes your life easier in that respect. In minutes you can flesh out site sections and arrange content in a myriad of ways. In Wordpress, this method of arranging content without functionality of Views is/was a modern nightmare and a reason I do not want to use it at all unless its a blog and nothing more.
The Drupal Support Forum is tricky. Not all modules are as active as say, Views or Pathauto (being two of the most popular modules). However, SO is also at your disposal. I answer a lot of Drupal questions here. The trick to the Forum there is you have to ask it in the right spot. True, sometimes you may have to wait a few days to get an answer, then again no one -owes- you an answer for a free product. Thats the nature of open source.
Every developer has their favorite modules to use with Drupal, and more often than not, its the same 20 or so modules. It depends on what you are doing, what you are trying to implement. It's not that 'everything needs a module' its that Drupal is such a vanilla install because Drupal does not want to assume your purpose nor overwhelm with options. The UX is something they are trying to improve anyway, and popular modules are making their way into core.
Well, I began to grow very tired of
the limitations of Wordpress - I
needed more control and flexibility
over my sites. So... I have recently
started using Drupal 7
Why not go back to CI? Drupal certainly has it's strengths, but I don't think Drupal will give you any more "control and flexibility" than Wordpress.
If the standard modules/plugins, themes/templates, from WP, Drupal, or Joomla, fill your needs, then using a CMS can be a lot faster than building a site from scratch. But, if those CMSs do not fill your needs, you could find yourself "fighting the framework" and never really getting what you want.
You're just coming out from WordPress, which has great support and is relatively easy to extend to overcome what you call its limitations, if you know basic PHP, HTML, CSS & JavaScript. Every framework has its own potential/limitations.
As a user of WordPress my humble opinion is that you should have stayed with it.
As of you last question, It depends, to stick with one and only one framework has its advantages and disadvantages, the best of all is that you get to know it very well and eventually learn how to extended it. The bad part is that very often frameworks lose popularity and you are left to you own without an active user community and support.
Regards.
All of the popular CMS products (I'd maybe add Expression Engine to the mix) are great for 80% of what you want to accomplish and a huge pain to handle the other 20%.
That's just the nature of the beast.
On the plus side, it's OS so there's lots of people hacking away at it just like you which opens up the potential for someone else already having invented the wheel.
And with bulky enterprise CM solutions like SharePoint I find that you have to reverse the equation to 20/80 (ugh!).
If you're discouraged with Drupal and prefer to stick with WP, WordPress has many thousands of plugins, including ones that can overcome the limitations you're running into and make WP behave more like a normal CMS.
Just do a Google search for "top Wordpress CMS plugins." There's a lot of articles out there that can recommend ways to get WP to do exactly what you want.
I am setting up a web site for a football club and I am wondering which CMS to use.
I am a developer but I am doing this as a favour to a friend and would rather grab something with modules in it (registration, events, calendar, etc.) already. I need to be able to customise it but I had a look around and Wordpress looks like a blogging tool. I am wondering if anyone has experience with the above or any others and if you could shed some light. Thanks
The Major benefit of DotNetNuke is that you will be programming in .Net with all the tools that go with that. And the db is of course, SQL Server.
So if you are a MS guy, then DNN is a good option.
Day Of DotNetNuke is on in Europe this Friday and we will some slides which demonstrate how to use Telerik and sqlDataSource to build modules in minutes. These use Telerik grids to give you CRUD functionality in two simple files. Drop in to Paris if you are free, otherwise, visit the site next week and you can get the slides and some sample code, or else contact me and I will send them to you,
PS. Not sure why, but you will enjoy working on DNN.
good luck and enjoy.
Mark
I can't speak to the current relative merits of the different tools, as it's been a couple of years since I did a comparative evaluation of Drupal, Joomla, WordPress (and 40+ others).
But, I can testify that Drupal would be a good solution for almost any club website.
Out of the box - or with the installation of a commonly used module or three - you could set up:
Recent News
Upcoming events (Calendar)
Blogs (for the club President, Treasurer, other officers, team captains, etc etc)
Media such as podcasts, videos, etc
Of course, all this is optional. There's heaps of documentation online at http://www.drupal.org covering all this kind of thing.
The key point to take away is this: With Drupal, the challenge your friend will face with the website is "what to say" not "How to make it work".
It depends how well-versed you are in a particular CMS for example Joomal or Drupal or some other. If you can customize the things easily and be able to modify the CMS as per your needs, you should go with that one as both Joomla and Drupal have big list of extensions to their name. You should have advanced programming concepts especially OOP when it comes to customizing the CMS. The other option is to create everything from scratch on your own. In the end, I would prefer Joomla over Drupal.
If you have no experience at all with any CMS, I suggest you Joomla to start with. It is easier to learn and probably enough to manage a football club sites. It is also easier setting a Calendar, Event System and Photo Gallery. Drupal is more flexible, it has great user permission control, but it is a bit more complex.
Liferay Portal also has the features you need.
Quick and easy to set up with registration, Calendar ootb. it will be easy for your friend to admin in the future
I would like to know how feasible is Joomla or Drupal towards a website development which has around 80 web pages? I'm a part time website designer who does a bit of server end development as well using PHP and Python/Django. However, i have never attempted developing a website of this scale. There is a lot of static content on this website and some user interactions using JS/JQuery. The only PHP used would be in contact forms. Rest would be only HTML/CSS/JS. As there is lot of text information to be coded into the web pages i would like to know how Joomla or Drupal would help me?
When you use Content Management Systems, you don't need to use code to make content, that is what the CMS is for. If your site is purely static content with a contact form, Drupal might not be the best choice unless.
You already know Drupal.
You want to learn how to make sites with Drupal.
Drupal is very powerful, it's extremely flexible and a great framework. But it comes with a cost, it's more difficult to learn. If you just want to make a site with 80 or more pages and a contact form, you will most likely be better of with Wordpress. It's more simple and userfriendly. It's not a great development framework like Drupal, but if you only need a contact form and content, you wont need a development framework anyways.
If you're not used to using a CMS, both of these options will be quite a culture shock. In my experience, Joomla is slightly easier to learn than Drupal, but each are a LOT more work than hand-coding a bunch of pages.
Who will be updating the content, if at all? This should be a major factor in choosing a CMS, especially for a small, relatively static site. If the answer is "you" or "one person who can be trained" then you might want to think about keeping it hand-coded (making use of SSI or similar, where appropriate).
Alternatively, if you want a lightweight CMS, take a look at something like kirby or perch, both of which are excellent CMSs for small sites, with relatively low learning curves.
Drupal is pretty powerfull when it comes to content management content management. 80 pages is really nothing. You can sort everything easily with built in Taxonomy-module(used for categorys, tagging, ...) and even create own displays with the Views module. Because of CCK, you can make as many different content types you want, with all kinds of input options(wysiwig text, select lists, checkboxes, files, ...). For the contact form you just use the built in one or use the Webform-module.
I dout you'll have to do any coding for this, but beware, drupal is quite big and you might take some time to understand how it works and how to install. Once done however, it's all very smooth :)
Haven't worked with Joomla yet, can't help you there, but you might wanna google "drupal vs joomla" or similiar, there's plenty of articles. From what I've read, Drupal can do more, but Joomla' easier to learn.
It totaly depends on what functionality you want to have. If you are interested in multimedia or more complex functionality then Joomla is a better option. Thus when it comes to build up a complex and robust website full of features and functionality, you should go with Drupal. Go through this blog to get clear information: http://hirejoomlaprogrammer.blogspot.in/2012/07/joomla-drupal-or-wordpress-which-cms-to.html
I'm going to be moving my website to a CMS in the coming months I'd I need some help on choosing an appropriate CMS. Many of the websites I've seen tend to say "use Drupal, hands down". However, my website truly doesn't have a need for commenting or community features. Its pages will need to be modified occasionally, but not extensively. My website will also consist of many programs, each with their own sub-pages and menus.
There are probably 25 people that will need access to the content on my website and will need the ability to update it.
I do like the idea of being able to tag and categorize the content, and the modular aspect of Drupal but is it really right for my website? If not, which CMS may fit my needs better?
It sounds like Drupal would be an excellent solution to your company's needs. I used to recommend WordPress for smaller, single-blog type sites, but now, even for those, I recommend Drupal because you can start small and scale up as your needs grow. It has a very dedicated community and there is a module for just about any need you may have.
I would agree with Drupal. The thing about Drupal is that you start out very small and add on as you need things. There is a ton of documentation, it is well coded, always being expanded on, good forum support, and free. It's the easiest to install, most problem free, and most maintainable CMS system I've seen so far.
You can turn Drupal commenting off with the press of a button, and if/when you decide to add onto your website, perhaps you want an ad rotator, more extensive user permissions, etc, etc, it is all already developed for you and ready to go.
I am not sure if Wordpress supports multiple users on a site.
The smallest you can go for a CMS is something like 10kCMS or the more popular TinyMCE
If it is something small I will go with WordPress as it is easily themed and extensible. There are a lot of community plugins and support. Their documentation is also fairly simple as they don't have a thousand of functions and stuff you need to remember and understand. With some creativity the basic functionality of WordPress is sufficient to solve almost all problems that might arise in small to mid-size website.
I also like Drupal, but you may consider Umbraco as well. http://umbraco.org/ I'd use Umbraco over Drupal if your team is stronger in .Net than PHP. (Really, I think that's a larger concern - what are your organization's strengths? Play to suit them. You are making a decision that will pave the way for many developers besides yourself, and business decisions of your company.) Both are extendable and open source so you can write your own modules/components to customize. It may be cleaner to import into Drupal tables than Umbraco, since it goes down to xslt files. (EDIT: This looks to be no longer the case in the new version - http://umbracohosting.com/umbraco-4---get-excited/one-cms-any-database) From a front end dev perspective, both offer great control of the final output.
From working on legacy stuff a lot, you may end up hiring interns to do the gruntwork. There's bound to be tons of inline tables and all sorts of un-reusable code in there, it may be easier to scrape the content manually and start w/clean markup for the content portions.