Re: [WebDNA] CMS in WEBDNA

This WebDNA talk-list message is from

2009


It keeps the original formatting.
numero = 101881
interpreted = N
texte = Michael A. DeLorenzo wrote: > My eCommerce Edition has "CMS Builder". What's the difference from CMS in > Enterprise? No difference between editions, except that you can't enter/use a built CMS with the commerce edition. For that matter...how is SiteBuilder different from CMS and CMS > Builder? I know the difference from template design and content management > but is there a comparison somewhere we can look at? Or maybe a quick > "overview" of all of the tools so we know which one will be most useful. > Also, which of these have encrypted templates and which do not. I noticed > CMS in the developer version has them encrypted. It would be nice to know > what we can control and what we can not. Sorry for all the questions. I > never used any "out-of-the-box" functionality that came with WebDNA. I > usually built it all from scratch....but hey, why reinvent the > wheel....right? I've read the docs but it the description of each tool is > rather vague. > > Mike Yes, CMS and SiteBuilder are very different and used for different things. SiteBuilder is a way to create websites and commerce functions quickly. CMS does not deal with that at all. CMS is a way to manage your source code robustly, and to edit files online. You can see how these two (separate) purposes may work well together. Thus, SMSI built in a function that lets you include the sitebuilder files when building a CMS. Now you have the best of both worlds (so to speek). You don't have to manage SiteBuilder files with a CMS of course, and it would be more probable to use the CMS for other things. store.webdna.us contains all the info for the features in each edition. However, I could see a use for some kind of graphic or table that shows the differences in brief. We'll work on that. Donovan -- Donovan D. Brooke PH: 1 (608) 770-3822 ------------------------------------------------ VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] CMS in WEBDNA (Stuart Tremain 2009)
  2. Re: [WebDNA] CMS in WEBDNA (Donovan Brooke 2009)
  3. Re: [WebDNA] CMS in WEBDNA (Stuart Tremain 2009)
  4. Re: [WebDNA] CMS in WEBDNA (Donovan Brooke 2009)
  5. Re: [WebDNA] CMS in WEBDNA ("Dan Strong" 2009)
  6. RE: [WebDNA] CMS in WEBDNA ("Michael A. DeLorenzo" 2009)
  7. Re: [WebDNA] CMS in WEBDNA (Donovan Brooke 2009)
  8. Re: [WebDNA] CMS in WEBDNA (Donovan Brooke 2009)
  9. Re: [WebDNA] CMS in WEBDNA (Donovan Brooke 2009)
  10. Re: [WebDNA] CMS in WEBDNA (Bert 2009)
  11. Re: [WebDNA] CMS in WEBDNA (Stuart Tremain 2009)
  12. [WebDNA] CMS in WEBDNA (lawrence@authorsimage.com 2009)
Michael A. DeLorenzo wrote: > My eCommerce Edition has "CMS Builder". What's the difference from CMS in > Enterprise? No difference between editions, except that you can't enter/use a built CMS with the commerce edition. For that matter...how is SiteBuilder different from CMS and CMS > Builder? I know the difference from template design and content management > but is there a comparison somewhere we can look at? Or maybe a quick > "overview" of all of the tools so we know which one will be most useful. > Also, which of these have encrypted templates and which do not. I noticed > CMS in the developer version has them encrypted. It would be nice to know > what we can control and what we can not. Sorry for all the questions. I > never used any "out-of-the-box" functionality that came with WebDNA. I > usually built it all from scratch....but hey, why reinvent the > wheel....right? I've read the docs but it the description of each tool is > rather vague. > > Mike Yes, CMS and SiteBuilder are very different and used for different things. SiteBuilder is a way to create websites and commerce functions quickly. CMS does not deal with that at all. CMS is a way to manage your source code robustly, and to edit files online. You can see how these two (separate) purposes may work well together. Thus, SMSI built in a function that lets you include the sitebuilder files when building a CMS. Now you have the best of both worlds (so to speek). You don't have to manage SiteBuilder files with a CMS of course, and it would be more probable to use the CMS for other things. store.webdna.us contains all the info for the features in each edition. However, I could see a use for some kind of graphic or table that shows the differences in brief. We'll work on that. Donovan -- Donovan D. Brooke PH: 1 (608) 770-3822 ------------------------------------------------ VP WebDNA Software Corporation 16192 Coastal Highway Lewes, DE 19958 Donovan Brooke

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:

[WebDNA] [arrayset name=array_1&dim=X,Y,Z] Margins (2012) Drop Down Menus (2002) Math with Time (1997) WebCatalog can't find database (1997) absolute paths for databases? (1997) [WebDNA] mod_WebDNA_apache2.2.so: mach-0, but wrong architecture (2010) [WebDNA] How to code a 301 redirect (2008) Fun with Dates - revisited (1997) Some Questions (1997) WebCommerce: Folder organization ? (1997) Multiple Newcarts (1996) Webcatalog error, Plug-in for Webstar (1996) ODBC to WebCat (2000) Bug or syntax error on my part? (1997) Re:PCS Customer submissions ? (1997) Trouble with formula.db + more explanation (1997) date range (1998) Not reading code (1997) [GROUPS] followup (1997) logging in a user (1999)