Jump to content

WANTED! Webpage, CMS for web building newbies


vikingkiller

Recommended Posts

.

Request - WANTED! preferably alive

 

The web is full of tutors for HTML, CSS, XML etc. There is tons of it. But, take this as a free hint to get readers to your webdesign homepage. This is what at least some like to read... but there isn't anything about this on the web. This is a fri tips!

 

Tutor on understanding principles of CMS's (for webdesign w. GNU /GPL CMS's)

Write small or an extensive tutor for (make a lean webpage with links to deeper explainations):

Generic understanding of principles to webdesign with open CMS's U could also use an example CMS (make sure it's kind of mainstream cms) but then relate to how most other CMS's work and why. There are lots of step by step tutors for different CMS's out there but they do not make reason or understanding. So, aim at understanding generic principles!

 

Chapters could be:

 

# Cms features. CMS with in line admin or non linear. Does it matter? Which features are critical for the implementation of a template, or a self made webpage?

 

# I found a nice template. How to think and what to look for to implement it into a normal CMS. Tags, codes, what are they and what do I need to know?

 

# Does all CMS allow any template? Why? Why not?

 

# Must my template be changed to fit my choosen CMS? Where do I find codes and tags to do it?

 

# Words and expressions. Modules, extensions, plugins. How do they connect to the core? Is a module only 1 webpage? Templates, themes what are they and do all cms's use the terms in same manner? Why?

 

# What is a good contents module? What is needed, and what is mumbo jumbo?

 

# If I make my own webpage to implement into a CMS. Should I make it just as an oldfashion stand alone HTML page and there after divide it into HTML and CSS ...or should i make it in some special structure?

 

# What do I need to maintain the website and keep it secure?

 

....that is some ideas folks. I guess a good "principles of webdesign with CMS" would be equal to perhaps 3 - 10 legal pages. What R U waiting fore, do U know thiese things, start your writing now! It will be appreciated, I promise.

 

.

Edited by vikingkiller
Link to comment
Share on other sites

I think the concept he is trying to do is to have a generic tutorial/documentation about CMS that would apply to about any type of CMS software but that would be virtually impossible because no one CMS are alike except the software is loaded onto your host, has admin access, can update/add new pages/articles, add-ons, etc.

 

Base on the questions he's given so far, it's not very concise and seems to be amateurish. Finally, he didn't indicate an link (unless the link was removed by a mod) or to PM him or if we are to start a new forum in this regard.

Edited by newseed
Link to comment
Share on other sites

I started reading and decided it was Spam... but then again Thelma and a couple advanced members did not so I bow to the majority... I thought it was another "read my article" type of thing.

 

And Thelma? Don't go getting any ideas about me bowing before you more often... :D

Link to comment
Share on other sites

And Thelma? Don't go getting any ideas about me bowing before you more often... :D
OK - I won't :P

 

I first thought it looked like spam, too - but there was no actual link or even a product name. Mostly, it read like nonsense, but I wanted to give the dude the benefit of the doubt.

Link to comment
Share on other sites

Hey, love U're answers!

 

 

What is and what is not?

Most or every serious open CMS has some kind of step-by-step guide for implementing templates /themes. Unfortunately those instructions in most cases are hurt by:

a) missing steps

B) high level native (english or php, etc) expressions that make it impossible to understand

c) so long and tedious that anyone or everyone get lost reading it.

 

A small tutor on how to understand the generic process of setting ut a webpage would definitely help reading bad tutors for each CMS.

 

 

Misunderstandings

All CMS's are NOT different. :rolleyes: At a micro level naturally every cms is different, they are nor compatible or clones... But at a task oriented level they all do the same things like integrating a HTML code and CSS formate etc into publishing a content and members /community administration center. Yes they use slightly different approaches to do this but the main task, which is close related to the generic principles still remains.

 

 

For short

One could say that that a generic cms principles walkthrough should be used for pre understanding before reading any of the established cms's webpage implementation instructions to read them with more "understanding eyes" so to say.

 

 

Perhaps this should be moved to the cms departement.

 

.

Edited by vikingkiller
Link to comment
Share on other sites

Hey, love U're answers!

 

 

What is and what is not?

Most or every serious open CMS has some kind of step-by-step guide for implementing templates /themes. Unfortunately those instructions in most cases are hurt by:

a) missing steps

B) high level native (english or php, etc) expressions that make it impossible to understand

c) so long and tedious that anyone or everyone get lost reading it.

 

A small tutor on how to understand the generic process of setting ut a webpage would definitely help reading bad tutors for each CMS.

You just can't do a 'generic' documentation on how to implement a template to a CMS because each CMS is different on how a template is implemented. For example: Joomla template implementation is different from CMS Made Simple. Also, both are coded differently if you were to incorporated one of your own personal design and so you have to take totally different approah for each one.

 

Misunderstandings

All CMS's are NOT different. :rolleyes: At a micro level naturally every cms is different, they are nor compatible or clones... But at a task oriented level they all do the same things like integrating a HTML code and CSS formate etc into publishing a content and members /community administration center. Yes they use slightly different approaches to do this but the main task, which is close related to the generic principles still remains.

This type of 'generic' documentation will end up being more confusing than each of the original software documentation.

 

Since you have so much passion for this, why don't you take a crack at it yourself and provide the 'generic' documentation for review?

 

 

For short

One could say that that a generic cms principles walkthrough should be used for pre understanding before reading any of the established cms's webpage implementation instructions to read them with more "understanding eyes" so to say.

 

Get us started by providing 3-4 examples and we will test them by applying them to our favorite CMS.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...