I need a intranet portal for a Repair factory in which 100 Technician worked.
The main purpose of this portal is "sharing technical information (like technical bulletins etc)".
I also create a simple website/portal with HTML,Javascript. Which is running sucessfully.
But Now we need a Blog like site in which Technician can share own experience/knowledge with other. for this requirement i tried with Joomla,wordpress, drupal etc.
firstly suggest me which platform is best? i have beginning knowledge of PHP, JavaScript and JQuery.
requirement:
Technician can post a article within one or more defined categaries.(like model,level of information,Electrical or mechnical etc.)
After submitting articles, it sent to the Technical Specialist or Technical Editor for approval.
after approved it is published to Blog with ranting,commenting option.
Which theme,plug-in is suitable?
Take a look at Plone (http://plone.org/), I think it fits perfectly for your needs.
Plone lets non-technical people create
and maintain information for a public
website or an intranet using only a
web browser. Plone is easy to
understand and use — allowing users to
be productive in just half an
hour — yet offers a wealth of
community-developed add-ons and
extensibility to keep meeting your
needs for years to come. "
For those looking these days and who want / need WordPress you can use Woffice (https://woffice.io/) or Thrive. Both have all these features.
Related
I´m currently developing the Intranet for the company I am working for. The site is currently based on SharePoint, but I have to migrate it to Wordpress. And that´s my first developer experience with Wordpress, you just should know. Creating the theme, content and working with the WP Admin area works very well, but where I´m feeling defenseless is the permissions topic.
Generally, the whole page content is managed by the Marketing department. So, for me it is ok that they have access to WP Admin and I would use one of the predefined roles available.
But there will be also an area for the departments where specified users per department should be able to
edit the pre created page content
add subpages and edit its content (it would be nice if it can be defined which page templates can be selected by the user)
add posts for a pre created category (that should not be changeable by the user)
edit its profile and password
A whole access to WP Admin should be therefore prevented.
I read much information about roles, capabilities and reviewed forums and blogs presenting potential plugins. But to be honest, I´ve lost the overview and I´m totally scared about what´s the right way to do such like this the professional way.
Is there anybody who was already in such a situation or knows a good resource where to read more?
Thanks a lot.
John
PressPermit is the tool I choosed. It covers all needs described in my question.
Note: To use all features, you need to buy a support subscription currently available for $55 a year for one site.
However, a very powerful tool and in comparison to Advanced Access Manager I tried before, it really supports permissions also for multiple roles.
If you are thinking about, use the screencasts to see if the tool cover your needs. Unfortunately, there is no trial available, but you can request an evolution wordpress installation which was setup within one day in my case. This service costs $5.
We are planning to create an asp.net website (probably mvc), that needs a cms for news items.
Our content managers and others who require to publish news have asked if they can use wordpress for content management.
Our users have different roles, and news items should be visible to certain roles, or even specific users if possible.
The reason they want wordpress is the manager's user friendliness, so if some other alternative with the same kind of user experience would be ok.
Could anyone please point me in some direction?
NOTE: I'm still doing research at the moment, so I've got nothing holding me back at this point.
There is an API plugin that has been developed to spit out information in JSON, but I have not actually implemented a site with it:
http://wordpress.org/extend/plugins/json-api/
Perhaps you could have the authors work on a wordpress install and create your app to draw content via that plugin?
I too was facing the same issue, little different. We want to have WP as CMS so that our site can take the benefit of SEO which is very easy with WP. SO we installed WP under a folder in the Main ASP.net based website. Initially there were issues, I was unable to run it. Finally managed to run it. Solution is posted here - http://www.wwwlabz.com/how-to-run-a-php-based-website-from-a-subfolder-in-asp-net-website. Hope it will help someone. Actual site where we implemented this is http://www.periproperties.com/content/.
Now I want to have specific section of WP to be accessible on my site. SO I am exploring different options and will post, if found something
Thanks.
DotNetNuke is the most popular ASP.NET based CMS (source). I am implementing my first project in it and so far I am very happy with it.
Note the free edition will not work for you since you need customizable security roles and free has a limited set of predetermined roles. You'll need the pro edition.
I don't know how similar it is to WordPress. Overall, WordPress is much more popular but of course there are platform issues with WordPress since it is Apache based and you want to create an ASP.NET website.
I'm not entirely sure how to properly ask this, so please bear with me.
I have an idea for a site I would like to build, which would basically be a site for members to create some data and have it housed in my database. I would like to offer a value-add to the site which would allow people to spin off their own website via my own "website builder" tool (probably some sort of CMS). Their website would be able to communicate with my master database to display their data.
Getting down to the crux of the topic, I'm looking for architectural advice/ideas/etc. regarding what services I could use to do this. I'm not looking a 100% automated solution, but something along these lines (which may not be completely correct, I admit):
Customer puts in an order to create their own site, using my tools.
I setup a separate domain for them, roll out the CMS foundation to the site, and the customer has full editing control of the CMS to design it however they would like.
The CMS would have some customizations so that it includes functionality to call APIs located on the master site, which would return the relevant data.
In the research I have done on SO, I've seen a lot of mentions of Umbraco which honestly looks like a good start. I'm just worried that when I go to upgrade a version, I have to deal with overwriting my custom API functionality. I'm guessing this is the nature of the beast, and requires me to accept/plan for it.
Does anyone have any thoughts about this? Some high-level starting points? Thanks!
I've been thinking about this same issue for my customers.
It is not hard to automatically roll out a stock cms such as Wordpress or Joomla. This sort of thing is done all the time by "1 click installers" that DreamHost and others have.
Including custom widgets or plugins for the CMS that can connect to your main app is also not hard.
For dns, you can use Amazon Route 53 or other DNS services that include a good api at the dns management level.
I suggest that you focus on using a CMS that is very popular (eg Wordpress or Joomla) rather than something less well known such as Umbraco. Using a more popular system will drastically reduce your training costs--remember that if you supply the CMS to your customers, then they'll also expect you to supply the support for it...
I've been adding quite a few blogs to sites and I'm wondering if it's better to add blogging software on the site or use an external blogging service. The major reason I can think of adding a blog to site is if you want to customize it later on (other than look) such as more integration with the site. If I put it on the site, I'll probably use WordPress as I'm familiar with it.
Is there any major advantage to one method or the other?
I would go with putting the blog on your website itself. This will help with a number of things:
Transparency: Your users will feel as if they are on the same website, because they in fact are. Your blog will become simply an extension to your website. On the other hand, a blogging service will most likely appear as though you are going to a completely different website.
Integration: You are able to integrate everything on your website with your blog. This includes any existing user bases, or future ones. Also, the look of your blog can match your website perfectly, much more so than with a blogging service.
Customization: You get 100% control over every single feature of your blog. If you want some new crazy feature, you can program it. Blogging services are typically much more closed than this.
The downsides will be that you have to maintain it, and any features that you want you have to put in yourself.
One of the advantages of having blog on your site is that all the content will belong to your site, which is good for search engine since it will increase your site visibility through SERP. But you will have the price to pay: installation and maintenance.
It's not cut and dried:
(Assuming this is for clients) do you have an ongoing relationship with the client and time scheduled for upgrades? Most blog software needs at least some upgrading or security patching from time to time.
Are you relying on some sort of social media network effects from these blogs? If so, you may get better mileage from a hosted product as they often promote related sites within their networks (e.g. Wordpress has the "Possibly related posts" feature).
As Brian said, integration could be an issue if you have other areas of your site that rely on logins. In that case, probably better to host it yourself.
Is there any SEO disadvantage in using a subdomain to host a blog on Wordpress or Blogger? I don't want to go to the trouble of creating a blog module for my site - I'd rather just set up a CNAME entry and point a subdomain to a free Wordpress or Blogger account. Will Google punish me for doing this by claiming that I have "duplicate content" - i.e. the intro text for each blog entry will be on my main site and the full details will be visible on Wordpress/Blogger? Is it better to incorporate the blog functionality into my main site? Are there any other potential disadvantages to this subdomain/external hosting approach using a free blog host?
There are a lot of advantages to self-hosting your blog.
You can do whatever you want with your own self-hosted blog. On Wordpress you could get banned and lose all of your content.
You can host ads or and do other commercial stuff not possible on Wordpress. (The free wordpress blog doesn't allow any advertisements other than their own ads).
Better ranking opportunity in search engines by using your own top-level domain.
You can modify your functionality at will.
It looks more professional and gives you bragging rights.
On Wordpress you may run up against bandwidth restrictions if your blog gets really popular - you won't be able to do anything about it.
Willem Obst answer makes some excellent points, but two serious accusations that are not correct. I know these are incorrect because I am part of the WordPress.com team.
Num 1. If there is a ToS issue, we work with our customers to resolve the issue. In the rare case, where a blog is suspended, the customer is still assisted with exporting their content.
Num 6.We have no bandwidth limits and never have.
Many companies use free WordPress.com for their blog. Here are some examples
http://wordpress.org/showcase/flavor/wordpresscom/
WordPress.com is also is a blogging community which gives you access to a large audience and the community features like the global tag pages.
It's a great way to get a blog going, and there is no lock in. Here is an example of a blog by some friends that started on WordPress.com and since moved to host it themselves to gain the additional flexibility Willem describes so well:
http://blog.bootuplabs.com/
Finally to the original question. It's a mixed bag.
The nay sayers to using a subdomain will focus on Google and other search engines generally treating the subdomain as it's own domain with it's own authority.
The pro subdomainers will focus on it being another opportunity for a result in Google and the search engines. As is the case for the "bootup labs" example. (Although, Google's Matt Cutts over a year ago promised this was changing.)
Unrelated to SEO, many teams use a subdomain or separate domain all together for web security reasons. You may notice that http://blog.flickr.net/ is on flickr.net instead of flickr.com primarily -- I understand -- for this reason.
No in one word
Actually a good idea. Self hosted blogs tend to have a lot integrated into them e.g autopinging
In answer to the question.... NO.
The question you asked is also a little ambiguous. Are you wanting to host your own blog ie run it on your own server under a subdomain, or are you wanting to add a CNAME entry that links to your blog.
There are benefits to both:
Running your own - Advantages:
You can control every aspect of it
You can change the design/layout as much as your coding ability can handle
If you have a fast server, your blog will be served to viewers extremely well
You can advertise on your own blog - Google Adwords/Adsense etc...
You can setup advanced analysis of traffic and see every little detail about everyone who visits your blog
You can tweak the SEO of your blog to the 'n'th degree
Running your own - Disdvantages:
Hosting a blog (especially a popular one) requires a pretty powerful web server
You have to maintain the blog and security of the blog eg. users and permissions
Dedicated Server hosting can be expensive
Hosting blogs use a lot of bandwidth
Using a third party blog - Advantages:
Generally free
No strain on your server/bandwidth
Security and permissions management is limited but managed by the host
Generally hosted blogs have an extremely user-friendly GUI
Using a third party blog - Disvantages:
Sometimes include advertising that benefits the host not your company/blog
Very limited ability to customise/edit the design of the blog
Limited control over the security and user management
Other hosts can choose to stop offering a blog hosting service
In regards to SEO and blogs:
Your blog is not going to suffer or be penalised by GOogle/Yahoo/Other search engines if you use a CNAME redirection to another host.
You will not get penalised by a search engine for duplicate content if the content is not completely duplicated on, for example if your main domain uses the title and summary of what is on your blog hosted on the subdomain.
If you adhere to the main SEO principles there is no reason why your blog would suffer on a subdomain:
Using relevant addressing methods eg. yourblog.yourdomain.com/title-of-blog-article.html
Use W3C compliant/correct XHTML/HTML/CSS code
Use appropriate and relevant META data (keywords, descriptions, titles) for the blog and the articles.
Relative linking instead of absolute linking
Hope this helped. If you have any other questions feel free to ask