Ravelry Lurking

Related Posts:

• No Related Posts

Creating Your Own Website: The Basics

A CMS is the backend of your website. It lets you add new content, moderate comments and trackbacks, rearrange pages, etc. Often, it lets you do this with very little to no knowledge of html or css. It is an administration method that doesn’t rely on hand coding and FTP transfers. Nice, eh?

Choosing a CMS

I’m not going to get into which CMS is right for your business. That is a rather complex evaluation and is a series of articles in and of itself. This is about getting your feet wet and installing and building an experimental website. For our purposes, which CMS you choose is based on your technical abilities and your desire to tinker.

Never Heard of a CMS or Little to No Knowledge of HTML or Curious, but don’t want to spend more than 1 hour

Try WordPress.

Used WordPress Before or Some Knowledge of HTML or Willing to Spend a Few Hours Experimenting

Try Joomla or EZPublish.

Used One of the Previous Systems or Some Knowledge of HTML and PHP or Willing to Spend 8+ Hours Experimenting

Try Drupal.

So what’s the point of picking a CMS now?

For our purposes, you are picking something that you will install and run locally. It will never see the light of day unless you upload it to a real host or change your machine’s web server settings, which I don’t recommend. Shared hosts are generally more secure and have better up time than you would hosting your own site and the price is about the same.

This is what’s known as a localhost. It’s a real web server that is only visible on your local machine. You build and test everything locally and then you upload it and make it available for the world to see.

Why do this? Well, ask yourself if your readers will like seeing all the “Under Construction” notices, error messages, and constantly changing layout. (Hint: The answer to this is a resounding no.) Also, it’s a non-threatening way to experiment.

It doesn’t matter if you blow up the web page (as long as smoke isn’t coming out of your computer, but that’s a separate issue) because no one will see it but you.

How do I create a localhost?

By far the simplest method is BitNami. Simply choose which system you want to install and download and install the native stack. Follow the Readme instructions for your operating system to run it.

BitNami is cheating compared to the old install MAMP (Mac), WAMP (Windows) or XAMPP (Linux and Windows). Download the CMS from its website and install it into the htdocs folder. Then configure the file permissions and set up the database and run through the CMS’s setup process. Later, especially if you have a host that doesn’t use Fantastico or some similar system to install common CMSs, you may want to try doing your own install with a clean MAMP or XAMPP and the downloaded application. But for now, stick with the quick and relatively fool proof BitNami method.

The price for both the BitNami and the MAMP/XAMPP methods is the same…$0. In other words, it costs you nothing but some time to experiment and set things up the way you like them before you push your site out to the world.

What about ________?

For your first experiment, I recommend sticking with one of the systems offered prepackaged by BitNami. Later on, you may want to explore a little more. I’m mostly a PHP person, so the systems that I’m most familiar with are PHP-based. I’ve tried others. Below are a few that I’ve tried and run long enough to say they work in some situations.

• XOOPS (PHP)

• CMS Made Simple (PHP)

• Plone (Python)

• Django (Python)

• Movable Type (Perl)

XOOPS is what I almost went with for this site. It’s nice, very nice, but it lacked a few features that I felt I would need in the future and I didn’t see anyone in the developer channels discussing adding them.

In all honesty, there is little difference between what you can do with CMS Made Simple and what you can do with WordPress, but sometimes you don’t want a blog. You don’t have to have a blog with WordPress, but it’s name is almost synonymous with blogging. If that bothers you, SimpleCMS may be something you want to look into.

Plone and Django were both run in test versions for clients. I really don’t know enough Python to be able to delve into their inner workings, so I didn’t try. The administration interfaces were clean and the learning curve on Django was much lower than I expected it to be. That’s about all the insight I can offer on them, other than hire a Python developer.

I ran my personal blogs on Movable Type for about three months before I moved it back to WordPress. It’s nice software, but the moment I decided to start consolidating, and in one case selling, my blog content, I no longer had any need for it. I found WordPress easier to use both from the administration aspect and from a coding one. (Remember that warning at the top. This is me. I want to at least be able to skim the code and know if it makes sense or not.)

What do you use?

For this site, I use Drupal. It has a higher learning curve than some of the other choices, but it offers some functionality that wasn’t readily available on the others, it has an active community, and it’s development cycle means I won’t be upgrading my system every other month. (The constant upgrades was my major gripe with a self-hosted WordPress and what eventually pushed me towards using WordPress.com for a time.)

Related Posts:

• No Related Posts

Smooth Traditional Heel (Toe-Up)

Worked after a gusset, this toe-up heel is modeled after a traditional top-down round heel, but the construction is radically different. Unlike heels with picked up stitches, it’s ridge-less. Yes, this is another “my dad has the world’s most sensitive feet” creation. After six months of tinkering, I finally had a finished product that met with his approval. Another six weeks with the lovely test knitters on Raverly produced the final result.

Round heels have many names, including French Heel and Traditional Heel. I tried and failed to name this toe-up twist many times. I finally turned to Twitter. Thanks to Racherin for helping me name it. Smooth perfectly describes the inside of this heel.This heel is worked across the heel stitches. That is the total sock stitches divided by two minus the stitches adjusted for the gusset on either side. Please follow your pattern’s instructions for making your gusset and then substitute this heel for the one used in your pattern. If you are using one of my patterns, these instructions and photos are used to supplement the pattern.

