Loading...
Answers
MenuI need to have an advanced membership website developed - do you have recommendations on choosing between WordPress and Ruby on Rails?
I need to have an advanced membership website developed, allowing 2 different types of users to login, create profiles and view customised dashboards - very similar to Clarity in terms of functionality in fact. Do you have any recommendations on whether WordPress or Ruby on Rails would offer the best solution? I know that WordPress is widely used and has great functionality but was informed by a developer that Ruby on Rails would provide a more advanced solution. I'm also seeking a developer - preferably this won't lead to a biased answer for the first part of my question - any recommendations would be greatly appreciated! (Functionality will be key for me.)
Answers
You are comparing apples to oranges. WordPress is a platform, Ruby is a web framework. If you are looking to develop a completely custom platform, you could certainly do it in Rails, but you could also write it in PHP (like WordPress).
I'd do some digging and see what is out there for pre-made software first before you build something from scratch. I'd imagine there are already plugins that would do this sort of thing for Expression Engine, Joomla or WordPress. No need to re-invent the wheel!
In the short term I think you will get going quicker with Wordpress with some plugins that should enable what you are looking for.
But to make this decision I would first consider if this version of the product you are looking to build is just to test if your business can work - like an MVP (Minimum Viable Product) - or is it the long term version of something already tested and proven.
If you are still trying to figure out if what you want to do has any legs, then I would go with wordpress. Get it running in a few days and test everything you need to make it work. For example getting users, creating the content you need and learning how to convert visitor to paying members. If you spend a few week/months on this and you get answers to all the non-technical questions, you can also re-asses if it is time to build a fully custom solution.
If all the other parts are already figures out and you want a custom build technical solution that allows greater flexibility I would use Rails. Or some of the other frameworks like node.js or CakePHP.
There are also some software services online build for this. So make sure you look at them as well.
Ruby on Rails has some limited options for membership sites so it's likely you'll need custom development to get the solution you want. It's more likely that you'll find a WordPress plugin that covers your needs - including something like Paid Memberships Pro that is free but is super developer friendly.
Caveat: I advise on & build WordPress membership sites so I admit that I may be a little biased :)
You won't be able to build Clarity on Word Press. It's a content management system so while powerful is extremely limited compared to what you could do with Ruby or any other software language. But as someone else identified here you're comparing apples to oranges. Word press will give you a website quickly and you can make some tweaks and changes within the limitations of WordPress and it's plugins. Ruby on rails is entirely different - you can build whatever you want. Although it will take longer and cost more, you'll be able to create a web application as opposed to just a website. Hope that helps!
Full Disclosure: I'm the founder of ChimiChurri (see http://chimi.co). We build the kind of membership website/application you are looking to build by leveraging a proprietary product building platform and a professional services team. I'll attempt to keep my answer as honest / unbiased as possible.
The quick answer is you can likely build your membership website with either. But, WP is, IMHO, the wrong tool for the job. I have built WP sites and coded WP plugins before and, from a software engineering perspective, you'll likely very quickly end up in what I'd typically describe as "plugin mess". Meaning you'd probably end up with a duct-taped ball of WP + custom theme + several (different) third-party plugins + custom code + third party services that will be extremely hard to maintain and continue to iterate and build upon. So, while doable, you'll sacrifice quality and accumulate "technical debt", to say the least.
As per Ruby on Rails, it is a very solid MVC framework I have used to build many products and applications throughout my career, including marketplace and market-network type applications like the one you are describing. But, with RoR alone you'd indeed have to build lots of custom functionality to get to MVP or v1, and that will take money and/or time.
With Chimi (our product building platform), you can get the best of all worlds: a solid, robust Ruby on Rails application that has lots of the features you are looking for available out-of-the-box, without sacrificing quality, flexibility, or ownership, and with a relatively small budget and fast execution and implementation time.
With Churri (our professional services) you also get access to top-quality engineers and developers that can build custom features and integrations unique to your needs.
Let me know if you'd like to setup a time to chat - I'd love to give you a demo and see if we'd be a good fit for your needs.
Disclosure: I co-own the business that does both custom development and Wordpress development.
While there are number of plug-ins to organise membership website for Wordpress, I don't think that you can build something like Clarity there.
Like others wrote in your case Wordpress can be a way to test the water, prove that there is a demand for your solution. You'll get something running fast albeit you have to go with what is available rather than develop it the way you see it.
Sooner rather than later you will overgrow the platform: the solution will be too complex, to slow, to hard to maintain and modify. This is a point to leave Wordpress and develop custom solution with Ruby or other technology.
Should you start from Wordpress or Ruby depends on many things, the most important in my opinion are;
- Where is your innovation? Is it on tech side or more on business side?
- Can available Wordpress plugins meet at least critical requirements to your MVP ?
Feel free to contact me for further discussion of your projects.
Rails hosting is going to cost you way more and you must take into consideration maintenance, e-commerce app development, widgets, etc. If you are on a budget and you want the better price, then I would go with WordPress.
You can read more here: https://www.devdude.com/ruby-on-rails-vs-wordpress/
Besides if you do have any questions give me a call: https://clarity.fm/joy-brotonath
Related Questions
-
How much should I charge to develop a WordPress site?
Take the # of hours it takes you to do it and charge $50/hour. That's the price. Eventually you can charge $100/hour but that will require a bigger customer. If the customer is small < $1M in gross sales per year - charge $50/hour If the customer id medium < $1-5M / sales - charge $75 Over $5M - charge $100 The challenge you'll face is clearly defining the expectations and handoff so that you're not stuck doing stuff that you can charge for and always getting interrupted from past customers.DM
-
I want to build a expert marketplace directory listing website, which wordpress theme I should use?
Checkout is a high-quality WordPress theme by Array built for marketplaces of any kind. https://arraythemes.com/themes/checkout-wordpress-theme/ Let me know if you have any questions about implementation, and I'd be happy to setup a call.LL
-
How do you manage a developer who's slow, especially when you have a small budget and you don't feel like you'll get things done in time?
Usually Programmers are only slow when they don't know how to solve a particular problem. So they will spend a lot of time researching and a lot of trial & errors to solve a problem. It is important that before you engage a programmer on a project, you break down the entire project into simple, easy to understand modules. Let him give you an estimate of how many hours he will require to complete each of the modules. Example: a typical site will have a login module, registration, My account, profile etc. So let him estimate how much he will require to do the login. You can go even detail here. (e.g. how much extra time if you were to implement Facebook/Twitter Login?). Once he start developing, track his progress closely and make sure he is following his given timeline. If he goes over his budgeted time on a module, talk with him and see what went wrong. It is often seen that they may be wasting their time on something very insignificant that you may have asked him to implement, but you can totally go by without it too. So by understanding what is taking longer time, you will be able to prioritise things better. You definitely need some tools to get this done. Google Spreadsheet or Excel works just fine. But if you don't mind spending a few bucks there are many agile project management tools that you might look into. Here is a list, google them all and sign up for trials: * AgileZen * Agile Bench * Assembla * AssiTrack * Blossom * Basecamp * Breeze * DoneDone * Eidos * Fogbugz * GreenHopper * Jugggla * Kanbanpad * Pivotal Tracker Or the reason why he is slow can be purely non-technical. Sometime your developer may don't share the same level of enthusiasm as you about the idea that you are working on. They often don't often see the "bigger picture" (since you don't share everything with them explicitly). If you can somehow get them excited about what he is a part of, it will work like a drug :) He will work day and night without questioning you. But you need to work equally as hard as him. The moment he sees that you are the boss and he is just the guy doing work for you -- his mentality will shift from being part of something to being the low paid developer. Ultimately its all about motivation and making him a part of your venture. After all he deserves it, if he is really playing a crucial role in the entire development.SK
-
What are the key accomplishments for the first year of a startup?
A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.TW
-
How can I manage my developers' performance if I don't understand IT?
Whenever you assign them a task, break down the task into small chunks. Make the chunks as small as you can (within reason, and to the extent that your knowledge allows), and tell your devs that if any chunks seem large, that they should further break those chunks down into bite size pieces. For instance, for the overall task of making a new webpage, _you_ might break it down as follows: 1) Set up a database 2) Make a form that takes user email, name, and phone number and adds them to database 3) Have our site send an email to everyone above the age of 50 each week When your devs take a look at it, _they_ might further break down the third step into: A) Set up an email service B) Connect it to the client database C) Figure out how to query the database for certain users D) Have it send emails to users over 50 You can keep using Asana, or you could use something like Trello which might make more sense for a small company, and might be easier to understand and track by yourself. In Trello you'd set up 4 columns titled, "To Do", "Doing", "Ready for Review", "Approved" (or combine the last two into "Done") You might want to tell them to only have tasks in the "Doing" column if they/re actually sitting at their desk working on it. For instance: not to leave a task in "Doing" overnight after work. That way you can actually see what they're working on and how long it takes, but that might be overly micro-manager-y At the end of each day / week when you review the tasks completed, look for ones that took a longer time than average (since, on average, all the tasks should be broken down into sub-tasks of approximately the same difficulty). Ask them about those tasks and why they took longer to do. It may be because they neglected to further break it down into chunks as you had asked (in which case you ask them to do that next time), or it may be that some unexpected snag came up, or it may be a hard task that can't be further broken down. In any case, listen to their explanation and you should be able to tell if it sounds reasonable, and if it sounds fishy, google the problem they say they encountered. You'll be able to get a better feel of their work ethic and honesty by how they answer the question, without worrying as much about what their actual words are. Make sure that when you ask for more details about why a task took longer, you don't do it in a probing way. Make sure they understand that you're doing it for your own learning and to help predict and properly plan future timelines.LV
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.