I've been using Foundation 4 (and jumping into 5 now) for the past 6 months or so and I've created a couple responsive products and used it as a test to learn and work with SASS/Compass.
I've got a request from a client for a simple, static site - and I'm wondering if anyone who works with Foundation regularly had any advice on whether they are using foundation to create small/non-responsive sites with SASS/Compass or if they went another way with a framework.
Simple blog + 5 static pages for a small company.
Considering it is a static, simple blog site, you could use Jekyll with GitHub Pages. All you'd need is an account on GitHub now that they let you use a custom domain. No hosting required. Foundation would work too although I prefer Semantic UI.
Related
I has created eshop in shopify and I want to add a functionality ( with the framework .net ) in shopify but I don't know how....
I searched on the internet but I didn't find anything just I found this link from the ShopifySharp github but I didn't understand how to use it.
Who can help me?
https://github.com/nozzlegear/ShopifySharp
There are several possible ways to add functionalities to a Shopify shop depending on what you want to do.
They range from editing your shop's theme (mostly for simple needs) using html and/or js and/or and/or css and/or the liquid templating language (be careful though that any theme update may override your edits), to developing and hosting a custom app that would interact with your shop via a set of APIs (for more complex needs). Both techniques require a certain level of expertise (especially the later). See this very complete blog article for more info about how to build a Shopify app.
Basically you can build an app using any language and framework. The repo you found on Github looks like a C# SDK implementation of Shopify API. You are free to structure your app as you want provided you authenticate and communicate with Shopify using the possibilities offered by the API.
Our company is aiming to build an eLearning Website, we are a team of developers and our boss is suggesting using WordPress for it. We are experienced in building web apps using Codeigniter and Laravel.
I already know that we can build any type of web app using WordPress, but my questions is that is it appropriate using WordPress for building it, in terms of ease in teamwork, time, customization, easiness or anything else which you may suggest compared to usign Codeigniter or Laravel?
Yes definitely Wordpress would be a great platform to work in. Since it has extended its wings from a normal CMS to ecommerce, social networking and much more to come.
And about developing the eLearning site yes it would be definitely magnificent to develop it in wordpress as there could be some plugins for it or else you can develop one with ease.
Benefits of Working in Wordpress:
Large number of community members around to help you.
Your website will be most search engine friendly with it.
Really takes less time to develop any application because most of things are in built and you can also modify them to match your requirements.
Installation and migration is effortless.
It absolutely is suitable. There's several advantages:
Prototype can be developed in a number of days
Great for SEO since it's also a blogging platform. You won't have to code SEO friendly CMS by hand.
Possible to have a website front end that can compliment the webapp front end
JSON API is already done for you.
Lots of people are proficient with wordpress so it's not difficult to find staff further down the track
It can use a responsive design straight out the box
The JSON API can work with HTML5 mobile app API's like cordova and jquerymobile and onsen.
I only know Wordpress and have started to seek another alternative framework, Zend. I have heard hearsay that Zend is better than other frameworks. If you are "a serious coder", or try to act like one, you need to use it for building your web app.
Some say Zend is better but it is subjective. It is fast and secure but nobody has given a reason or at least compared it with with Wordpress.
Ultimate question : Does Zend have themes or plugins just like Wordpress ?
Any hint will be helpful
edit. maybe it's stupid, but it's a question. if you don't like it, or you feel it's offensive then down-vote. I don't mind ;). No hard feelings
You're comparing apples and oranges. Wordpress is not a framework, it's a publishing tool. The only thing you can do with Wordpress is make blogs.
A framework is a set of code that provides you with tools to build things. Zend Framework is a web framework that lets you build web applications. In fact, you could build Wordpress using Zend Framework (and it would probably be way better than its current sad design). You could build any other kind of site with Zend Framework. What Zend doesn't do is provide you with a bunch of pre-built web pages and templates and content management systems... those are all publishing tools (which you could build with a framework).
In short, you can't build a web app with Wordpress, since it's not a framework, and Zend doesn't have themes because it's a coding tool.
You are asking the difference between Ferrari and the tomato. Both are red, but…
Zend Framework is a Framework
Wordpress is a Blog software
You may write app like Wordpress using ZF, but not vice versa.
Wordpress is a content management system. It is much more specialized than Zend, which is a generic application framework.
You could build a cms with Zend for example. But you would have to build it from the ground.
I dissagree that Wordpress is not a framework. As a developer you can develop plugins into wordpress that can do some pretty neat things. Okay, you may say that wordpress is not a framework itself, but it does provide a development framework that allows developers to tap into. True it started life as blogging software, but to limit wordpress to only blogs is not doing wordpress the justice it deserves.
Zend_Framework on the other hand is completely different to wordpress. Zend_Framework will help your web development, but it wont do it for you. Where wordpress will work as a content management system/blog out of the box leaving the developer with a plugin framework to allow you to build custom modules and code that will run within wordpress, Zend_Framework will expect you to build everything from scratch. Sure it will provide some helper classes to help you along the way, but its up to the developer to pretty much write their entire application from scratch using Zend tools.
Personally speaking if you want complete and utter control over your entire application, and want to do everything from scratch with some help from Zend, then Zend_Framework is a tool you might want to investigate. If however you just want a website with a little customisation, then wordpress is a very good tool for that.
But the two dont compare side by side, they are different solutions for different problems.
Zend is an application framework. WordPress is a buggy blog manager. If you don't know the difference, then you probably have no reason to use Zend.
There appears to be a project called Zendpress to create a Wordpress-like blog platform built on Zend Framework. Strikes me as a great idea, though at present, there doesn't seem to be any significant activity there.
If you are a coder you can use Wordpress to build any web apps easily. Zend framework is the old fashion way to build web based apps. To this date, Wordpress is getting more powerful and flexible which you can use on any web developments. It is not only a CMS.
A friend of mine really likes using Joomla as a base for his websites. He also likes the power that Asp.Net has and can code in VB.Net.
He wants to use Joomla as the "Master Page" and Asp.Net/VB.Net/SQL Server to handle the main business logic of the application. He is planning on using the Joomla Wrapper Module (an IFrame, joomla modules) to integrate the ASP.Net into the Joomla website.
Joomla will be able to handle the security (users,roles,registration), menu (based on roles), static content (e.g. About Us page) and it will pass an Encrypted Username & Password to the Asp.Net web page (example here).
The goal of the website is to allow users to register & subscribe to a (free or paid) service where they will be able to customize content and download it as a file.
What disadvantages are there when doing this? Are there work arounds?
Some issues that I can think of are:
Links clicked in an IFrame won't change the browser's url which means that you can't bookmark pages and they aren't in the browsers history.
If Asp.Net has to know the users/roles (which is very likely) then it would have to access the Joomla database or keep its own user table which will have to be in sync with Joomla's users.
EDIT:
I would never build a new website this way, but I was looking for concrete points to convince my friend that using Joomla and Asp.Net together isn't a good idea.
I believe your friend's idea is fine. Both platforms have strong points. Joomla is a mature open source CMS platform that has an enormous amount of community contributed components and it is easy to use which makes it appealing. But I can also see instances where you may want to include ASP.Net functionality in certain scenarios. I have had clients who use Joomla but wanted an app I have written in .Net and it did not make sense to spend the time or money to rewrite it in PHP and MySql. The two can be integrated securely. I wish your friend luck in his endeavors.
I don't see what advantage you get from using Joomla when the app is ASP.net (nor the advantage of coding an ASP.net app when the framework uses PHP/MySQL).
I'm not convinced the security is tight because you can open iframes and bypass the Joomla security. Then you talk about passing username/password to the iframe - but now you need to validate this again through the ASP.net app.
I once coded an app in raw PHP and included it in a Joomla site using iframes. I realized fairly quickly that there was basically no security because the raw PHP had no knowledge of Joomla (although the app was not visible to site visitors and only known about by admin). I quickly recoded it into a built-in component.
To me, this sounds like you're reinventing the wheel on both sides of the app. If you want to use Joomla, either learn how to make components (it's pretty simple) and do it in PHP, or hire someone to do it for you ;).
If PHP is not your strong point, then use a full ASP.net site, perhaps with a CMS as GmonC suggested. Even creating your own basic CMS with some pre-built components (e.g. Telerik) would probably be quicker than integrating PHP and ASP.
Seriously, IMHO, if you're not going to integrate some legacy system or isn't doing this kind of "integration" development as an "experiment" to learn something - in a summarized way, if you just want to have your work done, I think the description you provided inserts a lot of complexity and overhead that aren't needed in the first place.
This added complexity of two completely different ecosystems is a disadvantage to what should be just simpler. I really believe you should try to use Joomla or other CMS written in .net like dotnetnuke (or build your own) instead of this configuration.
If you add more information about what are the goals and objectives of this project, my opinion may change. Until them, I keep my opinion of simplicity.
The time and effort you are going to go through to use Joomla is going to far outweight what it would take to just get some other CMS that was designed for .NET.
Stop over-engineering yourself into a midlife crisis.
Also, Joomla? Seriously? Joomla?
me too don't get any advantages for joomla, it's big system and it just as good as wordpress for regular projects, just wordpress is much simplier. joomla has no good documentation to learn and hard to extend.
I am developing a site (ASP.Net based) that, besides other features enables the users to blog as well. I am thinking of integrating BlogEngine.Net to my portal.
From whatever little I have analyzed, integrating at presentation layer will be far more challenging in comparison to doing so at business layer. That means (I guess) I will have to use the BlogEngine.Core.dll in my application.
I am looking for some sort of approval from the community, complimented with suggested do's and dont's. BTW, I find the business layer a bit intimidating (complex) as I want some basic & necessary features only.
you can check out http://www.ajaymatharu.com/integrating-blogengine-into-an-existing-site/
I recently did this for a client - note how I styled the blog to fit the main site design:
http://www.homenetdirect.com/
This was an ASP.NET 3.5 Web Application Project with master pages. I took one of the basic themes from BlogEngine that resembled what I was trying to get lookwise. Then I had all the elements that needed to be styled. Do the CSS gradually starting from the main container and work your way in (use Firefox dev toolbar). One more thing: I had to set up a subdomain for the blog - contrary to what a lot of people say, this will not hurt your SEO. SEO starts and ends with good content.
EDIT:
Creating themes for BlogEngine (Al Nyveldt's tutorials are worth watching):
http://www.nyveldt.com/blog/post/BlogEngineNET-Creating-Themes-Webcast.aspx
I integrated BlogEngine.NET 1.4 on my website. The result is exactly ONE web application (not a web site). However, the task wasn't an easy one as I had to change the source code of both the presentation layer and the core DLL to fit my needs. Now there's already version 1.6 and I guess, I'm gonna have to do same work again some time.