Learning anything from scratch isn’t a problem. In the beginning, milestones between each difficulty level are small and it is easy to get a sense of accomplishment for each small step you take.
After one or two weeks, “reality” sets in. It becomes increasingly difficult to hit the next milestone. Sometimes people just forget the initial enthusiam they. Sometimes, they become “too busy”. Most people give up on learning at this stage. Some persist for another month or two before giving up. Yet, others continue to learn and thereafter begin to excel in whatever they do. Is there a secret in learning?
Over the last half a year, I have gone from knowing nothing about designing and coding, to building two wordpress themes and I am still learning. My motivation is still strong.
In this post, I would like to share with you how I view learning after persevering for 6 months and how I kept my motivation levels up.
It is very common to have to change CSS codes midway in a design at some point or another. Because of the way most CSS codes are structured, it is usually painful to sieve through the whole code and look for the particular area where you would like changed.
Whats more, if colors or text sizes have to be changed, it can be disastrous if you miss out on a few elements and an absolute headache if you can’t find where they’re located
In this article, I’m going to introduce one simple add-on that really helped me with organizing and changing my CSS codes.
One of the blocks I had while I designed my first website was how much space should I leave after my headings or paragraphs. Along the same question, how much space should I give within the line of text themselves. My first approach to this whole process was to eyeball it. You might have done the same
There’s nothing wrong with eyeballing the amount of space and setting it according to your gut feeling. However, there is a much better approach to setting this amount of space and we’re going to cover it in this article today.
Now that you’ve managed to create the layout and header sections, its time to move into the meat of the series. In this article, I’ll discuss how I styled the content section on my blog and also mention various elements that are easily overlooked by first time designers. If you’re working on your own blog, this would be a great post to pick up important design considerations and to see if you missed anything out.
Continuing the series on creating a clean and simple website, I’m going to share with you how I coded my blog from scratch. In this article, I’ll discuss how to go about first creating fixed width layouts using pixels. If you’re new to this, you might want to check out the previous article on writing HTML for the website that we’re creating
II’ll try to explain everything clearly and simply in a way that you should be able to follow even if its your first time looking at CSS. My blog design definitely doesn’t have the bells and whistles around the internet, and thats why I think its such a good place to start from.
CSS can be seem to be difficult at a first glance when you’re new to it. You may be confused about the different CSS properties, what they do and what they are for. Don’t worry, I got you covered.
Have you heard of the 80/20 rule where 80% of the results come from 20% of the effort? Its the same in CSS. Which is why in this post, I’m going to talk about the most highly used CSS properties you will definitely need to know.
Its going to be a post packed full of information. Lets dig in.
After getting to know the structure of the website look like, its time to create them. In this article, we’re going to explore how to create the HTML content of a website.
Websites have a structure, just like houses have pillars. Understanding the structure of a website and how it is made up is an essential first step in creating a website. Today, I’ll dive into the overview of what a website structure look like, and how planning this structure in advance can really help you learn to create a website.
Until a few months ago, I always thought programming was something that I would never venture into. I really see the value, yet, I never really dared venture into the massive lines of code.
Honestly, I was afraid. I was afraid of the thought of giving up halfway because the workload was so tough. I gave up along the way a few times, but managed to pull through till today. It wasn’t as bad as I thought after all. People have the misconception that you have to be damn smart to program, but it really isn’t the case.
If you feel the same, this post about my story could give you something to think about.