learn-ruby VS Solidus

More consistent learning. The job search also gave me a chance to get back to my Ruby/web development learning roadmap. I realized that at my last job, I wasn't consistently spending time improving my skills, outside of whatever I might (if I was lucky) be learning in work projects. It's just hard to fight against the pressure of the day-to-day work. Here are some approaches that I'll try this time around: Disregard immediate applicability and learn something I'm interested in for the sake of expanding my mind. Right now that's learning functional programming. Learn actively, whether by contributing to Exercism's Ruby track, building a collection of Ruby code katas, or maybe even creating a text-based game.

Beyond these basics, I've put together a list of my favorite Ruby/Rails learning resources.

I made the Git list by (1) scouring the Web for recommended resources, then (2) trying out each one to see if it would be worth going through to the end. In case you're curious about which resources didn't make the cut, here's the commit where they are removed.

As a guide to my reflections today, I'll use my "Learning Ruby" roadmap, which originally arose out of the chaos of my bookmark hell, where I was having trouble keeping track of the actually important learning resources. The roadmap worked well for me and eventually I put it up on GitHub because making it public gives me more motivation to keep making progress.

For me, Ruby was a great choice for a career change. I used to be a teacher until I quit in 2020, then over the next 1.5 years I studied and practiced part-time, while working full-time in a remote customer support job. Ever since I started learning Ruby, I've saved my favorite learning resources here: https://github.com/fpsvogel/learn-ruby. Many of them are free.

So I've set out to explore the problem of organizing business logic from more angles than before, using the resources listed below. These lists are excerpted from my "Learning Ruby" road map which I often update, so you may want to find these lists there if this post is old at the time of your reading it. The sections corresponding to the lists below are, at the time of writing, "Rails architecture" and "Rails codebases".

For more resources, here's my list of my favorites: https://github.com/fpsvogel/learn-ruby

I'll tell my story and you can decide if it resonates with you at all. Also these might help you: my Ruby roadmap (favorite learning resources), and my blog post "How to find your first Rails job".

I've made a big list of my favorite learning resources, but here are some possible first steps:

I actually don't know of a good "beyond the basics" Rails course. The one or two that I've seen out there are prohibitively expensive. For me the best way forward has been to improve in specific areas, such as OOP, testing, and SQL basics. I've made a list of my favorite resources in each area, which might help you.

github.com/solidusio/solidus (72k lines): E-commerce platform.

Not really basic, but Solidus.

In 2014, Floyd was lesser known as The Floyd Leg. Our website was on Squarespace for both its e-commerce solution and web hosting. A large part of our current success was realized by choosing to invest in a custom web application that’s built with Solidus. With our website no longer abstracted by a WYSIWYG ("What You See Is What You Get") editor, we partnered with Nebulab to handle full-stack web development. Solidus (Spree, at the time, before it was acquired, forked, and renamed) was recommended to power the e-commerce part of our application. The decision to go custom came after a successful Kickstarter campaign back in 2015 for the Floyd Legs—a set of four steel table legs that fastened onto any flat surface to quickly put a table together. We proved a market need for adaptable and sustainable furniture design. The co-founders, Kyle Hoff and Alex O’Dell, knew there were more product offerings on the roadmap as they championed Floyd to be the furniture solution for all apartment essentials. Fast forward to 2019, Floyd is seeking to be the furniture solution for the entire home worldwide.

I'd say Solidus and Spree are you best options rather than trying to roll out you own ecommerce solution.

Completely agree. Alternatively, I would look for an open source project like solidus https://github.com/solidusio/solidus

Solidus: https://github.com/solidusio/solidus/releases/tag/v3.1.1

Check out https://solidus.io/

Hey there! I'm about to set up a small eshop (expected around 50 orders/month) for a relative (an artist). I've contemplated what's available, and I'm not very happy with what I found.

- There's Woocommerce, which I've installed and tried doing basic setup, and it's too deeply bloated in the Wordpress ecosystem. My first impression from Prestashop was that it's going to be quite a similar PHP mess

- I don't want to get vendor locked-in with things like Shopify. They also don't seem to offer much design customizability (I'm a web dev and there's quite a unique design concept for the site from the artist)

- Searching GitHub for ecommerce, Solidus[1] looked quite promising, however, it also slightly overshoots the border of 'too complex' for me, and their docs on integrating a custom payments provider (a strict requirement - not US based) aren't really great

[1]: https://github.com/solidusio/solidus

So my question is: are there any borderline-pet projects I've missed?

I've been doing web dev for over 2 years now, so I'm also thinking about building my own almost-serverless solution. Is that plausible in reasonable time (wouldn't want to give this more than 2 weeks), or are there too many holes to fall into even though the sensitive part of payments is handled by a simple integration?

One more bit of info, together with building this, their whole web is going to be transferred to a new CMS, likely the Netlify headless CMS (IMO a very cool concept - no backend, frontend uses GitHub http API to directly commit any saved changes). Therefore ideally I'd love to integrate the products inventory into this CMS, which saves data into markdown + front matter, and then can be built into HTML or any JSON to be fetched by frontend - that's why I said almost-serverless.