In my knowledge, Deity Falcon provides ReactJS based framework to implement Headless PWA (Progressive Web App) for BigCommerce but it's Paid. Apart from this, VueStorefront seems good and is open source.
Any suggestion to use better framework with BigCommerce for a growing company to save cost but create an optimal scalable PWA frontend?
Vue Storefront founder here ;)
I just want to make few clarifications to Sean W post:
Vue Storefront is not just a community framework. It is backed by a whole company employing almost 30 people dedicated only to this project PLUS community. We recently got 1,5 mil $ funding and got backed by YCombinator so we are definitely not going anywhere :). We also have active community of more than 4000 developers actively supporting others on our Discord chat and contributing to the project. We also have the biggest amount of live shops among all mentioned frameworks. I'd risk a (slightly biased) statement that together with Next.js Commerce we are the most reliable option on the market.
The last version of Vue Storefront 1 is from a year ago but we are actively developing v2 for almost a year that gets a new minor version each month (last is from 5 days) and is aiming to support all major eCommerce platforms (currently it's Commercetools and Magento with Shopify / SFCC / BigCommerce in the making).
If I were you I'd go with either Next.js Commerce if you prefer React or Vue Storefront if you prefer Vue. Both have great communities, vibrant ecosystem and are backed by well-funded companies that are not going anywhere :)
Cheers!
Related
I have a business idea which I want to materialize for sometime .. I recently shared my idea with 2 close friends who also found it very interesting, new and doable plus the cost included for the project to start is reasonable and they have planned to invest in it. Much of the success of this project app depends on the proper marketing element out of which most of the time, you have to personally meet up with clients/vendor and make them use your application.
The idea is to connect local ecommerce (retail shops, businesses, vendors, etc.) with users/customers through a messaging app mostly similar to whatsapp. I have already started to look for a xmpp/jabber developer who can accomplish our requirements. We are expecting him to develop the app and also set-up the server requirements. Our budget lies within $3000-4000 range for the project to initiate.
I want the app to have the following aspects:
a) user friendly GUI
b) highly scalable (planning to start within my city located in south asia)
c) location sharing (want users to navigate nearby shops/vendor offering their type of goods/services)
d) have a user review feedback against vendors and an additional page for vendor profile/rating system
e) only customer - vendor chats with functionalities like camera snaps, audio recording (just like whatsapp).
f) both for ios and android
Now the whole idea outlaid, after reading lots of articles, discussion and tutorials, I have some questions (I am a non-technical person btw):
1- I believe ejabberd is the best option as compared to tigase or prosody due to high scability. Is this ok to go with or should I look at other xmpp servers?
2- Currently, I am planning to launch this application within my city (rated as worldwide no.2 as per population stats of above 25m people), should I set-up a local server with high internet bandwith and a powerful machine or should I outsource it to some xmpp hosted server in the US (as their technological infrastructure has always provided quality service).
3- Should I be worried about the developer stealing the source code or is there any effective way to minimize this risk?
4- Any ideas what other things I am missing. This is dead serious for me and I am willing to do anything to get this project on the road.
(P.S.: The idea for this app is similar to the existing app called Lookup but I am planning to add some variations to it)
Thanks and sorry for being a bit lengthy ..
Regards,
Ahmed
ejabberd is indeed likely your best bet. However, be careful about the budget. To launch a quality service in an highly competitive area you have to have a significant budget, both development and marketing, if you expect your project to succeed.
We are looking for a Asp.net CMS to integrate in our existing Enterprise-Webapplication. Some requirements:
Full integration in Visual Studio 2010 and our existing Application (so no Umbraco)
Common ASP.NET Web Forms Developing practices (Global.asax, Masterpages, User-/Custom-Controls)
Security (FormsAuthentication, custom Membership-/RoleProvider)
Very flexible and extendable (good API)
Lightweights CMS with good performance (thousands of simultaneous requests)
Easy content editing
At the moment we are looking at Sitefinity and N2CMS.
I really like the N2CMS approach (Integrate CMS engine in application) but is it mature enough for "real" usage scenarios? Is there another alternative to N2CMS?
Yes, N2 is mature. Company I work for is using it for more than three years now for various projects, and it is still our platform of choice. Best thing about it is that it is not CM System in a classic manner but rather CM Framework with several layers, meaning you have many things implemented, but they are not part of the core. As a result, you can change almost anything that is not usually changeable in other CMSes.
Also, whole architecture is organized in such a way that you can easily override almost any system behavior with your own implementation. Example? Imagine you reached 100s of news entries under News folder in site tree, and you decide to completely hide them from site tree, instead implementing plugin for manipulating them. Solution? Attribute-decorated class with 10 lines of code for hiding items in a tree based on your custom rule expressed in C# code.
I think N2 is pretty polished product and that you can go for it without too much worries.
We too are using N2. We've used it for a campaign site and now we are building our companies corporate website and the 20-or-so country specific subsidiary sites.
It is very fast to develop on (if you are a .net programmer it is a treat, an html-guy might find it difficult). Extremely flexible and extensible. And so far it seems to be very mature and stable. It has less features in terms of workflow-management than e.g. sitecore, but then again most customers put a lot of emphasis on those things, when they evaluate options, but end up not using them. So I don't think that is a problem.
The problem we are having is that it doesn't properly support preview, so website editors cannot preview their changes before publishing them. It is supposed to be done at some point, but there is no word on when.
Full disclosure, I work for Telerik and I'm the Sitefinity Evangelist.
Full integration in Visual Studio 2010 and our existing Application (so no Umbraco)
This is a difficult item to claim with a blanket statement.
I don't know much about your existing application. Our customers have accomplished a lot of Sitefinity integrations with various applications. This could be done through web services, custom controls or simply accounting for external URL's in Sitefinity's sitemap. Feel free to post to our Sitefinity forums for recommendations for your specific scenario.
Regarding Visual Studio integration, Sitefinity includes Telerik RadControls and OpenAccess ORM. We also try to align ourselves closely with traditional ASP.NET technologies.
Common ASP.NET Web Forms Developing practices
Sitefinity Templates = ASP.NET Master Pages
Editable CMS regions = ContentPlaceHolders
Sitefinity Widgets = ASP.NET Controls
Sitefinity Themes = ASP.NET Themes
We make the marketing claim "if you know ASP.NET, then you know Sitefinity". However, realistically all products comes with some learning curve. As much as possible we try to align ourselves with the experience ASP.NET developers already have.
Security (FormsAuthentication, custom Membership-/RoleProvider)
Sitefinity's authentication is based on traditional ASP.NET Membership & Role providers. We've included a couple (Sitefinity & Active Directory) but you can extend with your own.
Very flexible and extendable (good API)
Our API is LINQ enabled and we also have a Fluent API. We also have a full RESTful web service API.
Lightweight CMS with good performance (thousands of simultaneous requests)
Our own Telerik web sites run on Sitefinity, and many of our customers support web sites that handle a large volume of traffic.
However, I'm not sure what constitutes "lightweight". Many CMS's have little overhead, but also do very little. We've tried to deliver a lot of features and end-user friendliness with Sitefinity. This comes at the cost of some overhead.
Managing the balance between a CMS that "helps you" and "gets out of your way" is a constant challenge. The best I can promise is that we're aware of the challenge and we're doing our best to deliver effective results.
Easy content editing
Judge for yourself. Even better, download the product and let your content editors experiment. We welcome the comparison. Over & over again, this becomes our differentiator.
--
Hopefully this post doesn't sound like a lot of evangelist BS. I've tried to be accurate with my answers. Best of luck with your project.
I would like to take a look at Adobe CQ5 CMS system. Does anybody know if I can download it to my developer computer? I can not find link on web site.
I know Adobe offers CRX as opensource - but my interest is in CQ5 cms.
You can download it. Adobe has re-branded and re-released Communique since acquiring Day Software. CQ5 is now known as ADEP. Read about it in Adobe's ADEP Architecture Guide: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/solutions/customer-experience-solutions/enterprise-platform/pdfs/adep-2011-architecture-considerations-for-new-and-existing-customers-ue.pdf. Here is an excerpt:
The Day CQ and CRX product lines have been incorporated into ADEP. CRX forms the foundation of the Experience Services stack, and CQ has been branded as the new Web Experience Management solution.
Architecturally, these products are unchanged, enabling a smooth upgrade experience in the future.
New customers requiring the web content management capabilities of CQ should purchase and develop
their applications on one of the Web Experience Management solution editions (Basic, Standard, Premium).
The Web Experience Management solution incorporates all the capabilities of CQ 5.4.
Download a trial version of ADEP here: http://www.adobe.com/devnet/enterprise-platform/trial-downloads.html
According to my rep you need to engage with Adobe to get a copy. We don't have it in house yet as the do want a training session so that users aren't frustrated with the complexity. I've played around on a test site and also played with it at conventions and it seems like one of the better designed CMS options at the moment.
I am working on CQ5, its a very advanced CMS tool as compared to the others. But its not a open source like other Drupal, Joomla, etc. You have to purchase the developer suite.
Refer to the links for online document support.
CQ5 generally requires a license. However, you CAN get started with the various components. CQ5 is a system built on top of Felix (OSGi console), Jackrabbit(JCR), and a few other pieces, e.g. ExtJS for a lot of front end stuff. If you learn these technologies you won't 'know' CQ5 but you will have a big step up in terms of learning it.
The best thing to do is learn SLING.
http://sling.apache.org/documentation/getting-started/discover-sling-in-15-minutes.html
If you really understand Sling and OSGI, the JCR stuff is pretty trivial. Mastery of these core technologies makes CQ/AEM pretty straightforward.
Adobe CQ5 is a tool being used for creating websites having content-oriented pages. This is a product of Adobe, so you cannot get it free.
Instead, to get a glimpse of it, please refer developer website of Day OR adobe CQ. Also, we have some useful URLs, which can be referred: http://vimeo.com/39504016 (an introduction video) ; http://docs.adobe.com/ ; http://adobecq5interviewquestions.wordpress.com/introduction-to-cq/
what's a good cms for web shops ? I've always used Drupal so far, but I haven't ever developed webshops. I saw there are Magento and a Drupal module Ubecart.
I actually would like to know a "known, easy to use webshop framework so I don't have to take care abuot security issues.. etc
thanks
I have been using both Magento (community edition) and Ubercart depending on client's target hosting preference. I must say that Magento has some impressive functionality and flexible as it has been around for a while. However there are some serious problems with this. Upgrading Magento to the latest version is a complete nightmare and have a good chance of needing to reinstall. Building your themes in Magento is so convoluted, it takes so many inheriting files to create a simple layout change. There is cummunity support, but most of them screaming for help as I remember. Magento model is "make money from support". So I found that they are not so quick to help on the forums.
With Ubercart it is refreshing to see the amount of active help. I think this is important if you are new this. If you are already familiar with Drupal, then I would say stick with Ubercart. It is much simpler to manage than Magento.
They are both good with application security, but you will need to setup your own SSL cert anyway. I've played with some other carts such as Zen and OS Cart, but found them inferior compared to Ubercart and Magento.
There are more than 500 of them. shopping-cart-reviews.com has a search by parameters feature, does a good job.
If I where you, I would compare open source packages like magento and ubercart against hosted ones like our own SolidShops.com.
Check out my blog post about magento (and open source ecommerce packages) versus hosted ones. I've outlined when to go best with open source / hosted depending on your situation.
We've built SolidShops.com specifically for web designers that need an easy and flexible platform for building small to medium sized stores. It's hosted so you won't have to install, update, secure, backup, ... a thing
Design is 100% flexible if you know html and css and it's a breeze to set up.
I was trying to analyze the trend about companies leaving their own custom built solution in favor of the standard CMS solutions such as Drupal, Joomla and DotNetNuke etc. While I can find many stories about medium and large organizations leaving their custom solution for Drupal/Joomla etc, I cannot find any reference where organizations are leaving prebuilt CMS's/Frameworks to go custom again. Is this not happening at all or it's just a matter of not being properly documented?
Thank you.
Imran.
I can't think of a situation where a company has abandoned an in-house developed CMS in favor of re-developing a CMS on their own.
Everything I'm familiar with involves leaving a hand rolled CMS solution in favor of a commercial/open source solution.
Well i can imagine that while most companies prefer homebrewn solutions for some of them or in certain scenario's an open source or commercial alternative might fill their needs.
In case we at our work need to set up a blog we'll most likely choose wordpress, we know it, it does what it needs to do and does it good. Customization isn't a big deal but out of the box it works too.
For larger projects we always use our own CSM built with our own framework, that is what we know best.
So to answer your question, I still have to see the first company going from existing CMS to custom built but i'm fairly certain there are alot doing both.
Looking at it just from an engineering standpoint -- a commercial CMS company, with 50 full time engineers, puts in about 100k hours of engineering effort annually into managing and developing products. A homegrown solution typically has a small team of engineers assigned to manage and develop it, often also balancing other projects & responsibilities. Let's say the homegrown solution has a team of 4 people, working part time (20 hours) a week, which is about 4k hours annually into managing and developing the product.
That's 100k vs 4k hours of engineering in 1 year.
Also consider, for the homegrown solution, most of the first year's 4k hours will be spent recreating basic content management that has been written 100 times over, e.g. permissioning, workflow, approval processes, etc.
From a business standpoint, businesses want to focus on their core competencies. Unless your core competency is content management, makes no sense to build a homegrown CMS from scratch, and companies largely are not doing this, or moving away from them if they have in the past.