honeyCMS Wiki & Documentation Rss Feed

Updated Wiki: Home

worldlifesite — Sat, 10 Jan 2009 01:37:54 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Create websites
Add Features to website(s) - see below
Apply themes
Apply widgets
Manage users
Manage features and data records
Test website before uploading to server
Setup Employee roles and user roles
Perform system maintainence
Run reports

The current features website Administrators can add to websites are:

Articles - Allow roles to add/edit/read articles
Forums - Allow roles to add/edit/read/delete forum posts/threads
Adnet - Add an advertising system to the website
Admin - A scaled down website admin for administrators away from thhe client application
Newsletters - Send Newsletters to users and maintain an online archive
Storefronts - Create storefronts to sale products
UserComm - Send alerts to user's via SMS, IM, desktop alerts, online website alerts for users that agree to receive them

Integration of Windows Live Services API is being adding to the application and other APIs are planned. The application will allow administrators to offer IM services for members; send alerts to members whether they're online or offline, offer social networking, and more. The goal is to have a high quality commercial grade open source CMS written for the .NET 3.5 platform. From a programmers perspective .NET technologies that the HoneyCMS application uses make coding quick and pretty painless.

Members that do join the development team will be able to access top of the line .NET development tools free of charge, a BizSpark licensing agreement is requirement prior to the downloading of these tools. Team membership will be limited to no more than 10 members. Each member will be given access to four websites (denoted by **):

1) http://www.microsoftstartupzone.com/pages/home.aspx HoneyCMS at BizSpark ** -

This website is a meeting place for venture capital and partners for the project.

2) http://www.honeycms.org Company Website ** -

Official landing website

3) http://workspace.office.live.com HoneyCMS Office Live Workspace ** -

This website is for meetings and document sharing outside of code files.

Other websites:

1) http://www.codeplex.com/honeyCMS HoneyCMS at Codex(this site)** -

This is the project code website, releases and change logs are here. Team members get access to upload code files, add issue/task items and start threads. Anyone can get a Codeplex account and that'll gain some editing access. For more information, see [CodePlex Basics: Getting Started

These sites will link to each other. Each site serves a different function. Eventually some sites will be integrated into one website.

Find out more about BizSpark at: http://www.microsoftstartupzone.com/pages/home.aspx.

This is an application with every intention of becoming a house hold name. HoneyCMS is planning to be the next evolution for content management systems. You can send an email with a link to your project website that contain sample projects and code, and why you want to join this project to HoneyCMSTeam@honeycms.org. Please include a tentative project work schedule. This project is being set up to eventually become a full time gig for team members. People of all ages, genders and ethnicities are encouraged to apply. Beginners, gurus, professionals and the occasional coders are also encouraged to apply. Team membership is open to US citizens. The company formation and some contracts for software licensing actually require this. International prospects are more than welcome to add webparts, masterpages and themes to the project when we reach that stage.

The goal of this project is to get TheBeerHouse Staterkit into a Drupal like format but, easier to update for non programmers or designers. The idea is to be a top notch .NET open source content management system that makes the work of end users and contributors such as designers and developers easy.

Updated Wiki: Home

worldlifesite — Sat, 10 Jan 2009 01:36:36 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Updated Wiki: Home

worldlifesite — Wed, 07 Jan 2009 16:37:44 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Updated Wiki: Home

worldlifesite — Mon, 29 Dec 2008 16:42:41 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Project Description
HoneyCMS is a Content Management Systemm akes it easier for end users, administrators, designers and developers to use and customize websites. Its a high quality, commercial grade application using the latest .NET development tools and techniques.

This project is currently in setup mode and only available to project coordinators and developers. This project originally was updating TheBeerHouse CMS into the HoneyCMS using ASP.NET AJAX tools. That, as of December 2008, has changed. This project will be a Windows client application for generating CMS websites.

The application will allow website administrators to design, develop and test the site on the pc side before uploading to the web server. This is similar to a website generator application only the code generated is for an ASP.NET 3.5 webserver content management System website. This model would make the HoneyCMS more powerful than a strickly website generated application.

For Admin, bandwidth to administer the website would be reduced. Also security would increase since Admin access comes from the pc side. The client authenticates before calling the server. More authentification protocals can be used. A scaled down website server side Admin of the wesbsite will be added that limits the administration of the website. Most websites are actually created on the client side and then uploaded to the server. This model is preferred by most website creators because of speed, bandwidth savings, pre-testing before uploading and more security to the web server's critical files. While on the road an administrator wouldn't need full administration access. HoneyCMS developers would be able to create targeted mobile Admin functioning.

Developers will be able to quickly add features to the HoneyCMS for the website application. Contributor's work can be made simplier. A Designer can design layout(tableless) in their favorite tools and offer it to the HoneyCMS community. Admin will search for new templates from the HoneyCMS application and select which ones to download. Developers can create plug ins that convert any tableless template into an ASP.NET masterpage and skin. XHTML is already done by the application but a contributor could create a Photoshop converter plug in. Developers would be able to easily allow administrators or any Role with content generator access to offer their content in PDF form (have you noticed that agencies and goverment sites love making their content .pdf or .htm(l)). This version of HoneyCMS offers far greator power than the strickly website administration version of the application.

Team Developers can write their plug-in tool(s) into the HoneyCMS Windows client application. Non Team developers can write server controls that Administrators will be able to add into their websites from a community search and download of selected server controls. Server controls are easy to create.

The web parts and webzones features are no longer needed as server controls are added instead. Team developers can quickly allow Adminstrators to change their website into one that allow users to use webparts. All they would have to do is create the plug-in code that has Admin features to converts website pages into the zones needed and convert thte server controls to parts. On the pc side its faster to open the files, add the code and then save the changes and test.

Having access to Windows APIs for the desktop will allow developers to offer far more robust functionality. For example, a developer can quickly add blogging features to the website using Windows Live Writer. The client and clients for users that have that access would quickly be written into HoneyCMS using the Windows Live Framework API. Administrators and anyone with that sort of access to the web application can post and pre post Articles or Blog content. Graphical functions can be down on the pc and thte finished product added to the server. HoneyCMS developers would be able to offer Administrators ways to develope movies, and other advanced graphics on the client and embedded into webpages and upload to the server without limits or resource greed that trying to do this sort of website administrative duties would present if Admin was strickly donw on the webserver where Admin would have to log in to do administration.

This Windows client application version of the HoneyCMS also allow Team developers to write code that support cloud computing systems. This offers far greater resource managability of server resources for website owners and more are moving to this type of server hosting setup. That make the application more poised for future web computing.

The generated CMS website will be an MVC web application.

The data model for the client HoneyCMs and the HoneyCMS generatoed CMS website will be an Entity Data Model, EDM. If you're familiar with DBA practices this is the conceptual level of data modeling for applications. An entity would be a customer or supplier, fields in a data table would represent properties of the entity. EDM has a Conceptual Data Definition Language (CSDL) and a Store Schema Definition Language (SSDL). Each is xml based.

