I've been using Squarespace's developer platform for a gallery site. It's decent. I used the blank developer template, so I built most of the CSS from scratch. In my opinion, some of the drawbacks are:
- The editable text fields only support h1, h2, h3, and p tags. If you plan to have four font sizes or the people maintaining the site don't mind using the editable code blocks, this isn't a bad thing.
- If you use the built-in blocks then write your own CSS overrides, you are assuming those classnames (generated on squarespace's side) will be the same. Forever.
- I found myself overriding a lot of the system blocks with very bad css (some !importants)
The good things:
- Every post has an associated JSON endpoint. No heavy lifting on this side.
- In my experience, support gets back to you in a day or less with helpful answers.
- The support for custom post types (See the docs) is finally acknowledged.
In my opinion, the developer tools are great for your own site or if the client has familiarity with basic html tags. I am not sure I would use it again for a site to hand off to a non-technical client. If the system blocks (built in video, text, image types) were customizable, I would recommend Squarespace more heartily.
I have not used Squarespace's ecommerce functionality so I am unqualified to comment on those. I have heard good things about Webflow's CMS offering, so I would check that out to compare.
Before getting into web dev with Clojure, I recommend reading and doing the exercises from Clojure for the Brave and True to learn the language itself. It is one of the most engaging technical books I have come across in some time.
http://www.braveclojure.com/
In my experience, I have had 3-6 hour long blocks with 1-3 members of the company, technical and non-technical. It typically starts with 5-10 minutes of chit-chat about my background and the company, then we do a technical exercise or a series of personality questions (for instance, explaining something technical to an employee in marketing to see if we could work together and if I could communicate across departments). After that, we wrap up with ~10 minutes of Q&A. Since it takes up so much time, it's important to get the phone screen right to not waste time on both sides. I have heard of companies that will have you pair program for a whole day instead of doing whiteboard questions.
Burning Man is a great week to be in the Bay Area. Shorter lines for everything, less traffic, more seats on the bus, et cetera. I wish it lasted a month.
Excellent project. Small angular error: when I go to http://ysnmn.org/#/services/30, it looks like there's a ng-repeat dupes error in the console. Using track by $index may solve this (I ran into this problem working with angular).
I don't see it on any other pages. Either way, nice work!
One example -> the city of San Francisco offers bus tickets home for homeless people who have relatives or friends in another town who are willing to take them in. The program is called "Homeward Bound."
If you want to live in San Francisco proper without paying a terrifying amount, try looking at some neighborhoods that are not the same places where everyone wants to live (Mission, SOMA, Lower Haight, North Beach, NOPA, etc). The Inner Richmond or Sunset are good picks if you don't mind having a 20-30 minute commute. Still expensive, but not as bad as the aforementioned neighborhoods. Those can easily be $2k per person if you are signing a new lease and not moving in with someone with rent control.
If you want some substantial space for $2k or under, I would look at the East Bay exclusively.
I have tried to finish this book three times, but I have had to start at the beginning each time. The plot is dense and I can't jump back in after ~150 pages and a month of not reading it.
I would not worry too much about making the "wrong" choice between Ruby and Python. I found it fairly easy to learn Python after coding Ruby for a year. Have fun!
- The editable text fields only support h1, h2, h3, and p tags. If you plan to have four font sizes or the people maintaining the site don't mind using the editable code blocks, this isn't a bad thing. - If you use the built-in blocks then write your own CSS overrides, you are assuming those classnames (generated on squarespace's side) will be the same. Forever. - I found myself overriding a lot of the system blocks with very bad css (some !importants)
The good things: - Every post has an associated JSON endpoint. No heavy lifting on this side. - In my experience, support gets back to you in a day or less with helpful answers. - The support for custom post types (See the docs) is finally acknowledged.
In my opinion, the developer tools are great for your own site or if the client has familiarity with basic html tags. I am not sure I would use it again for a site to hand off to a non-technical client. If the system blocks (built in video, text, image types) were customizable, I would recommend Squarespace more heartily.
I have not used Squarespace's ecommerce functionality so I am unqualified to comment on those. I have heard good things about Webflow's CMS offering, so I would check that out to compare.
This post was very helpful to me in seeing how other people use the dev platform (I have no affiliation): http://www.instrument.com/latest/creating-a-clean-custom-mai...
Hope that helps!