--------------020108030803070809090202Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg"Content-Transfer-Encoding: base64Content-ID:
Govinda
11 janvier 2012 17:09
Hi Lawrence,
It is a noble impulse.
From where to start? From where you are! You could spend time studying existing CMS(es) like WP or Joomla (or many others), to learn more the thought processes that went into those things (and that is probably really a good idea unless it would overwhelm and squelch your impulse)... and/or you could just start coding and learn the mistakes more from finding out first hand. Either way you will discover things just as/when you discover them... you know what I mean? Just keep focused and do. Pondering can only go so far. Most will come from doing, whether that doing is focused study, or writing code.
Several thoughts come to mind.. at least these few for just starters:
--------------- from the code/coder's perspective -------------
- Be flexible and prepared to re-write a lot of code. One thing will lead to another.. will lead to another.. there is amazingly more things to consider than one thinks of at first. If you are not sure you up to the task, and are asking what is involved, then it means there will especially be more involved than you had originally thought. But this is not to discourage you. You will learn so much, and like all creative endeavors, have *something in hand* at the end, not to mention if it gets to be even useful for others :-) .
- MVC design will save vast amounts of maintenance headache; separation of logic from presentation (separate the webdna from the HTML/CSS/JS that spits out to the browser as much as possible).
- modularized design of functions. Re-use code. Keep it DRY, and easy to maintain.
- clear consistent code style with contexts indenting each other, so everything is readable and easy to see the logic, easy to see any context within the context of its parent context. Use white space and comments well too.
- good db design/normalization for efficient use of RAM/resources
- don't trust anything the user can affect in any way. Not negative or fear-based.. but in the name of security... filter/clean/validate *everything* the user can touch (including the hacker user)... form submits (POST), URL param-manipulation (GET), cookies, [thisurl], and more... security is an always-expanding topic, so have a maximally-conservative attitude.. and in case of any doubt then go the extra mile to protect you and the honest users.
--------------- from the end-users' perspective ----------------
- SEO-friendly URLs, so that file paths 'mysite.com/end/up/like/this.html', as opposed to 'mysite.com/end.html?up=T&like=T&this=T'
- graceful enhancement with javascript/CSS/HTML5 as opposed to broken features when lesser/dumbed-down client software us used.
***
This is a huge topic.. So for now I'll just stop with these few thoughts to get you going.
-Govinda---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
Banahan
11 janvier 2012 11:48
Hi,
I read that a lot of you have build their own CMS.
So I'm now thinking building my own, but I don't know were to start with and if I have the knowledge to do so...
I would like to do something halfway between Wordpress and Joomla.
What tips could you give me were to start from.
If some of you would be interested, maybe we could build something and give it for free at the community...
Up to my opinion, I think a "good" CMS could help to get new web designer to use Webdna.
Lawrence
|
--------------020108030803070809090202Content-Type: image/jpeg; x-apple-mail-type=stationery; name="compose-unknown-contact.jpg"Content-Transfer-Encoding: base64Content-ID:
Govinda
11 janvier 2012 17:09
Hi Lawrence,
It is a noble impulse.
From where to start? From where you are! You could spend time studying existing CMS(es) like WP or Joomla (or many others), to learn more the thought processes that went into those things (and that is probably really a good idea unless it would overwhelm and squelch your impulse)... and/or you could just start coding and learn the mistakes more from finding out first hand. Either way you will discover things just as/when you discover them... you know what I mean? Just keep focused and do. Pondering can only go so far. Most will come from doing, whether that doing is focused study, or writing code.
Several thoughts come to mind.. at least these few for just starters:
--------------- from the code/coder's perspective -------------
- Be flexible and prepared to re-write a lot of code. One thing will lead to another.. will lead to another.. there is amazingly more things to consider than one thinks of at first. If you are not sure you up to the task, and are asking what is involved, then it means there will especially be more involved than you had originally thought. But this is not to discourage you. You will learn so much, and like all creative endeavors, have *something in hand* at the end, not to mention if it gets to be even useful for others :-) .
- MVC design will save vast amounts of maintenance headache; separation of logic from presentation (separate the webdna from the HTML/CSS/JS that spits out to the browser as much as possible).
- modularized design of functions. Re-use code. Keep it DRY, and easy to maintain.
- clear consistent code style with contexts indenting each other, so everything is readable and easy to see the logic, easy to see any context within the context of its parent context. Use white space and comments well too.
- good db design/normalization for efficient use of RAM/resources
- don't trust anything the user can affect in any way. Not negative or fear-based.. but in the name of security... filter/clean/validate *everything* the user can touch (including the hacker user)... form submits (POST), URL param-manipulation (GET), cookies, [thisurl], and more... security is an always-expanding topic, so have a maximally-conservative attitude.. and in case of any doubt then go the extra mile to protect you and the honest users.
--------------- from the end-users' perspective ----------------
- SEO-friendly URLs, so that file paths 'mysite.com/end/up/like/this.html', as opposed to 'mysite.com/end.html?up=T&like=T&this=T'
- graceful enhancement with javascript/CSS/HTML5 as opposed to broken features when lesser/dumbed-down client software us used.
***
This is a huge topic.. So for now I'll just stop with these few thoughts to get you going.
-Govinda---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
Banahan
11 janvier 2012 11:48
Hi,
I read that a lot of you have build their own CMS.
So I'm now thinking building my own, but I don't know were to start with and if I have the knowledge to do so...
I would like to do something halfway between Wordpress and Joomla.
What tips could you give me were to start from.
If some of you would be interested, maybe we could build something and give it for free at the community...
Up to my opinion, I think a "good" CMS could help to get new web designer to use Webdna.
Lawrence
DOWNLOAD WEBDNA NOW!
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...