The CSDL ties to program code and the SSDL represents actual data storage data definitions. CSDL and SSDL map together. This model allows a scenario where a flat file legacy system, a fifteen year old COM+ application and a modern SQL server base data store are all needed to generate application process logic and results data. They can all be used by one application. The CSDL deals with the business logic or business rules of the application and not the technical confinements of a particular data store. The SSDL converts the data store into a data definition that the CSDL will understand. So, regardless of the underlying data store technology, the actual application logic will not be affected, only business rule changes will change that area of the application. This makes the EDM data access model an object oriented data access model. When coupled with Linq to ADO.NET technologies data storage and/or business rule changes for the application will take a minimal effort to update. This means when ever data store changes occur only the SSDL needs to be updated. Business logic itself and business rules themselves would have to change in order for the CSDL to change. This is a model that is close to writing an application once where technological changes aren't greatly effecting the application to warrant a large scale application rewrite.

Integration of Windows Live Services API is being adding to the application and other APIs are planned. The application will allow administrators to offer IM services for members; send alerts to members whether they're online or offline, offer social networking, and more. The goal is to have a high quality commercial grade open source CMS written for the .NET 3.5 platform. From a programmers perspective .NET technologies that the HoneyCMS application uses make coding quick and pretty painless. Members that do join the development team will be able to access top of the line .NET development tools free of charge, a BizSpark licensing agreement is requirement prior to the downloading of these tools. Team membership will be limited to no more than 10 members. Each member will be given access to four websites (denoted by **):

1) http://www.microsoftstartupzone.com/pages/home.aspx HoneyCMS at BizSpark ** -

This website is a meeting place for venture capital and partners for the project.

2) http://www.honeycms.org Company Website ** -

Official landing website

3) http://workspace.office.live.com HoneyCMS Office Live Workspace ** -

This website is for meetings and document sharing outside of code files.

Other websites:

1) http://www.codeplex.com/honeyCMS HoneyCMS at Codex(this site)** -

This is the project code website, releases and change logs are here. Team members get access to upload code files, add issue/task items and start threads. Anyone can get a Codeplex account and that'll gain some editing access. For more information, see [CodePlex Basics: Getting Started

These sites will link to each other. Each site serves a different function. Eventually some sites will be integrated into one website.

Find out more about BizSpark at: http://www.microsoftstartupzone.com/pages/home.aspx.

This is an application with every intention of becoming a house hold name. HoneyCMS is planning to be the next evolution for content management systems. You can send an email with a link to your project website that contain sample projects and code, and why you want to join this project to HoneyCMSTeam@honeycms.org. Please include a tentative project work schedule. This project is being set up to eventually become a full time gig for team members. People of all ages, genders and ethnicities are encouraged to apply. Beginners, gurus, professionals and the occasional coders are also encouraged to apply. Team membership is open to US citizens. The company formation and some contracts for software licensing actually require this. International prospects are more than welcome to add webparts, masterpages and themes to the project when we reach that stage.

The goal of this project is to get TheBeerHouse Staterkit into a Drupal like format but, easier to update for non programmers or designers. The idea is to be a top notch .NET open source content management system that makes the work of end users and contributors such as designers and developers easy.

Updated Wiki: Home

worldlifesite — Thu, 18 Dec 2008 00:23:28 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Project Description
HoneyCMS is a Content Management Systemm akes it easier for end users, administrators, designers and developers to use and customize websites. Its a high quality, commercial grade application using the latest .NET development tools and techniques.

This project is currently in setup mode and only available to project coordinators and developers. This project originally was updating TheBeerHouse CMS into the HoneyCMS using ASP.NET AJAX tools. That, as of December 2008, has changed. This project will be a Windows client application for generating CMS websites.

The application will allow website administrators to design, develop and test the site on the pc side before uploading to the web server. This is similar to a website generator application only the code generated is for an ASP.NET 3.5 webserver content management System website. This model would make the HoneyCMS more powerful than a strickly website generated application.

For Admin, bandwidth to administer the website would be reduced. Also security would increase since Admin access comes from the pc side. The client authenticates before calling the server. More authentification protocals can be used. A scaled down website server side Admin of the wesbsite will be added that limits the administration of the website. Most websites are actually created on the client side and then uploaded to the server. This model is preferred by most website creators because of speed, bandwidth savings, pre-testing before uploading and more security to the web server's critical files. While on the road an administrator wouldn't need full administration access. HoneyCMS developers would be able to create targeted mobile Admin functioning.

Developers will be able to quickly add features to the HoneyCMS for the website application. Contributor's work can be made simplier. A Designer can design layout(tableless) in their favorite tools and offer it to the HoneyCMS community. Admin will search for new templates from the HoneyCMS application and select which ones to download. Developers can create plug ins that convert any tableless template into an ASP.NET masterpage and skin. XHTML is already done by the application but a contributor could create a Photoshop converter plug in. Developers would be able to easily allow administrators or any Role with content generator access to offer their content in PDF form (have you noticed that agencies and goverment sites love making their content .pdf or .htm(l)). This version of HoneyCMS offers far greator power than the strickly website administration version of the application.

Team Developers can write their plug-in tool(s) into the HoneyCMS Windows client application. Non Team developers can write server controls that Administrators will be able to add into their websites from a community search and download of selected server controls. Server controls are easy to create.

The web parts and webzones features are no longer needed as server controls are added instead. Team developers can quickly allow Adminstrators to change their website into one that allow users to use webparts. All they would have to do is create the plug-in code that has Admin features to converts website pages into the zones needed and convert thte server controls to parts. On the pc side its faster to open the files, add the code and then save the changes and test.

Having access to Windows APIs for the desktop will allow developers to offer far more robust functionality. For example, a developer can quickly add blogging features to the website using Windows Live Writer. The client and clients for users that have that access would quickly be written into HoneyCMS using the Windows Live Framework API. Administrators and anyone with that sort of access to the web application can post and pre post Articles or Blog content. Graphical functions can be down on the pc and thte finished product added to the server. HoneyCMS developers would be able to offer Administrators ways to develope movies, and other advanced graphics on the client and embedded into webpages and upload to the server without limits or resource greed that trying to do this sort of website administrative duties would present if Admin was strickly donw on the webserver where Admin would have to log in to do administration.

This Windows client application version of the HoneyCMs also allow Team developers to write code that support cloud computing systems. This offers far greater resource managability of server resources for website owners and more are moving to this type of server hosting setup. That make the application more poised for future web computing.

The data model for the client HoneyCMs and the HoneyCMS generatoed CMS website will be an Entity Data Model, EDM. If you're familiar with DBA practices this is the conceptual level of data modeling for applications. An entity would be a customer or supplier, fields in a data table would represent properties of the entity. EDM has a Conceptual Data Definition Language (CSDL) and a Store Schema Definition Language (SSDL). Each is xml based.

