armonraphiel

- Bed reviews are either very anecdotal or company sponsored.

- Do not buy a bed without testing it. Bring a pillow and spend at least 15 minutes relaxing on each candidate.

- If you can afford it, avoid “beds in a box”. They retain serious heat, provide little support for any sleeping position, and are not easy to return. Casper beds specifically caused me and my spouse a month of back pain.

- Test the softest version of the bed before making a decision, even if you prefer firm beds. There is a often a significant positive difference between “medium” and “extra plush”.

- Beware “free” add-ons. Mattress stores use them to hedge against returns and refunds by applying the value of the items to the mattress. This means if you return the mattress, you won’t get the full refund back.

- Shop at local mattress outlets, if possible. I was able to save $1,200 on the same exact model quoted (also at discount) at the major mattress chain with no haggling.

Looks like the core site is Rails but it seems they use a bit of everything. Preact, Go, Node, etc

You also get a few free static sites as well https://www.digitalocean.com/products/app-platform/

At the time, the master->main switch felt completely pointless.

But I came to appreciate the courage needed to actually commit. It's a signal that people do care.

Issue is, most folk have no idea on how to meaningfully contribute towards a lack of representation.

That said, I used Rails for the first time for a small client last week and it was fairly easy process.

I’d also recommend ACloudGuru as well

The vast majority of users that WP caters to are better served by Facebook Pages, Wix, Squarespace and Webflow.

Large and high traffic sites aren’t a great fit for WP either as the codebase was never meant for scalability and still maintains a painful developer expierence.

There are plenty of options, “JAMStack” included, that are still a much better fit.

However, before migrating I suggest:

- using Jekyll's --incremental flag

- move your asset pipeline into a separate process (webpack --watch)

- reduce any Jekyll gems (each one adds considerable overhead)

If you want to leave Jekyll, I also recommend Eleventy. It's fast, require very little work to migrate from Jekyll, and can create pages from data.

Each one I’ve seen built was an attempt to drastically raise the value of zoned lots before selling it off as part of a package deal.

It's a feeling that doesn't go away & often compounds on imposter syndrome.

The full product can be compared to Google Firebase but the Amplify Console specifically offers features similar to Netlify on top of standard AWS services (S3/CF/Codebuild).

I find it a much better experience than manually setting up S3/CF websites because of the out-of-the-box features that simply wouldn't happen otherwise for a static site like:

- instant cache invalidation

- branch deployments (with password protection & rollbacks)

- deployment process only deploys modified files

- simple custom headers

- simple redirects (redirecting individual assets in Cloudfront is not easy)

Eleventy is my new Jekyll replacement.

- Node.js based (a simple npx command)

- Easily understood by beginners

- supports multiple template languages

- can build pages programmatically (needed for building pages based on external data sources)

- is quite fast

I’m a huge Gatsby fan but Eleventy is preferred for projects where React isn’t necessary.

Hugo also deserves honorable mention but it’s been relegated behind Jekyll, due to its confusing documentation.