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/
EDIT: One interesting observation (from the outsider's perspective) - As I see, Clojure encourages use of primitive/language-provided data structures such as maps, lists, etc.. instead of creating your own abstractions and "inventing languages" (this is mentioned in a negative context, in Clojure docs). This is radically different approach compared to e.g. SICP, where creating many mini languages is actually encouraged. I personally find Clojure approach messy and unstructured (Also browsing a code in the wild).
Anyway, as I can tell, Clojure has enough support to create well structured abstractions.
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.
I don't think I would do well in those sorts of interviews. I guess my experience is different because I've only interviewed remotely (remote interview, on site job). So they were typically 2-3 30 min Skype calls with different members of the company (CEO, CTO, Investor occasionally) and then I would send through code for them to look at or they would give me a small feature of their product to develop (1-2 days paid remote work) and review me based on that.
That kind of coding interview would be ideal too, but that takes more total time than 4-6 hours. It's 8-16 hours total vs 3-6 hours. When an engineer has a FT position already, they can't easily commit that much time as you can as a freelancer.
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."
- 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!