The CSDL ties to program code and the SSDL represents actual data storage data definitions. CSDL and SSDL map together. This model allows a scenario where a flat file legacy system, a fifteen year old COM+ application and a modern SQL server base data store are all needed to generate application process logic and results data. They can all be used by one application. The CSDL deals with the business logic or business rules of the application and not the technical confinements of a particular data store. The SSDL converts the data store into a data definition that the CSDL will understand. So, regardless of the underlying data store technology, the actual application logic will not be affected, only business rule changes will change that area of the application. This makes the EDM data access model an object oriented data access model. When coupled with Linq to ADO.NET technologies data storage and/or business rule changes for the application will take a minimal effort to update. This means when ever data store changes occur only the SSDL needs to be updated. Business logic itself and business rules themselves would have to change in order for the CSDL to change. This is a model that is close to writing an application once where technological changes aren't greatly effecting the application to warrant a large scale application rewrite.

Integration of Windows Live Services API is being adding to the application and other APIs are planned. The application will allow administrators to offer IM services for members; send alerts to members whether they're online or offline, offer social networking, and more. The goal is to have a high quality commercial grade open source CMS written for the .NET 3.5 platform. From a programmers perspective .NET technologies that the HoneyCMS application uses make coding quick and pretty painless. Members that do join the development team will be able to access top of the line .NET development tools free of charge, a BizSpark licensing agreement is requirement prior to the downloading of these tools. Team membership will be limited to no more than 10 members. Each member will be given access to four websites (denoted by **):

1) http://www.microsoftstartupzone.com/pages/home.aspx HoneyCMS at BizSpark ** -

This website is a meeting place for venture capital and partners for the project.

2) http://www.honeycms.org Company Website ** -

Official landing website

3) http://workspace.office.live.com HoneyCMS Office Live Workspace ** -

This website is for meetings and document sharing outside of code files.

Other websites:

1) http://www.codeplex.com/honeyCMS HoneyCMS at Codex(this site)** -

This is the project code website, releases and change logs are here. Team members get access to upload code files, add issue/task items and start threads. Anyone can get a Codeplex account and that'll gain some editing access. For more information, see [CodePlex Basics: Getting Started

These sites will link to each other. Each site serves a different function. Eventually some sites will be integrated into one website.

Find out more about BizSpark at: http://www.microsoftstartupzone.com/pages/home.aspx.

This is an application with every intention of becoming a house hold name. HoneyCMS is planning to be the next evolution for content management systems. You can send an email with a link to your project website that contain sample projects and code, and why you want to join this project to HoneyCMSTeam@honeycms.org. Please include a tentative project work schedule. This project is being set up to eventually become a full time gig for team members. People of all ages, genders and ethnicities are encouraged to apply. Beginners, gurus, professionals and the occasional coders are also encouraged to apply. Team membership is open to US citizens. The company formation and some contracts for software licensing actually require this. International prospects are more than welcome to add webparts, masterpages and themes to the project when we reach that stage.

The goal of this project is to get TheBeerHouse Staterkit into a Drupal like format but, easier to update for non programmers or designers. The idea is to be a top notch .NET open source content management system that makes the work of end users and contributors such as designers and developers easy.

Updated Wiki: Home

worldlifesite — Thu, 18 Dec 2008 00:19:09 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Project Description
HoneyCMS is a Content Management Systemm akes it easier for end users, administrators, designers and developers to use and customize websites. Its a high quality, commercial grade application using the latest .NET development tools and techniques.

This project is currently in setup mode and only available to project coordinators and developers. This project originally was updating TheBeerHouse CMS into the HoneyCMS using ASP.NET AJAX tools. That, as of December 2008, has changed. This project will be a Windows client application for generating CMS websites.

The application will allow website administrators to design, develop and test the site on the pc side before uploading to the web server. This is similar to a website generator application only the code generated is for an ASP.NET 3.5 webserver content management System website. This model would make the HoneyCMS more powerful than a strickly website generated application.

For Admin, bandwidth to administer the website would be reduced. Also security would increase since Admin access comes from the pc side. The client authenticates before calling the server. More authentification protocals can be used. A scaled down website server side Admin of the wesbsite will be added that limits the administration of the website. Most websites are actually created on the client side and then uploaded to the server. This model is preferred by most website creators because of speed, bandwidth savings, pre-testing before uploading and more security to the web server's critical files. While on the road an administrator wouldn't need full administration access. HoneyCMS developers would be able to create targeted mobile Admin functioning.

Developers will be able to quickly add features to the HoneyCMS for the website application. Contributor's work can be made simplier. A Designer can design layout(tableless) in their favorite tools and offer it to the HoneyCMS community. Admin will search for new templates from the HoneyCMS application and select which ones to download. Developers can create plug ins that convert any tableless template into an ASP.NET masterpage and skin. XHTML is already done by the application but a contributor could create a Photoshop converter plug in. Developers would be able to easily allow administrators or any Role with content generator access to offer their content in PDF form (have you noticed that agencies and goverment sites love making their content .pdf or .htm(l)). This version of HoneyCMS offers far greator power than the strickly website administration version of the application.

Team Developers can write their plug-in tool(s) into the HoneyCMS Windows client application. Non Team developers can write server controls that Administrators will be able to add into their websites from a community search and download of selected server controls. Server controls are easy to create.

The web parts and webzones features are no longer needed as server controls are added instead. Team developers can quickly allow Adminstrators to change their website into one that allow users to use webparts. All they would have to do is create the plug-in code that has Admin features to converts website pages into the zones needed and convert thte server controls to parts. On the pc side its faster to open the files, add the code and then save the changes and test.

Having access to Windows APIs for the desktop will allow developers to offer far more robust functionality. For example, a developer can quickly add blogging features to the website using Windows Live Writer. The client and clients for users that have that access would quickly be written into HoneyCMS using the Windows Live Framework API. Administrators and anyone with that sort of access to the web application can post and pre post Articles or Blog content. Graphical functions can be down on the pc and thte finished product added to the server. HoneyCMS developers would be able to offer Administrators ways to develope movies, and other advanced graphics on the client and embedded into webpages and upload to the server without limits or resource greed that trying to do this sort of website administrative duties would present if Admin was strickly donw on the webserver where Admin would have to log in to do administration.

The data model for the client HoneyCMs and the HoneyCMS generatoed CMS website will be an Entity Data Model, EDM. If you're familiar with DBA practices this is the conceptual level of data modeling for applications. An entity would be a customer or supplier, fields in a data table would represent properties of the entity. EDM has a Conceptual Data Definition Language (CSDL) and a Store Schema Definition Language (SSDL). Each is xml based.

The CSDL ties to program code and the SSDL represents actual data storage data definitions. CSDL and SSDL map together. This model allows a scenario where a flat file legacy system, a fifteen year old COM+ application and a modern SQL server base data store are all needed to generate application process logic and results data. They can all be used by one application. The CSDL deals with the business logic or business rules of the application and not the technical confinements of a particular data store. The SSDL converts the data store into a data definition that the CSDL will understand. So, regardless of the underlying data store technology, the actual application logic will not be affected, only business rule changes will change that area of the application. This makes the EDM data access model an object oriented data access model. When coupled with Linq to ADO.NET technologies data storage and/or business rule changes for the application will take a minimal effort to update. This means when ever data store changes occur only the SSDL needs to be updated. Business logic itself and business rules themselves would have to change in order for the CSDL to change. This is a model that is close to writing an application once where technological changes aren't greatly effecting the application to warrant a large scale application rewrite.

