![]() Squarespace 5 supported XMLRPC which allowed me to utilise the excellent Mac blogging application MarsEdit. Nowhere near as much effort as this migration took, but certainly more than I felt was acceptable. This meant it would have been a lot of effort to migrate. ThoughtAsylum was far from being a simple site in Squarespace migration terms. Squarespace had a migration path to upgrade sites from version 5 to version 6, and beyond, but they were suitable only for simple sites. This area actually covers a multitude of things, but previously this site was to an extent ‘stuck’ on an old version of the Squarespace content management system ( CMS. ![]() Squarespace was no longer fit for purpose There are many reasons for updating the site, but they probably break down into a couple of main categories. I’ll come back to discuss many of these points in detail below. There’s no option for scheduling blog posts.There are no more comments on blog posts.The search is now utilising an external search engine rather than something on the platform.The look and feel of the site has been refreshed.The format of the site has changed to make it responsive, so that it is now much easier to use on mobile devices. ![]() The content was originally written in HTML, but is now predominantly converted to Markdown, HTML only being utilised where Markdown has proven insufficient.The site is now being hosted on GitHub Pages. The content was previously being hosted on a Squarespace system.While the content is the same as it was before at the level it is shown to you the reader, pretty much everything else has changed. In this post I’m going to give a little bit of background to the what, why and how. It isn’t just a makeover, it’s actually a rebuild from the ground-up. At the end of the day I think any convention is better than no convention and by that I mean anything but random, but remember alphabetize is better than all other options.If you have visited much in the past, you may have noticed a change recently. You’ll be surprise how quickly you can adapt and write code. Here’s what I propose: if you’re not already ordering your properties alphabetically, try it out maybe for your next project. Other than that, I have not faced any other obstacles using alphabetical ordering with my teams. Lets be honest though, this can occur with any of the other methods as well. This will cause the element to stretch horizontally across its’ parent rather than move it to the right. This means if the property is altering the element’s dimensions it’ll be in one group while positioning will be in another. The most popular method seems to be logical grouping, grouping properties by their logical use case. Other Conventionsīefore diving into the benefits of alphabetical ordering lets weigh in on the competitors. After doing some research (Google searching and reading the handful of forums) there doesn’t seem to be a lot of people practicing alphabetical ordering of properties - in fact the poll at CSS Tricks shows that only 14% of polled users do so. ![]() What actually prompt me to write this article was how unpopular or discussed this method is. I usually proceed to explain why, which I will detail later on. This is because mentors are people who’ve been working in the industry for some time and often never heard of the approach. Usually it’s the mentors that then questions, “why?”. My answer is always, “it’s alphabetical” - everybody usually laughs, then realize I’m serious. I’ve been teaching an Introductory to HTML and CSS course for Ladies Learning Code for a few years now, and usually part way through the CSS exercise somebody will ask, “how do you know where to add that CSS property?”. Alphabetize your CSS properties, for crying out loud ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |