Re: [WebDNA] Webdna and CMS
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108073
interpreted = N
texte = > 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. >=20 > Lawrence Hi Lawrence,=20 It is a noble impulse. =20 =46rom where to start? =46rom 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=3DT&like=3DT&this=3DT' - 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=
Associated Messages, from the most recent to the oldest:
> 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. >=20 > Lawrence Hi Lawrence,=20 It is a noble impulse. =20 =46rom where to start? =46rom 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=3DT&like=3DT&this=3DT' - 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=
Govinda
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
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...
Related Readings:
typhoon... (1997)
Search-context (1999)
2.0 Info (1997)
Dreamweaver and WebDNA (2003)
ANNC: Cool New WebCat Site!!! (Lotsa Flash) (2000)
[WebDNA] Sending emails (2010)
WCS Newbie question (1997)
Wierd quantities (2000)
Email Set-Up? (1997)
RE: File Uploads (1998)
9 digit zip (2002)
[UPPERCASE] (1997)
Not really WebCat (1997)
WebCat2 - [include] tags (1997)
Bug alert! (1997)
WebDelivery downloads alias, not original ? (1997)
[protect admin] (1997)
300 ticks (2003)
Kaaaaahhhhhhhnnnnnnn! (1997)
Ok here is a question? (1997)