Integration of Windows Live Services API is being adding to the application and other APIs are planned. The application will allow administrators to offer IM services for members; send alerts to members whether they're online or offline, offer social networking, and more. The goal is to have a high quality commercial grade open source CMS written for the .NET 3.5 platform. From a programmers perspective .NET technologies that the HoneyCMS application uses make coding quick and pretty painless. Members that do join the development team will be able to access top of the line .NET development tools free of charge, a BizSpark licensing agreement is requirement prior to the downloading of these tools. Team membership will be limited to no more than 10 members. Each member will be given access to four websites (denoted by **):

1) http://www.microsoftstartupzone.com/pages/home.aspx HoneyCMS at BizSpark ** -

This website is a meeting place for venture capital and partners for the project.

2) http://www.honeycms.org Company Website ** -

Official landing website

3) http://workspace.office.live.com HoneyCMS Office Live Workspace ** -

This website is for meetings and document sharing outside of code files.

Other websites:

1) http://www.codeplex.com/honeyCMS HoneyCMS at Codex(this site)** -

This is the project code website, releases and change logs are here. Team members get access to upload code files, add issue/task items and start threads. Anyone can get a Codeplex account and that'll gain some editing access. For more information, see [CodePlex Basics: Getting Started

These sites will link to each other. Each site serves a different function. Eventually some sites will be integrated into one website.

Find out more about BizSpark at: http://www.microsoftstartupzone.com/pages/home.aspx.

This is an application with every intention of becoming a house hold name. HoneyCMS is planning to be the next evolution for content management systems. You can send an email with a link to your project website that contain sample projects and code, and why you want to join this project to HoneyCMSTeam@honeycms.org. Please include a tentative project work schedule. This project is being set up to eventually become a full time gig for team members. People of all ages, genders and ethnicities are encouraged to apply. Beginners, gurus, professionals and the occasional coders are also encouraged to apply. Team membership is open to US citizens. The company formation and some contracts for software licensing actually require this. International prospects are more than welcome to add webparts, masterpages and themes to the project when we reach that stage.

The goal of this project is to get TheBeerHouse Staterkit into a Drupal like format but, easier to update for non programmers or designers. The idea is to be a top notch .NET open source content management system that makes the work of end users and contributors such as designers and developers easy.

Updated Wiki: Home

worldlifesite — Wed, 17 Dec 2008 23:31:31 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

Project Description
HoneyCMS is a Content Management Systemm akes it easier for end users, administrators, designers and developers to use and customize websites. Its a high quality, commercial grade application using the latest .NET development tools and techniques.

This project is currently in setup mode and only available to project coordinators and developers. This project originally was updating TheBeerHouse CMS into the HoneyCMS using ASP.NET AJAX tools. That as of December 2008 has changed. This project will be a Windows client application for generating CMS websites.

The application will allow website administrators to design, develop and test the site on the pc side before uploading to the web server. This is similar to a website generator application only the code generated is for an ASP.NET 3.5 webserver. This model would make the HoneyCMS more powerful than a strickly website generated application.

For Admin bandwidth to administer the website would be reduced. Also security would increase since Admin access comes from the pc side. The client authenticates before calling the server. More authentification protocals can be used. A scaled down website server side Admin of the wesbsite will be added that limits the administration of the website. Most websites are actually created on the client side and then uploaded to the server. This model is preferred by most website creators because of speed, bandwidth savings, pre-testing before uploading and more security to the web server's critical files. While on the road an administrator wouldn't need full administration access. HoneyCMS developers would be able to create targeted mobile Admin functioning.

Developers will be able to quickly add features to the web application. They can plug in pre compiled code that admin can test on the pc sdie before uploading to the webserver. Having access to Windows APIs for the desktop will allow developers to offer far more robust functionality. For example, a developer can quickly add blogging features to the website using Windows Live Writer. The client and clients for users that have that access would quickly be written into HoneyCMS using the Windows Live Framework API. Administrators and anyone with that sort of access to the web application can post and pre post Articles or Blog content. Graphical functions can be down on the pc and thte finished product added to the server. HoneyCMS developers would be able to offer Administrators ways to develope movies, and other advanced graphics on the client and embedded into webpages and upload to the server without limits or resource greed that trying to do this sort of website administrative duties would present if Admin was strickly donw on the webserver where Admin would have to log in to do administration.

The data model will be an Entity Data Model, EDM. If you're familiar with DBA practices this is the conceptual level of data modeling for applications. An entity would be a customer or supplier, fields in a data table would represent properties of the entity. EDM has a Conceptual Data Definition Language (CSDL) and a Store Schema Definition Language (SSDL). Each is xml based.

The CSDL ties to program code and the SSDL represents actual data storage data definitions. CSDL and SSDL map together. This model allows a scenario where a flat file legacy system, a fifteen year old COM+ application and a modern SQL server base data store are all needed to generate application process logic and results data. They can all be used by one application. The CSDL deals with the business logic or business rules of the application and not the technical confinements of a particular data store. The SSDL converts the data store into a data definition that the CSDL will understand. So, regardless of the underlying data store technology, the actual application logic will not be affected, only business rule changes will change that area of the application. This makes the EDM data access model an object oriented data access model. When coupled with Linq to ADO.NET technologies data storage and/or business rule changes for the application will take a minimal effort to update. This means when ever data store changes occur only the SSDL needs to be updated. Business logic itself and business rules themselves would have to change in order for the CSDL to change. This is a model that is close to writing an application once where technological changes aren't greatly effecting the application to warrant a large scale application rewrite.

Integration of Windows Live Services API is being adding to the application and other APIs are planned. The application will allow administrators to offer IM services for members; send alerts to members whether they're online or offline, offer social networking, and more. The goal is to have a high quality commercial grade open source CMS written for the .NET 3.5 platform. From a programmers perspective .NET technologies that the HoneyCMS application uses make coding quick and pretty painless. Members that do join the development team will be able to access top of the line .NET development tools free of charge, a BizSpark licensing agreement is requirement prior to the downloading of these tools. Team membership will be limited to no more than 10 members. Each member will be given access to four websites (denoted by **):

1) http://www.microsoftstartupzone.com/pages/home.aspx HoneyCMS at BizSpark ** -

This website is a meeting place for venture capital and partners for the project.

2) http://www.honeycms.org Company Website ** -

Official landing website

3) http://workspace.office.live.com HoneyCMS Office Live Workspace ** -

This website is for meetings and document sharing outside of code files.

Other websites:

1) http://www.codeplex.com/honeyCMS HoneyCMS at Codex(this site)** -

This is the project code website, releases and change logs are here. Team members get access to upload code files, add issue/task items and start threads. Anyone can get a Codeplex account and that'll gain some editing access. For more information, see [CodePlex Basics: Getting Started

