Answer the question
In order to leave comments, you need to log in
Ready-made CMS or self-written?
And so the task is to make a website (blog) of one of the city companies, their occupation is training people + now they are trying to launch something like their own TV, they want to upload video clips pre-recorded in the studio on this very site.
What thoughts have been on my mind so far.
-Use a ready-made CMS, I paid attention to Livestreet as I had already worked with it before.
- write your own content management system.
and with the advent of the second thought, two questions
arose - how long will it take?
How much will it cost to develop?
I want to ask which way to choose: ready-made or your own? And a related question, choosing the second option, please answer - how long will it take? How much will it cost to develop?
Thanks in advance!
Answer the question
In order to leave comments, you need to log in
Sorry, I won’t answer all the questions, but “And so the task is to make a website (blog)” - did you watch Wordpress?
Have a look, perhaps the rest of the questions will become irrelevant.
Developing your own CMS will take a lot of time. Especially if you are alone. I think it's better to take the same Wordpress as an example and finish it if necessary.
There are blogs out of the box and in Drupal, plus a bunch of other tasty things, and that's not counting plugins
It takes a long time to develop your CMS, believe me, and it will cost much more.
I think it's better to take a ready-made CMS, and, if necessary, write your own modules for it, if you need to implement any unique idea.
I think that there is no need to reinvent the wheel, use wordpress, as written earlier, or other cms with the appropriate blogging plugins.
1. Of course, write your own - have fun.
2. How long? Infinity, because anyway, give up this worthless occupation.
3. Of the ready-made CMS, Bitrix is better. The version you need will cost 12 thousand and include as much as the above crafts do not even represent (http://www.1c-bitrix.ru/products/cms/editions/standard.php). If you arrange a partnership, then it will be 2 times cheaper. Plus, if necessary, you can expand the functionality in the right direction by improving the license. Well, it will be extremely simple to explain the choice to the authorities, because. there are incomparably many materials, support and pluses.
I recommend Composite C1 compositec1.codeplex.com - free open source system on ASP.NET (.NET 4)
Required:
- Composite C1
- blog package. Description - docs.composite.net/C1/Packages/Community/Blog.aspx. Live: community.composite.net/C1/Blog.aspx
- if desired, a Russification package for the CMS interface docs.composite.net/C1/Packages/LanguagePacks.aspx
- YouTube package - post videos on YouTube, play locally. Description: docs.composite.net/C1/Packages/CompositeMediaPackages/CompositeMediaYouTube.aspx. Live users.composite.net/C1/Videos/Pages.aspx?video=E4IuMtAUclU
Costs:
- Hosting
- Design
- replacement of the design on the site with yours.
You need to know:
- the site needs hosting with .NET 4 full trust.
- the blog is not open source, but you can completely remake it for yourself - there are XSLT + C # functions. Very easy to customize.
- the blog is not localized, but if necessary for a couple of hours of work.
IMHO:
In terms of time, if there is a work template for the evening - two.
Use the finished one, everything has been written for blogs for a long time. It is more practical to add the missing functionality in which case. Livestreet with its plugins can do a lot.
You should write your own either for learning purposes (bicycles are useful for novice developers), or if you are creating something non-standard.
I would look at what is available from the ready-made CMS (Let's say there is also a nice Movable Type), look at the source, pick it up, and make a decision.
Cons of ready-made solutions, especially young ones:
- possible damage from vulnerabilities - in LS there was a potential opportunity to steal the admin panel, for example
- dependence on some modules, for example, if I want to add another editor to the collective farm, and in the next version they introduced something new in this same editor, I get hemorrhoids (here it is necessary to control the changes somehow).
Pros - everything works right away. and fast.
If I had little time, I would write modules for the same LS. If there were a lot, I would write my own on the framework.
There was a similar question recently. I dare to copy here my answer there: “One of the most ideal questions for breeding a meaningless holivar, from which the author still does not learn anything new.”
Definitely live street and definitely do not need bicycles, if possible, just help finish the live street and rivet modules for it, they have an open source product and, as usual, there are not enough developers.
Any promising project will sooner or later be impossible to pull alone. If you need to urgently assemble a team, then how much easier it will be if the CMS is ready and known.
I know from myself, many times I had to rake tons of self-written shit in the “urgent” mode.
Joomla is undeservedly forgotten (see joomla.org ), although it is not originally a blogging engine, but installing special components easily turns the site into what you need.
Pros:
— good and simple admin panel;
— a large community, including Russian-speaking;
For extensions here: extensions.joomla.org/extensions/news-production/blog
I would like to advise you the LabCMS system , written by the user Loki3000 with his own hand. Modularity and easy customization, both front-end and back-end. The main functions are implemented, and with a competent API and quick recommendations from the author, it will not be difficult to add your functionality. I abandoned LiveStreet in favor of LabCMS. Recommend!
Well, one more stone in the garden. Watch the videos "Blogging in 20 minutes with Rails" and "Blogging in 20 minutes with Codeigniter".
Modern frameworks (including self-written ones) allow blogs to be riveted only in this way, and there is no need to cut off the excess, as in Drupal.
Drupal barely works on a dedicated server, Joomla too, Wordpress works average, but if you do something serious, it works slowly despite the cache, Of course, for a Wordpress blog, but for a blog with news galleries, this site is obviously not on WP or Drupal, of course, why invent , better than Drupal, not one normal site on such "Engines" does not work and do not forget about JOOMLA
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question