My website might help some people?

[TheBadger]

Hi I have no idea if I am allowed to do this here but I have just finished creating 3 tutorials on ADC, USART and Bluetooth on PICs.

I really don't care about traffic so if this isn't allowed feel free to remove it I was just thinking people might like to read them, plus I wouldnt mind someone telling me how crap they are as I haven't had any testers yet.

S.O.R is my only link in my "links" section as I get most of my help from here.

So yeah if you want to check it out its at www.eeworld.co.uk

[Soeren]

Hi,

I wouldnt mind someone telling me how crap they are as I haven't had any testers yet.

Nice site, but a couple of things spring to mind.
Photos: Keep them relevant (i.e. don't post them unless they help move the story forward). Put them on the site (using flickr doesn't look too pro). Make schematics large enough to read.

Intra-Links: Only place them when there actually is content - following a link to a text like "someday there will be content here" is a surefire way to avoid return visitors.

The generally accepted formula attracting return visitors is: Content, Navigation and look/feel (in exactly that order).

Not meant put you down! Overall you have a nice start.

[TheBadger]

Not at all put me down, thanks for the feedback!

I like using Flickr as my main host for photos, maybe I could take the hyperlinks off the photos so they look like they are embedded on the site.

When you say the photos should only move the story forward which photos are you talking about as the site is split between tutorials and blog, in the tutorial sections I didn't think I had used enough photos.

That schematic I couldn't figure out how to make big, but now I can just forgot to change it, will do now.

*edit
I have now taken all the links from the photos in the tutorial sections, I thought it wouldn't matter in the blog section as then the user might get access to the flickr albums and look at the other photos, plus blogs are informal, but it did look naff in the tutorials section to have flickr links.

[rbtying]

Wrap all the code you post in styled "< pre >" or "< code >" blocks (remove spaces) - syntax highlighting would be good as well.  It makes it much easier to read, and simpler to copy & paste. 

For ex:

This is easier to recognize as code:

Code: [Select]

void func1() { doSomething(); }
than this:

void func1() {doSomething(); }

[TheBadger]

I couldn't get syntax highlighting to work but I have made the code highlighted from the rest of the text.

What do you think?

[Gertlex]

Nice. I had not realized that putty could be used for COM ports.

[rbtying]

I couldn't get syntax highlighting to work but I have made the code highlighted from the rest of the text.

What do you think?

Install this: http://wordpress.org/extend/plugins/wp-syntax/ <-- You're running wordpress, take advantage of it.

[TheBadger]

I did install that but it sent all my C18 code wrong, as it isnt proper C its microchips C.

or I did something stupid

[rbtying]

You should at least be able to get basic things highlighted - variable types, functions, command structures, etc.  It's alright if C18 commands aren't highlighted, but the flow of a program is much easier to decipher when highlighting is enabled. 

[Gertlex]

On the topic of highlighting, I will briefly hijack.  If you're using Firefox, you can use the HighlightAll add-on and thus make code anywhere more readable as needed
https://addons.mozilla.org/en-us/firefox/addon/highlightall/

/hijack