These sites will link to each other. Each site serves a different function. Eventually some sites will be integrated into one website.

Find out more about BizSpark at: http://www.microsoftstartupzone.com/pages/home.aspx.

This is an application with every intention of becoming a house hold name. HoneyCMS is planning to be the next evolution for content management systems. You can send an email with a link to your project website that contain sample projects and code, and why you want to join this project to HoneyCMSTeam@honeycms.org. Please include a tentative project work schedule. This project is being set up to eventually become a full time gig for team members. People of all ages, genders and ethnicities are encouraged to apply. Beginners, gurus, professionals and the occasional coders are also encouraged to apply. Team membership is open to US citizens. The company formation and some contracts for software licensing actually require this. International prospects are more than welcome to add webparts, masterpages and themes to the project when we reach that stage.

The goal of this project is to get TheBeerHouse Staterkit into a Drupal like format but, easier to update for non programmers or designers. The idea is to be a top notch .NET open source content management system that makes the work of end users and contributors such as designers and developers easy.

Updated Wiki: Job Types

worldlifesite — Tue, 16 Dec 2008 00:11:51 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - RoleTypes

FileName: XmlDataLists.xml

<?xml version="1.0" encoding="utf-8" ?>
<rootList>
<topList text="RoleTypes">
<listItem id="00" text="Admin" desc="Administration duties allow read/edit/add/delete access to application configuration and all records within the application"/>
<listItem id="01" text="AdminAssist" desc="Administration Asistant duties allow read/edit/add access to all records within the application"/>
<listItem id="02" text="RecordsAdmin" desc="Records Administrator duties allow read/edit/add/delete access to any record from Features within the application"/>
<listItem id="03" text="RecordsAdminAssist" desc="Records Administrator Assistant duties allow read/edit/add access to to any record from Features within the application"/>
<listItem id="04" text="Editor" desc="Editor duties allow read/edit/add/delete access to edit Articles/Categories/Comments on Articles of a user or group of users"/>
<listItem id="05" text="EditorAssist" desc="Editor Assistant duties allow read/edit/add access to edit Articles/Categories/Comments on Articles of a user or group of users"/>
<listItem id="06" text="CategoriesAdmin" desc="Categories Administrator duties allow read/edit/add/delete access to any category within the application"/>
<listItem id="07" text="CategoriesAdminAssist" desc="Categories Administrator Assistant duties allow read/edit/add to any category within the application"/>
<listItem id="08" text="Author" desc="Author duties allow read/edit/add/delete access to edit only that Author's Articles"/>
<listItem id="09" text="CommentsAdmin" desc="Comments Administrator duties duties allow read/edit/add/delete access to any comments within the application"/>
<listItem id="10" text="CommentsAdminAssist" desc="Comments Administrator Assistant duties allow read/edit/add access to any comments within the application"/>
<listItem id="11" text="ArticlesCommentor" desc="Articles Commentor duties allow read/edit/add access to read/edit/add/delete access to edit only that Commentor's Articles"/>
<listItem id="12" text="ForumsAdmin" desc="Forums Administrator duties allow read/edit/add/delete access to all Forums records within the application"/>
<listItem id="13" text="ForumsAdminAssist" desc="Forums Administrator Assistant duties allow read/edit/add access to all Forums records within the application"/>
<listItem id="14" text="ForumsCommentor" desc="Forums Commentor duties allow read/edit/add/delete access to edit only that Commentor's Forums posts"/>
<listItem id="15" text="PollsAdmin" desc="Polls Administrator duties allow read/edit/add/delete access to all Polls records within the application"/>
<listItem id="16" text="PollsAdminAssist" desc="Polls Administrator Assistant duties allow read/edit/add access to all Polls records within the application"/>
<listItem id="17" text="StoresAdmin" desc="Stores Administrator duties allow read/edit/add/delete access to configure Stores and all Store records"/>
<listItem id="18" text="StoresAdminAssist" desc="Stores Administrator Assistant duties allow read/edit/add access to Store records"/>
<listItem id="19" text="ProductsNewsAdmin" desc="Products News Administrator duties allow read/edit/add/delete access to all Products Newsletters records within the application"/>
<listItem id="20" text="ProductsNewsAdminAssist" desc="Products News Administrator Assistant duties allow read/edit/add access to all Products Newsletters records and Products NewsLetter configuration within the application"/>
<listItem id="21" text="ProductsNewsReader" desc="Products News Reader duties allow read access to all Products Newsletters records on the site and receives Products Newsletter emails"/>
<listItem id="22" text="SalesNewsAdmin" desc="Sales News Administrator duties allow read/edit/add/delete access to all Sales Newsletters records and Sales NewsLetter configuration within the application"/>
<listItem id="23" text="SalesNewsAdminAssist" desc="Sales News Administrator Assistant duties allow read/edit/add access to all Sales Newsletters records within the application"/>
<listItem id="24" text="SalesNewsReader" desc="Sales News Reader duties allow read access to all Sales Newsletters records on the site and receives Sales Newsletter emails"/>
</topList>
<listItem id="25" text="ProductsBuyer" desc="Products Buyer duties allow read/edit/add/delete access to that Buyer's order item records"/>
<listItem id="26" text="MembershipAdmin" desc="Membership Administrator duties allow read/edit/add/delete access to Advertisement configuration all Membership records within the application"/>
<listItem id="27" text="MembershipAdminAssist" desc="Membership Administrator Assistant duties allow read/edit access to all Membership records within the application"/>
<listItem id="28" text="Member" desc="Member duties allow read/edit/add/delete access to that Member's Membership records"/>
<listItem id="29" text="AdvertAdmin" desc="Advertisement Administrator duties allow read/edit/add/delete access to Advertisement configuration and all Advertiser's records within the application"/>
<listItem id="30" text="AdvertAdminAssist" desc="Advertisement Administrator Assistant duties allow read/edit access to all Advertiser's records within the application"/>
<listItem id="31" text="Advertiser" desc="Advertise duties allow read/edit/add/delete access to that Advertiser's records"/>

..

</rootList>
--------------------------------------------------------------------------------------------------------------------------------

This is the markup for the RoleTypes XML data list in the XmlDataLists.xml. This data list primarily fills a drop down or check box list control. The selection(s) is added to the database programmatically in a rolestypes field. the RolesTypes field will ocntain a concatination of the XML attributes rootList.topList.text.Value + rootList.topList.listItem.id.Value.

Membership Types (memtypes) are assigned Roles. What ever a Role has access to do, users of that Membership type will inherit as their access to the application.

Since users can be of multiple member type they can inherit mulitple Roles as well.

Admin will be able to add new roles and their access to the application. Since Roles are so important and determine what a user can do, only admin has access to this function. Certain Roles will not be modifiable because the system use them for internal functioning.

Updated Wiki: Job Types

worldlifesite — Tue, 16 Dec 2008 00:00:33 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - RoleTypes

FileName: XmlDataLists.xml