Notes on Patterned Heels

After turning the heel, you always slip the first and last stitch. Make sure that your stitch pattern accounts for this. For example, a heel worked in *sl1, k1* heel stitch should be worked over an odd number of stitches. If your heel doesn’t have an odd number of stitches, increase 1 stitch using a tight increase, such as a lifted increase, in the center of the heel. After you finish the heel, ssk in the middle to eliminate the increase.

Heel Sole

The two ring stitch markers used here are optional, but they make life much easier. The below assumes you have an odd number of heel stitches and wish to work the heel in heel stitch. It can be worked over an even number of stitches, but you should change the heel pattern. Otherwise, you will have a double row of slipped stitches on one side of your heel.

Tip: Think about your yarn overs as yarn arounds because the yarn is making a full loop around the needle before you k/p the next stitch.

After finishing the gusset, work the sock up to the beginning of the heel stitches.

Row 1 (RS): Knit the heel stitches and turn.

Row 2 (WS): Yarn over, purl 1, place the 1st heel marker, purl the remaining heel stitches, and turn.

Tip: The yarn over is actually a “with the yarn in the back, purl the first stitch”.

Row 3 (RS): Yarn over, knit 1, place the 2nd heel marker, knit to the 1st heel marker, remove the 1st heel marker, and turn.

Tip: The yarn over is actually a “with the yarn in the front, knit the first stitch”.

Row 4 (WS): Yarn over, purl 1, place the 1st heel marker, purl to the 2nd heel marker, remove the 2nd heel marker, and turn.

Option 1: Moon Shaped

Use this option if the recipient has wide feet or squarish heels.

Work rows 3-4 until there are 9 stitches between the 1st heel marker and the 2nd heel marker. Your last row is a purl (WS) row.

Option 2: Egg Shaped

Use this option if the recipient has normal feet.

Work rows 3-4 until there are 5 stitches between the 1st heel marker and the 2nd heel marker. Your last row is a purl (WS) row.

Option 3: True Round

Use this option if the recipient has normal or narrow feet. This is the truest to a traditional top-down heel shape.

Work rows 3-4 until there are 3 stitches between the 1st heel marker and the 2nd heel marker. Your last row is a purl (WS) row.

Turning the Heel

Row 5 (RS): Knit to 1 stitch before the 1st heel marker. Slip the stitch next to the marker purl-wise and remove the marker. Transfer the slipped stitch back to the left needle being careful to not twist it. K2tog the returned stitch with the next stitch. *K2tog the yarn over with the stitch to the yarn over’s left, repeating up to the last yarn over.* (Do not work the last yarn over.) Turn.

Row 6 (WS): Slip 1 purl-wise. Purl to 1 stitch before the 2nd heel marker. Slip the stitch next to the marker knit-wise and remove the marker. Slip the next stitch (after the marker) knit-wise. Return the two slipped stitches back to the left needle, keeping the twist caused by the knit-wise slips. Purl the two slipped stitches together through the back loop (p2tog-tbl). *Slip 1 knit-wise, slip 1 knit-wise, slipping the yarn over and the stitch separately. Return the two slipped stitches to the left needle, keeping the twist caused by the knit-wise slips. P2tog-tbl.* Repeat up to the last yarn over. (Do not work the last yarn over.) Turn.

Back of the Heel

Row 7 (RS): *Slip 1 purl-wise, knit 1* up to the last heel stitch (the remaining yarn over). Slip the yarn over knit-wise. Knit 1 from the gusset. Pass over the slipped yarn over. Turn.

Row 8 (WS): Slip 1 purl-wise. Purl up to the last stitch heel stitch (the remaining yarn over). Slip the yarn over knit-wise and return it to the left needle. Purl 2 together (p2tog) the yarn over and 1 stitch from the gusset. Turn.

Row 9 (RS): *Slip 1 purl-wise, knit 1*, repeat this up to the last heel stitch. Slip the last stitch knit-wise. Knit 1 stitch from the gusset. Pass over the slipped stitch. Turn.

Row 10 (WS): Slip 1 purl-wise. Purl up to the last heel stitch. Purl 2 together (p2tog) the last heel stitch and the first gusset stitch. Turn.

Repeat Rows 9-10 until you have consumed all the gusset increases. You should have the same number as stitches as you did before you began the gusset.

Joining the Heel to the Body

1st Round after the Heel: Slip 1 purl-wise and knit across the heel stitches. With the sock heel facing you, you have a left and right side of the sock heel. The left side will not have a hole because of the slip earlier. After the heel, continue working the top of the sock in pattern up to the right side of the heel. (You have the top of your sock on your right needle and the right side of the heel on your left needle.) With your left needle, lift the left side of the stitch two stitches below the stitch on the right needle, moving for back to front. (I think of this as moving from left to right because the needle comes from the side, not the back of the work. Yes, this is like a lifted increase.) Slip the lifted leg knit-wise. Transfer the slipped stitch (the lifted leg) back to the left needle, keeping the twist. K2tog the lifted leg with the first heel stitch. This invisibly closes the hole between the top of the sock and the heel.

Related Posts:

• No Related Posts