<?xml version="1.0" encoding="utf-8" ?>
<rootList>
<topList text="RoleTypes">
<listItem id="00" text="Admin" desc="Administration duties allow read/edit/add/delete access to application configuration and all records within the application"/>
<listItem id="01" text="AdminAssist" desc="Administration Asistant duties allow read/edit/add access to all records within the application"/>
<listItem id="02" text="RecordsAdmin" desc="Records Administrator duties allow read/edit/add/delete access to any record from Features within the application"/>
<listItem id="03" text="RecordsAdminAssist" desc="Records Administrator Assistant duties allow read/edit/add access to to any record from Features within the application"/>
<listItem id="04" text="Editor" desc="Editor duties allow read/edit/add/delete access to edit Articles/Categories/Comments on Articles of a user or group of users"/>
<listItem id="05" text="EditorAssist" desc="Editor Assistant duties allow read/edit/add access to edit Articles/Categories/Comments on Articles of a user or group of users"/>
<listItem id="06" text="CategoriesAdmin" desc="Categories Administrator duties allow read/edit/add/delete access to any category within the application"/>
<listItem id="07" text="CategoriesAdminAssist" desc="Categories Administrator Assistant duties allow read/edit/add to any category within the application"/>
<listItem id="083" text="Author" desc="Author duties allow read/edit/add/delete access to edit only that Author's Articles"/>
<listItem id="09" text="CommentsAdmin" desc="Comments Administrator duties duties allow read/edit/add/delete access to any comments within the application"/>
<listItem id="10" text="CommentsAdminAssist" desc="Comments Administrator Assistant duties allow read/edit/add access to any comments within the application"/>
<listItem id="11" text="ArticlesCommentor" desc="Articles Commentor duties allow read/edit/add access to read/edit/add/delete access to edit only that Commentor's Articles"/>
<listItem id="12" text="ForumsAdmin" desc="Forums Administrator duties allow read/edit/add/delete access to all Forums records within the application"/>
<listItem id="13" text="ForumsAdminAssist" desc="Forums Administrator Assistant duties allow read/edit/add access to all Forums records within the application"/>
<listItem id="14" text="ForumsCommentor" desc="Forums Commentor duties allow read/edit/add/delete access to edit only that Commentor's Forums posts"/>
<listItem id="15" text="PollsAdmin" desc="Polls Administrator duties allow read/edit/add/delete access to all Polls records within the application"/>
<listItem id="16" text="PollsAdminAssist" desc="Polls Administrator Assistant duties allow read/edit/add access to all Polls records within the application"/>
<listItem id="17" text="StoresAdmin" desc="Stores Administrator duties allow read/edit/add/delete access to configure Stores and all Store records"/>
<listItem id="18" text="StoresAdminAssist" desc="Stores Administrator Assistant duties allow read/edit/add access to Store records"/>
<listItem id="19" text="ProductsNewsAdmin" desc="Products News Administrator duties allow read/edit/add/delete access to all Products Newsletters records within the application"/>
<listItem id="20" text="ProductsNewsAdminAssist" desc="Products News Administrator Assistant duties allow read/edit/add access to all Products Newsletters records and Products NewsLetter configuration within the application"/>
<listItem id="21" text="ProductsNewsReader" desc="Products News Reader duties allow read access to all Products Newsletters records on the site and receives Products Newsletter emails"/>
<listItem id="22" text="SalesNewsAdmin" desc="Sales News Administrator duties allow read/edit/add/delete access to all Sales Newsletters records and Sales NewsLetter configuration within the application"/>
<listItem id="23" text="SalesNewsAdminAssist" desc="Sales News Administrator Assistant duties allow read/edit/add access to all Sales Newsletters records within the application"/>
<listItem id="24" text="SalesNewsReader" desc="Sales News Reader duties allow read access to all Sales Newsletters records on the site and receives Sales Newsletter emails"/>
</topList>
<listItem id="25" text="ProductsBuyer" desc="Products Buyer duties allow read/edit/add/delete access to that Buyer's order item records"/>
<listItem id="26" text="MembershipAdmin" desc="Membership Administrator duties allow read/edit/add/delete access to Advertisement configuration all Membership records within the application"/>
<listItem id="27" text="MembershipAdminAssist" desc="Membership Administrator Assistant duties allow read/edit access to all Membership records within the application"/>
<listItem id="28" text="Member" desc="Member duties allow read/edit/add/delete access to that Member's Membership records"/>
<listItem id="29" text="AdvertAdmin" desc="Advertisement Administrator duties allow read/edit/add/delete access to Advertisement configuration and all Advertiser's records within the application"/>
<listItem id="30" text="AdvertAdminAssist" desc="Advertisement Administrator Assistant duties allow read/edit access to all Advertiser's records within the application"/>
<listItem id="31" text="Advertiser" desc="Advertise duties allow read/edit/add/delete access to that Advertiser's records"/>
..

</rootList>
--------------------------------------------------------------------------------------------------------------------------------

This is the markup for the RoleTypes XML data list in the XmlDataLists.xml. This data list primarily fills a drop down or check box list control. The selection(s) is added to the database programmatically in a rolestypes field. the RolesTypes field will ocntain a concatination of the XML attributes rootList.topList.text.Value + rootList.topList.listItem.id.Value.

Membership Types (memtypes) are assigned Roles. What ever a Role has access to do, users of that Membership type will inherit as their access to the application.

Since users can be of multiple member type they can inherit mulitple Roles as well.

Updated Wiki: User Types

worldlifesite — Mon, 15 Dec 2008 22:47:58 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - User Types

FileName: XmlDataLists.xml

<?xml version="1.0" encoding="utf-8" ?>
<rootList>
<topList text="UserTypes">
<listItem id="00" text="Visitor" desc="User that is public and doesn't have a membership for log in access to the application."/>
<listItem id="01" text="Program" dewsc="User that is a program/bot that accesses the application."/>
<listItem id="02" text="Member" desc="User that has a membership account for log in access to a part of the application."/>
</topList>
..

</rootList>
--------------------------------------------------------------------------------------------------------------------------------

This is the markup for the UserTypes XML data list in the XmlDataLists.xml. This data list primarily fills a drop down or check box list control. The selection(s) is added to the database programmatically in a memtypes field. the MemTypes field will ocntain a concatination of the XML attributes rootList.topList.text.Value + rootList.topList.listItem.id.Value.

Everyone accessing the website is considered a User, whether the User is a Visitor, a Program or a Member that has to sign in to use the application.

There are only three types of Users; Visitor, Member or Program.

Visitors -

Visitors are users that visit the site and are not neccessarly members. If they sign up for anything they will become a member. Some visitors will come to the site to signup for the New Products or Sales newsletters only. Some will come to buy only, a option to receive the Sales or Products newsletter automatically will be offered to buyers but, not required. A visitor is any user to the site with access to the public pages. These users are automatically a part of the Public User Role.

Program -

This user is a bot that has access to the system. When a smart client is developed it will gain access under this user type. This user type is not added by administrators, its an internal type the developers use within the code. Other website code such as Windows Live will be this type of user. If a website developer decides to move the data SQL data store to cloud computing data services such as Azure, its reccommended that they design the code to make the service a program user type. This helps distinguish server to server or client code to server from user to server access to the application.

Member -

This type of user has sign in access. Administrators can create membership types such as a Silver member. There are membership types that are included with the application (which Admin can delete) such as Full-time Employee, Part-time Employee, Contractor, Affiliate, Paid Advertiser, Trail Member, Trail Advertiser, Free Member, NewsLetter Member, Editors, Writers, Administrator, Administrative Assistant. These membership types are held in an Membership Types XML data store. When a user is added the interface provides the type of membership available. Admin can assign a user to more than one membership. This is done to allow multiple access levels on a per user basis. The code will also assign membership types automatically based on the signup proccess. Once the user has a memberhip, the user will have access to add other types of memberships to their account.

For example a user may have only been interested in the newsletter but, later on decided to become a member to gain access to a part of the application that is members only. This same member may later on decide to advertise on the website and will be able to sign in and add the option to his/her membership account. That member will only have one sign in to access all of the application features for his/her various memberships.

Updated Wiki: User Types

worldlifesite — Mon, 15 Dec 2008 22:45:57 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - User Types

FileName: XmlDataLists.xml

Updated Wiki: XML Data Stores

worldlifesite — Mon, 15 Dec 2008 22:42:44 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data Stores

Configuration

Web.config

Menus

Admin Menu

Data Lists

Updated Wiki: Membership Types

worldlifesite — Mon, 15 Dec 2008 22:39:40 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - Membership Types

FileName: XmlDataLists.xml

<?xml version="1.0" encoding="utf-8" ?>
<rootList>
<topList text="MemTypes">
<listItem id="00" text="FTEmployee" desc="Member with Full Time Employee duties"/>
<listItem id="01" text="PTEmployee" desc="Member with Part Time Employee duties"/>
<listItem id="02" text="FTTempEmployee" desc="Member with Temporary Full Time Employee duties"/>
<listItem id="03" text="PTTempEmployee" desc="Member with Temporary Part Time Employee duties"/>
<listItem id="04" text="Affiliate" desc="Member with Affiliate level access"/>
<listItem id="05" text="SuperAffiliate" desc="Member with Super Affiliate level access"/>
<listItem id="06" text="Contractor" desc="Member with Contractor duties"/>
<listItem id="07" text="Advertiser" desc="Member with Advertiser level access"/>
<listItem id="08" text="TrailAdvertiser" desc="Member with Trail Advertiser level access"/>
<listItem id="09" text="TrailMember" desc="Member with Trail level access"/>
<listItem id="10" text="FreeMember" desc="Member with Free level access"/>
<listItem id="11" text="SilverMember" desc="Member with Silver level access"/>
<listItem id="12" text="GoldMember" desc="Member with Gold level access"/>
<listItem id="13" text="PlatinumMember" desc="Member with Platinum level access"/>
<listItem id="14" text="StoreBuyer" desc="Member that buys an item from the online store(s) integrated with the application"/>
<listItem id="15" text="NewsletterMember" desc="Member with access to receive and view online newsletters that require membership"/>
</topList>

..

</rootList>
--------------------------------------------------------------------------------------------------------------------------------

This is the markup for the MemTypes XML data list in the XmlDataLists.xml. This data list primarily fills a drop down or check box list control. The selection(s) is added to the database programmatically in a memtypes field. the MemTypes field will ocntain a concatination of the XML attributes rootList.topList.text.Value + rootList.topList.listItem.id.Value.

There are different types of memberships that a User can have. One User can have more than one membership type.

For example a StoreBuyer may also be a GoldMember and a Newsletter Member. This same member may become an advertiser later on. As long as the membership type is in good standings the member will use one log in to access all parts of the system he/she has membership access to.

Admin has an option to assign memberships on a per user basis. This is done because administrators may have the need or desire to add a user to a membership without the signup process. This can occur when administrators offer a user and not a role a special deal for some reason.

Administrators can assisgn memberships on a role base as well. For example, administrators may want to offer Super Affiliates a Platinum membership to the Articles database or Trail Advertising access as a reward.

Note: There are plans to include code that allow website administrators to join the HoneyCMS AdNetwork. This is an unobtrusive link on a few key pages that all HoneyCMS (and others eventually) will have placed on key pages to rotate link ads from the HoneyCMS AdNetwork. As an incentive for greator signups to the HoneyCMS AdNetwork website administrators can earn free credits per nth number of impressions of the HoneyCMS Adnetwork links on their website. Administrators can take these credits and sell them to others on their website (integrated with the application, no need to edit webpages) or use them for their own advertising on the HoneyCMS AdNetwork. There are other advertising options for Administrators to choose for their application.

Updated Wiki: Membership Types

worldlifesite — Mon, 15 Dec 2008 22:06:12 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - Membership Types

FileName: XmlDataLists.xml

<?xml version="1.0" encoding="utf-8" ?>
<rootList>
<topList text="MemTypes">
<listItem id="00" text="FTEmployee" desc="Member with Full Time Employee duties"/>
<listItem id="01" text="PTEmployee" desc="Member with Part Time Employee duties"/>
<listItem id="02" text="FTTempEmployee" desc="Member with Temporary Full Time Employee duties"/>
<listItem id="03" text="PTTempEmployee" desc="Member with Temporary Part Time Employee duties"/>
<listItem id="04" text="Affiliate" desc="Member with Affiliate level access"/>
<listItem id="05" text="SuperAffiliate" desc="Member with Super Affiliate level access"/>
<listItem id="06" text="Contractor" desc="Member with Contractor duties"/>
<listItem id="07" text="Advertiser" desc="Member with Advertiser level access"/>
<listItem id="08" text="TrailAdvertiser" desc="Member with Trail Advertiser level access"/>
<listItem id="09" text="TrailMember" desc="Member with Trail level access"/>
<listItem id="10" text="FreeMember" desc="Member with Free level access"/>
<listItem id="11" text="SilverMember" desc="Member with Silver level access"/>
<listItem id="12" text="GoldMember" desc="Member with Gold level access"/>
<listItem id="13" text="PlatinumMember" desc="Member with Platinum level access"/>
</topList>

..

</rootList>
--------------------------------------------------------------------------------------------------------------------------------

Everyone accessing the website is considered a User, whether the User is a Visitor, a Program or a Member that has to sign in to use the application.

There are only three types of Users; Visitor, Member or Program.

Visitors -

Visitors are users that visit the site and are not neccessarly members. If they sign up for anything they will become a member. Some visitors will come to the site to signup for the New Products or Sales newsletters only. Some will come to buy only, a option to receive the Sales or Products newsletter automatically will be offered to buyers but, not required. A visitor is any user to the site with access to the public pages. These users are automatically a part of the Public User Role.

Program -

This user is a bot that has access to the system. When a smart client is developed it will gain access under this user type. This user type is not added by administrators, its an internal type the developers use within the code. Other website code such as Windows Live will be this type of user. If a website developer decides to move the data SQL data store to cloud computing data services such as Azure, its reccommended that they design the code to make the service a program user type. This helps distinguish server to server or client code to server from user to server access to the application.

Member -

This type of user has sign in access. Administrators can create membership types such as a Silver member. There are membership types that are included with the application (which Admin can delete) such as Full-time Employee, Part-time Employee, Contractor, Affiliate, Paid Advertiser, Trail Member, Trail Advertiser, Free Member, NewsLetter Member, Editors, Writers, Administrator, Administrative Assistant. These membership types are held in an XMl data store. When a user is added the interface provides the type of membership available. Admin can assign a user to more than one membership. This is done to allow multiple access levels on a per user basis. The code will also assign membership types automatically based on the signup proccess. Once the user has a memberhip, the user will have access to add other types of memberships to their account.

For example a user may have only been interested in the newsletter but, later on decided to become a member to gain access to a part of the application that is members only. This same member may later on decide to advertise on the website and will be able to sign in and add the option to his/her membership account. That member will only have one sign in to access all of the application features for his/her various memberships.

Updated Wiki: Membership Types

worldlifesite — Mon, 15 Dec 2008 21:40:18 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

XML Data List - Membership Types

FileName: XmlDataLists.xml

--------------------------------------------------------------------------------------------------------------------------------

Everyone accessing the website is considered a User, whether the User is a Visitor, a Program or a Member that has to sign in to use the application.

There are only three types of Users; Visitor, Member or Program.

Visitors -

Visitors are users that visit the site and are not neccessarly members. If they sign up for anything they will become a member. Some visitors will come to the site to signup for the New Products or Sales newsletters only. Some will come to buy only, a option to receive the Sales or Products newsletter automatically will be offered to buyers but, not required. A visitor is any user to the site with access to the public pages. These users are automatically a part of the Public User Role.

Program -

This user is a bot that has access to the system. When a smart client is developed it will gain access under this user type. This user type is not added by administrators, its an internal type the developers use within the code. Other website code such as Windows Live will be this type of user. If a website developer decides to move the data SQL data store to cloud computing data services such as Azure, its reccommended that they design the code to make the service a program user type. This helps distinguish server to server or client code to server from user to server access to the application.

Member -

This type of user has sign in access. Administrators can create membership types such as a Silver member. There are membership types that are included with the application (which Admin can delete) such as Full-time Employee, Part-time Employee, Contractor, Affiliate, Paid Advertiser, Trail Member, Trail Advertiser, Free Member, NewsLetter Member, Editors, Writers, Administrator, Administrative Assistant. These membership types are held in an XMl data store. When a user is added the interface provides the type of membership available. Admin can assign a user to more than one membership. This is done to allow multiple access levels on a per user basis. The code will also assign membership types automatically based on the signup proccess. Once the user has a memberhip, the user will have access to add other types of memberships to their account.

For example a user may have only been interested in the newsletter but, later on decided to become a member to gain access to a part of the application that is members only. This same member may later on decide to advertise on the website and will be able to sign in and add the option to his/her membership account. That member will only have one sign in to access all of the application features for his/her various memberships.

Updated Wiki: User Table

worldlifesite — Mon, 15 Dec 2008 21:28:37 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

User Table

dbo.hcms_User

Everyone accessing the website is considered a User, whether the User is a Visitor, a Program or a Member that has to sign in to use the application.

There are only three types of Users; Visitor, Member or Program.

Visitors -

Visitors are users that visit the site and are not neccessarly members. If they sign up for anything they will become a member. Some visitors will come to the site to signup for the New Products or Sales newsletters only. Some will come to buy only, a option to receive the Sales or Products newsletter automatically will be offered to buyers but, not required. A visitor is any user to the site with access to the public pages. These users are automatically a part of the Public User Role.

Program -

This user is a bot that has access to the system. When a smart client is developed it will gain access under this user type. This user type is not added by administrators, its an internal type the developers use within the code. Other website code such as Windows Live will be this type of user. If a website developer decides to move the data SQL data store to cloud computing data services such as Azure, its reccommended that they design the code to make the service a program user type. This helps distinguish server to server or client code to server from user to server access to the application.

Member -

This type of user has sign in access. Administrators can create membership types such as a Silver member. There are membership types that are included with the application (which Admin can delete) such as Full-time Employee, Part-time Employee, Contractor, Affiliate, Paid Advertiser, Trail Member, Trail Advertiser, Free Member, NewsLetter Member, Editors, Writers, Administrator, Administrative Assistant. These membership types are held in an Membership Types XML data store. When a user is added the interface provides the type of membership available. Admin can assign a user to more than one membership. This is done to allow multiple access levels on a per user basis. The code will also assign membership types automatically based on the signup proccess. Once the user has a memberhip, the user will have access to add other types of memberships to their account.

For example a user may have only been interested in the newsletter but, later on decided to become a member to gain access to a part of the application that is members only. This same member may later on decide to advertise on the website and will be able to sign in and add the option to his/her membership account. That member will only have one sign in to access all of the application features for his/her various memberships.

Updated Wiki: User Table

worldlifesite — Mon, 15 Dec 2008 21:24:59 GMT

User's Guide	Technical Documentation	Contribute
User Accounts	System Requirements	Designers
Tutorials	Application Documentation	Developers

=====================================================================

User Table

dbo.hcms_User

Everyone accessing the website is considered a User, whether the User is a Visitor, a Program or a Member that has to sign in to use the application.

There are only three types of Users; Visitor, Member or Program.

Visitors -

Visitors are users that visit the site and are not neccessarly members. If they sign up for anything they will become a member. Some visitors will come to the site to signup for the New Products or Sales newsletters only. Some will come to buy only, a option to receive the Sales or Products newsletter automatically will be offered to buyers but, not required. A visitor is any user to the site with access to the public pages. These users are automatically a part of the Public User Role.

Program -

This user is a bot that has access to the system. When a smart client is developed it will gain access under this user type. This user type is not added by administrators, its an internal type the developers use within the code. Other website code such as Windows Live will be this type of user. If a website developer decides to move the data SQL data store to cloud computing data services such as Azure, its reccommended that they design the code to make the service a program user type. This helps distinguish server to server or client code to server from user to server access to the application.

Member -

This type of user has sign in access. Administrators can create membership types such as a Silver member. There are membership types that are included with the application (which Admin can delete) such as Full-time Employee, Part-time Employee, Contractor, Affiliate, Paid Advertiser, Trail Member, Trail Advertiser, Free Member, NewsLetter Member, Editors, Writers, Administrator, Administrative Assistant. These membership types are held in an XMl data store. When a user is added the interface provides the type of membership available. Admin can assign a user to more than one membership. This is done to allow multiple access levels on a per user basis. The code will also assign membership types automatically based on the signup proccess. Once the user has a memberhip, the user will have access to add other types of memberships to their account.

For example a user may have only been interested in the newsletter but, later on decided to become a member to gain access to a part of the application that is members only. This same member may later on decide to advertise on the website and will be able to sign in and add the option to his/her membership account. That member will only have one sign in to access all of the application features for his/her various memberships.