North American Mission Board, SBC Content Management Solution Request for Proposal

businessunknownInternet and Web Development

Nov 12, 2013 (3 years and 9 months ago)

125 views

Sitecore & ADCIEO Response to



North American Mission Board, SBC

Content Management Solution

Request for Proposal









P
repared by:
William Sapp

Phone
336
-
370
-
9119

Fax
415
-
380
-
0730

Email
wms@sitecore.net





Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



2

7
.

Vendor Narrative Response



1.

Full company name and
business address

Sitecore USA, Inc.

591 Redwood Highway, Bldg. #4000

Mill Valley,
CA 94941

United States

(415) 380 0600

2.

Number of years company
has been in business

10

3.

Corporation name,
partnership name, or names
of private holders

Sitecore

4.

State of Incorporation

Sitecore is a privately held, multi
-
national company
headquartered in Copenhagen, Denmark with sales, marketing,
engineering and support offices in the United States, United

Kingdom, Sweden, Australia, Netherlands and Germany.

5.

Number of employees

150+

6.

Annual sales revenue

Sitecore is positioned to
see a 50% increase in staff over the next year, while looking at the same for profits.


For additional
financial information pertaining to Sitecore, Sitecore would request a Non
-
disclosure Agreement to be put in place
with

your organization

and Sitecore.


Sitecore would expedite this process upon knowledge of advancement to the next
stage in

your

organization’s

v敮dor s敬散瑩tn pro捥ssK

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
3


7.

Brief Company history

Sitecore began in the mid
-
nineties with strong software development team implementing contempor
ary web content
management solutions for customers throughout Denmark. In 1998, Sitecore became an independent software vendor
(ISV), forgoing any implementation services and solely focusing on the development of Sitecore’s content management
platform.

Sit
ecore is the leader in developing and maintaining the most advanced pure .NET web content management and portal
platform in the industry. Sitecore V6, the company’s current flagship product, is the

sixth generation of Sitecore’s web
content management and
portal platform and technology. Since the company’s beginning, Sitecore’s team has focused on
leveraging Microsoft’s technology platforms and in 2002 they introduced the first pure .NET web content management and
portal platform. Today, Sitecore continues
its leadership with Sitecore V6 and the aggressive, ongoing product roadmap.




8.

Is your company currently
involved in any litigation in
which an adverse decision
might result in a material
change in the company’s
financial position or future
viability?


No

9.

To your knowledge, are there
any negotiations regarding
any acquisitions involving
your company?

No

10.

Are you a public or private
corporation?

Stock symbol, if publicly
traded


Private


Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



4



8.

Core Requirements

and Vendor Response




Requirement

NAMB Comment

Vendor Response

1.

The proposed CMS solution should be
operational with data migrated from existing
CMS (Kintera Sphere) solution before
12/31/2009

Minimal customization will be
requested beyond what is
required for migration of
content
and retain or enhance existing
functionality. The 12/31/2009
date is critical. An evaluation of
the existing site (
www.namb.net
)
and review of the attached site list
should aid in determining the
appropriate leve
l of effort.

The assumption should be that
only Kintera based content will
need to be migrated and existing
click
-
thru’s and integrations will
b攠r整慩e敤K Th攠on攠數捥p瑩tn
w楬氠l攠瑨攠r数污捥men琠tf th攠
䭩h瑥t愠Co䴠w楴h th攠kA䵂
hos瑥t 䵓jCo䴮

䵥整猠數pe
捴慴楯nsI 敳e散楡汬y w楴h 數p敲瑩s攠from 䅄䍉AlI 汥l by
䑥an楳 Chyb愬 form敲
卖p

of Kintera as Sitecore’s implementation
p慲瑮敲K

Add楴楯n慬asuppor琠楳⁡汳t 慶慩污l汥l瑯 migr慴攠from 䭩n瑥t愠Co䴠瑯
䵓jCo䴮

䅬Ao on s瑡ff w楴h AaCfb传楳 th攠form敲 Co䴠produc

m慮ag敲 for 䭩n瑥t愮

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
5



8.

Core Requirements

and Vendor Response



2.

The proposed CMS solution should provide a
toolset that allows the end
-
users
(departments) to update and manage their
own site content publishing/updates via
workflow and approvals. The toolset should
allow for the reuse of any
existing
functionality that is present anywhere in the
CMS.

This is a critical component.
Once rights and privileges are
determined, this group of users
will need to be able to manage
their own sites or pages with little
assistance. The expectation is that

the proposed CMS will be
conducive to distributed content
management. This user base is
not highly technical so ease of
use is important.

Developer
involvement should not be
required for basic site
maintenance and modifications.

Editorial content can be
managed via a number of editing interfaces,
each differing in sophistication, thereby ensuring appropriate
learning curves for different types of users.


Font, color, text position, images and other styling options can be
made available to content editors

should they be required.

The great thing with Sitecore is that the styling options can be
tailored to the content item level (e.g. job title, job description) and
locked down by user and/or style sheets.

Ad slot, banners and buttons can be easily added
into content layouts
by a user with a few clicks of the mouse (subject to permissions).
These components would have been pre
-
wrapped as Sitecore
renderings by a developer, and would subsequently be available
potentially anywhere in the site, or across mult
iple sites, if required.

Meta data, keywords and 3rd party tags can be content managed by
the Sitecore CMS at the content item level.


Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



6


8.

Core Requirements

and Vendor Response



3.

Webmaster Training

1. Primary CMS vendor point of
contact

2. NAMB overall site
management/privileges

3. CMS functiona
lity; as
appropriate

4. Content upload and page
modification tool use

William Sapp

wms@sitecore.net

336
-
370
-
9119

We provide an extensive, tiered developer training program which is
obligatory for our partners and
available to your company so you can
choose to develop or extend your Sitecore solution in house.


4.

Departmental CMS User Training

1. Content upload and page
modification tool use

2. CMS functionality; as
appropriate

Provided either online through Sitec
ore or by ADCIEO

in custom
training onsite.

5.

The proposed CMS solution should be hosted
externally with complete support and an
acceptable service level agreement.



Several options exist.
ADCIEO will
present these options for review
and approved.

6.

Hosting facility meets SAS70 Type II
Requirements


All proposed options meet SAS70 Type II certification requirements

7
.

Migration
of all content from existing
solution

(Kintera

Sphere
) into recom
mended
solution will be provided as part of proposed
solut
ion
.


ADCIEO will provide

migration of the current content into Sitecore.

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
7



8.

Core Requirements

and Vendor Response



8
.

Initial setup of templates with design and
layout supplied by NAMB; though CMS
solution specific recommendations and
lessons learned are encouraged.


ADCIEO will

share best practices on
the application of templates
provide by NAMB and then incorporate these templates into
Sitecore.

9
.

Ability to integrate with 3
rd

party video
content delivery service(s) directly or via
click thru.


The creation of links pointing

to externally stored streaming audio
and video content or Podcasting feeds is completely supported by
Sitecore.


Sitecore currently has several customers that have
integrated the CMS with Media Servers for the sorting of video and
audio assets.


In this i
mplementation, as noted above, users are
accessing these assets via the Sitecore UIs even though the items are
not being stored in the CMS database.


Additionally, those items
stored in the Media Server can also possess the same attributes as
managed conte
nt.


These include security permissions, workflow,
and versioning.

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



8


8.

Core Requirements

and Vendor Response



10
.

Ability to integrate with a 3
rd

party
ecommerce/merchant service(s) directly or
via click thru.


Sitecore is built on trusted open standards such as XML and Web
Services and as such
integration with 3
rd

part systems is easily
achieved.

There are numerous implementations of Sitecore where integrations
with 3
rd

party systems was key, some examples:

Science Museum


in瑥gr慴楯n w楴h ov敲 U d楦f敲敮琠汥g慣y sys瑥ms
using 卩p散or攠瑯 provi
d攠愠p污瑦orm on wh楣h 瑯 數pos攠瑨楳 捯n瑥t琠
on汩l攮

卩p散or攮n整e


fu汬⁩l瑥tr慴楯n w楴h 䵩jrosof琠to䴠aynami捳c
慬汯wing 瑨攠man慧emen琠tf p楴散ir攠r敳eur捥s 瑯 p慲瑮敲sI
d敶敬ep敲s 慮d 捵s瑯m敲s 慬氠through th攠w敢s楴攮

䑯汬慲 o敮琠A C慲


散omm敲捥 楮t
敧r慴楯n hand汩ng th攠book楮g
慮d p慹men琠tf 捡r r敮瑡汳K

䵡n捨es瑥t 啮楴敤


楮瑥tr慴aon w楴i memb敲sh楰 m慮agem敮琠
system handling and supporting all Manchester United’s online
memb敲sK

fn 瑥tms of paym敮琠g慴away in瑥tr慴楯nI su捨 as tor汤m慹I Amfs
慲攠
provided which can be used in conjunction with Sitecore’s
數瑥tsiv攠Amf 瑯 慬汯w s敡m汥ss 捯
-
op敲慴楯nK



S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
9


9
.

General

Requirements

and Vendor Response

This section lists NAMB’s performance requirements and the required proposal content
.
Please list your answers in the Vendor Response column.




#

Performance Requirement

Agreed

No
t
Agreed

Vendor Response

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



10

.

Compliance with web standards as defined by the W3C,
including CSS used for layout wherever appropriate




卩S散or攠s楴敳 慣h楥i攠愠h楧h l敶敬eof W3C 慮d 慣捥ss楢楬楴y 捯mp汩ln捥, 愠
r散敮琠卩瑥捯r攠pow敲敤 s楴攠慴瑲慣瑥t 愠W3C r慴楮g of 䅁A, wh楣h 楳 he汤
by 汥ss than 1┠%f g汯b慬as楴is.

卩S散or攠f敡瑵res bu楬i
-
in, un楱u攠慣捥ss楢楬楴y 瑯o汳 in捬ud楮g
p慴敮t
-
p敮ding
us慢楬楴y v慬楤慴楯n 慢楬楴楥s addr敳e楮g 慣捥ss楢楬ity, 捯n瑥n琠tomp汩ln捥 and
qu慬楴y enfor捥men琠ton捥rns. Th敳攠bu楬i
-
in 捡p慢楬楴楥猠me整em慮y
m慮d慴敤 go慬s 慮d s瑡nd慲ds, such 慳aADA 508 慮d WC䅇A wh楣h prov楤攠
gu楤敬enes for 瑨攠捲敡
瑩tn of w敢si瑥猠th慴a慲攠慣捥ss楢汥l瑯 p敯p汥lw楴h
d楳慢楬楴楥献iThey 慬獯 en慢汥lbr慮d 慮d 捯n瑥t琠tons楳瑥ncy 敮for捥men琠for
org慮楺慴楯ns th慴ahav攠污lg攠numb敲s of w敢s楴攠捯n瑲楢u瑯rs.


Th攠慣捥ss楢楬楴y v慬楤慴ar shows 捬敡r ind楣慴irs when 捯n瑥tt

do敳o琠
m敥琠獴tnd慲ds, 慮d 楮 many c慳敳 捡n fix 瑨攠prob汥m 慵瑯m慴楣a汬y.


Image


Accessibility Built In





Image


Automation of Error Fixi
ng




Example Site



DVLA ha
s unveiled its new corporate website, delivered by Eduserv, a not
-
for
-
profit IT services group serving the public sector, and powered by a
Sitecore Content Management System.


The DVLA website is visited by 1,000,000 people per week and provides
essential
information for all driving
license

holders and vehicle keepers in
the UK.


Sitecore’s .NET web content management software enables the rapid
d敶敬epm敮琠tf 敡s楬y 敤楴慢汥 fn瑥tn整esi瑥猠慮d w敢
-
b慳敤 慰p汩捡瑩lnsK

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
11


2
.

Content database should be a standards
-
based
protocol, allowing direct manipulation or the use
of data transformation service as necessary for
import, export, etc.





Microsoft SQL Server, MySQL, SQLite and Oracle.

3.

Workflow system to allow at least one level of review of
content before publishing, multiple levels preferred,
including user
-
based queues and email notifications to
multiple parties to report workflow progress/status.

Note: Solution should allow NAMB to

modify as needed.
There must be the ability to review history of content and
to revert to a previous state.




Sitecore provides an extremely flexible workflow engine for the building,
managing, and supporting any work requirement.

These include but are
not
limited to branched, parallel, and looped workflows, as well as the flexible
support for creating and supporting custom workflow rules.

Sitecore has
several customers that have created specific rules to follow FDA, WAI, SEO,
and HIPPA rules and complia
nce standards.


Also, Sitecore has used its workflow engine as an integration point with
several other applications such as translation services vendors, as well as,
document management applications such as SharePoint.


Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



12

4.

Ability to create ad
-
hoc content

forms based on existing
contact data [currently in NAMB.net], allowing all email
interaction to come through forms on the site and the
removal of all visible email addresses from the Web site.



Forms functionality can be achieved out of the box by using Web Forms for
Marketers module.



The Web Forms for Marketers module is designed to create simple forms in
a blink of an eye and in a friendly manner. The module can be configured so
that forms h
ave only a few adjustable parameters thus making the user
interface as simple as possible. For instance, the basic options cover the most
frequent needs of a regular web site editor such as creating basic input fields
(text boxes, checkboxes), basic action
s (save to a database, send an email)
and basic validators (RequiredField validator, Email address validator, etc.).

Form designers can include a confirmation page, which is configurable and
any information saved to the database can be reported on, and ex
ported in a
variety of formats including Excel, as an aspx file.

Image


Create a New Form




More complex forms can be developed based on a form generated by this
module. There is an option to convert the form into a sublayout (.ascx file),
so that de
velopers can edit this sublayout using common development tools
like Visual Studio.






Editors benefit from the easy drag and drop of standard .Net
webcontrols. Also, an array of widely used functions can be applied to the
forms created.





Creating a form goes into 5 steps:

o


Select the Sitecore node where you require the form

o


Click on the Forms Editor button to start the editor

o


Design the form using drag and drop of controls and positioning them in
their desired places.

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
13


5
.


NAMB’s core contact database infrastructure is Microsoft
CRM (MSCRM) hosted at our Alpharetta GA office.


1.

All contact data obtained through forms, logins, etc.,
must integrate with this system. Any contact data
required for any form or Web functional
ity should reside
in the MSCRM and accessed real
-
time or via a batch
processing based on the specific type of data being
accessed by CMS.


2.

A means of accessing MSCRM data should be
possible through standard, custom and/or pre
-
defined
reporting tools.




Sitecore provides open APIs for the integration of data from/to other CRM
technologies.


Sitecore also provides a web services layer for more flexibility
extensions for developers.


Currently, Sitecore has customers with
integrations with Sales Force,
Pivotal CRM, Microsoft Dynamics, Sales
Logic, ACT, Seibel, and more.

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



14

6
.

Ability to connect to other data sources.




As one of the first content management providers to adopt Microsoft’s .NET
瑥捨no汯gyI 卩瑥捯r攠C䵓j楳 ab汥l瑯 汥l敲慧攠瑨攠䵩jrosof琠w敢
s敲v楣敳i
s瑲慴敧y 瑯 捯nn散琠tnform慴楯nI p敯p汥l sys瑥ms and d敶楣敳K 卩p散or攠off敲s
愠hos琠tf t敢s敲v楣is 楮瑥gr慴楯n 瑯o汳 瑯 bu楬i 捯nn散瑩tns b整w敥n
慰p汩捡瑩lnsI 楮g敳琠捯n瑥t琬t慳 w敬氠as s敲v攠捯n瑥t琠瑯 ex瑥tn慬asys瑥msK

卩p散or攠s瑯r敳⁡nd work
s w楴h 慬氠of 楴i 捯n瑥n琠ts 塍iK To f慣楬楴慴攠
楮瑥gr慴楯n w楴h ex瑥tn慬ad慴慢慳攠sys瑥msI 卩瑥捯r攠off敲s th攠䑡瑡 mrov楤敲
慢s瑲慣瑩tn iay敲K Th楳 giv敳ed敶敬ep敲s 愠s瑡td慲d楺敤 way 瑯 數pos攠
d慴慢慳攠捯nn散瑩tns 瑯 卩p散or攠so 瑨ey 捡n 慣捥ss thos攠da
t慢慳敳 慮d
r散ords 慳⁩a 瑨ey w敲攠simp汥l塍i do捵men瑳K Th楳 s瑲敡ml楮敳e
d敶敬epm敮琠tnd 慬汯ws d敶敬op敲s 瑯 汥l敲慧攠瑨攠瑲emendous pow敲 of
塐慴a 慮d 塓iK

A汬⁣on瑥t琠w楴h楮 卩p散or攠楳 s瑯r敤 楮 愠s瑲u捴ur敤 mann敲 in s瑡nd慲d 塍i
form慴a 卩p散or攠
f敡瑵r敳⁢u楬琠楮 瑯o汳 for 數por琠tnd impor琠of 捯n瑥t琮t
Sitecore’s package designer lets the developer select content and files to
d楳瑲楢u瑥t瑯 o瑨敲 s敲v敲sI 攮gK from 愠d敶敬epmen琠獥tv敲 瑯 瑨攠produ捴楯n
敮v楲onmen琮tTh攠p慣k慧攠d敳楧n敲 prov楤敳⁡
gr敡琠t敡氠lf f汥l楢楬楴y on
how dev敬ep敲s org慮楺攬 s敬e捴c慮d p慣k慧攠捯n瑥n琬t捯d攠慮d d慴愠for
d楳瑲楢u瑩tnK



Image


Content Export Packager








Advanced options enable user’s to filter items by date of creation,
modif楣慴楯nI 捯n瑥n琠tr敡瑯r 整挮 m慣k慧攠d敦in楴楯ns 捡n b攠s慶
敤 for futur攠
use and combined with the use of Sitecore’s scheduler can also be
慵瑯m慴敤K

卩p散or攠so汵瑩tns 慲攠䅓AK久T app汩捡瑩lns 慮d 瑨敲efor攠suppor琠
imp汥m敮瑡瑩tn in 慮y K久T suppor琠污ngu慧攬 such 慳⁃# or 噩su慬a
S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
15


7
.

Ability to allow users to lookup and display information
by location, segmentation, etc. Applications would
include a “Church Search” feature and
missionary lookup
pages. This information may or may not reside in
MSCRM




Sitecore fully supports the searching capabilities of content and media assets
via the metadata properties associated with each item. Sitecore also supports
full text content
search.


Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



16

8
.


Ability to import large groups of existing html pages as an
.xml file. Example: 500 news stories in an index could be
imported with elements for <title>, <summary>, <date>
and <body> (for the html page content itself).




䑥D敮d楮g on th攠
qu慮t楴y and sour捥 of 瑨攠捯n瑥n琠w攠h慶攠s敶敲慬a
op瑩tns⽡/pro慣h敳e




††

䵡nu慬aimpor琠楳⁳u楴慢汥 wh敮 w攠hav攠愠sma汬ⁱuan瑩ty of 捯n瑥n琠
慮d⽯r wh敮 捯n瑥t琠ts uns瑲uc瑵r敤. Con瑥n琠t慮 b攠捯py p慳瑥a 楮瑯
卩S散or攧猠euthor楮g 敮v楲onm敮琠ty hand
.



If sour捥 捯n瑥t琠ts r敬慴楶ely s瑲u捴cr敤 慮d⽯r 楳 pr敳敮琠楮 污lg攠
qu慮瑩t楥猠w攠捡n imp汥men琠t 捵s瑯m impor瑥t. Th楳 楳 don攠by
imp汥m敮t楮g .久T 捬慳c敳⁡nd us楮g 卩瑥捯r攧s API w楴h 瑯o汳 for 捯n瑥t琠
impor瑡瑩tn. API 瑯o汳 楮捬cde 慮 I䐠慮d ID
T慢汥lm慮ag敲 wh楣h manag攠
瑨攠m慰ping b整w敥n key f楥ids from th攠sour捥 捯n瑥n琠tnd 楴im I䑳⁩D th攠
卩S散or攮 W楴i 瑨敳攠瑯o汳 w攠捡n mon楴ir 瑨攠impor瑡瑩tn of 捯n瑥t琠tnd
r敲un 瑨攠migr慴楯n pro捥ss wi瑨ou琠f敡r of dup汩捡瑥l 楴ims. Th楳 m整hod 楳
敳ee
捩慬cy su楴慢汥lwhen migr慴楮g 捯n瑥n琠trom oth敲 sys瑥ms v楡iw敢
s敲v楣敳ⰠAPIs or d楲散瑬t from 瑨攠und敲lying sour捥, for 數amp汥lfrom 愠
r敬慴楯n慬ad慴慢慳攮



佰琠tor 楮瑥tr慴楯n r慴h敲 瑨慮 migr慴楯n by imp汥men瑩ng 愠捵s瑯m d慴愠
sour捥. Arch楴散is c
慮 d整敲min攠瑨攠汥v敬eof in瑥gr慴楯n 攮g. fu汬r jus琠t敡d
-
only. In瑥gr慴楯n is don攠by imp汥men瑩ng 愠捬慳c wh楣h inh敲楴i from
䑡瑡卯ur捥 捬慳s



䵩Mr慴楯n 却牡瑥ty

·


䑹nam楣iP䡐 p慧敳ewou汤 b攠m慰p敤 瑯 pr敳敮瑡瑩tn 捯mponen瑳
(慳ax, 慳捸 and
xs汴⁰慧敳⤮

·


HT䵌 s瑡瑩挠p慧es wou汤 b攠migr慴敤 慳⁣on瑥n琯t慴愠楴ims.

·


P䑆⁆楬敳 捡n 敩瑨敲 b攠impor瑥t 楮瑯 瑨攠m敤楡i汩lr慲y or 捯py p慳瑥a
楮瑯 捯n瑥n琠楴tm f楥汤s. Images wou汤 b攠migr慴敤 楮瑯 瑨攠m敤楡i汩lr慲y 慮d
C卓 f楬is 捡n

敩eh敲 b攠impor瑥t 楮瑯 瑨攠m敤楡i汩lr慲y or simply p污捥d on瑯
瑨攠f楬攠sys瑥m.


S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
17


9
.

Search tool, allowing search of main site and search of all
sites within account.




Sitecore fully supports the searching capabilities of content and media assets
via
the metadata properties associated with each item. Sitecore also supports
full text content search.


10
.

Sitemap tool that works dynamically, updating itself
based on published pages. Tool should allow exclusion of
any pages.




Sitecore provides this out

of the box

11.

Ability to implement Google Analytics or other web
metrics tools.




Sitecore provides this ability via the Sitecore pre
-
built module, StatsCenter.


The StatsCenter Module provides customers with the ability to view the total
hits of the
site, the number of unique hits of the site, and the number of
unique visitors of the site.


All of this information can be provided based on a
specific time frame.


The StatsCenter Module also provides customers with
the specific visitor information such
as name, domain, URL, etc.


If a more
robust statistical application is required, Sitecore can easily be integrated
with the analytical package of each customer’s choice seamlessly.


These
include 3rd party tools such as WebTrends (who is a current Sitecor
e
customer), WebSideStory, Google Analytics, OmniTure, etc.


1
2
.

Provide automated RSS feeds and the ability to incorporate
and format external RSS feeds into pages.




Yes, Sitecore provides an RSS module for the creation, management and
syndication of
RSS.

1
3
.

Photo galleries that automatically create thumbnails,
ability to download full files, and allow display of
metadata in preview screens.




Yes, Sitecore provides a photo gallery module that provides this capability

18.

Polling functionality, for

simple “instant” polls with
online reporting of results available to user.







Included

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



18

19
.

Default URLs should follow a conventional folder
structure for maximum search
-
engine optimization.






卩S散or攠慵瑯m慴楣慬iy ou瑰uts m敡n楮gfu氠human r敡d慢汥

啒Ls g敮敲慴敤
from 捯n瑥n琠楴tm nam敳⸠Th楳 f敡瑵r攠慬so mak敳⁴h攠w敢s楴敳⁥慳楥a 瑯
捲aw氠lnd 楮d數 for s敡r捨 敮gin敳⸠啒Ls usu慬ly 捬csely repr敳敮琠瑨攠
website’s tree structure. If we consider the following site structure for
數amp汥:



Th攠啒i 瑯 瑨攠produ捴猠would b攠
h瑴t㨯⽤oma楮⽐rodu捴献慳px
I 瑨攠啒i 瑯
瑨攠b慴瑥a楥猠i慧攠wou汤 b攠
h瑴t㨯⽤oma楮⽐rodu捴猯A捣essor楥猯䵩獣敬污n敯us⽂慴瑥ayKaspx

慮d so onK

卩p散or攠慬獯 敮慢汥猠慵瑨ors to s整e慬楡獥a for 捯mmon w敢s楴敳K
Admin楳瑲慴ar 捯u汤 s整eup 慬楡猠aor 瑨攠慲瑩捬ts p慧攠so 楮s瑥慤 of 啒i
b敩eg
h瑴t㨯⽤oma楮LArt楣汥献ispx

楴iwou汤 b攠
h瑴t㨯⽤om慩nL乥wsK慳ax
K

th敮 p慧es 慲攠mov敤 or r敮am敤 瑨攠sys瑥m w楬氠iu瑯m慴i捡汬y m慫攠
慰propr楡瑥i捨慮ges 慮d 汥慤 v楳i瑯rs 瑯 瑨攠捯rr散琠楮form慴楯nK


S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
19


20.

Schedule go
-
live and kill times and dates for all content.




When content has been edited, reviewed and approved it will normally not
appear on the website (in a typical setup) unless it has been published. The
publishing is often carried out by users with publishing rights, typically by a
supervisor such as a Webma
ster or the Administrator. Other user roles may
have publishing rights depending on the actual user setup of the system.

The publish of content does not prevent Editors or other users from renewed
edit. They can do so as their changes

in effect will


not
be visible on the
website. The changes will not appear on the website unless a new publishing
has been made.

The Sitecore publishing processes does not just planning replicate one
database to the next.


Sitecore is hipped with 7 data repositories each
per
taining to separate topics.


There are 2 that are involved in publishing, the
Master and the Web.


The Master stores all content that is used for the
rendering in all CSM User Interfaces.


Once an item has been published
(Sitecore completely supports item
publishing / does not have to publish the
entire site) the published content is moved to the Web database that only
stores the latest version of content.


The production servers serving up page
request only render content from the Web Database.


For larger

clients, two
separate SQL instances are placed in the architecture, one in the LAN that
has 5 of the 7 databases, including Master, and two in the DMZ, including
Web.


21.

Schedule publishing time for updates to content.




Provided

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



20

22.

Multiple layout
templates allowed within the same Web
site.




奥猬Y
卩S散or攠s数慲慴敳⁣on瑥n琠trom pr敳敮瑡瑩tn, thus 慬汯睩wg this
r敱u楲em敮琠瑯 b攠me琮t啳敲s, w楴h suff楣楥n琠t敲m楳s楯ns, 慲攠慢汥l瑯 捨慮g攠
p慧攠污youts, 敩eh敲 for 愠sp散楦楣i捯n瑥n琠typ攠(攮g. news
慲瑩捬敳c, or sp散楦楣i
捯n瑥t琠楴tm (攮g. on攠sp散楦楣 news 慲瑩捬攩. 䙯r 數amp汥l慬lowing mov楮g
from 愠two
-
捯lumn 瑯 thr敥
-
捯汵mn 污you琠wou汤 b攠愠汩l敬y usag攠of th楳
fun捴楯n慬楴y.


㈳2

Con瑥n琠 pag敳e hav攠 慢楬楴y 瑯 sh慲攠 捯mmon 捯n瑥nt
w楴hin th攠
sam攠s楴攠(URL).




奥Y

24.

Ab楬楴y 瑯 sh慲攠捯mmon 捯nt敮琠t整w敥n s楴敳 (URLs).




卩S散or攠w慳⁤敳楧n敤 w楴h 捯n瑥t琠te
-
us攠慳⁡ 捯r攠f敡tur攮 E慣h 捯n瑥n琠
楴im 捡n hav攠楴i pub汩lh楮g 瑡rg整猠esub s楴敳, m楣io
-
s楴敳 and 慤d楴楯n慬a
dom慩ns) d敦楮敤 in

慤min楳瑲慴楯n 慮d 卩S散or攠w楬氠iu瑯ma瑩捡汬y ensur攠
瑨攠捯n瑥n琠楳⁰ub汩lh敤 楮 d楦f敲敮琠汯捡瑩tns. Th攠卩S散or攠C䵓Mw慳a
d敳楧n敤 sp散楦楣慬ly 瑯 慤dr敳e th攠sh慲ing of 捯n瑥n琠t整睥wn s楴is, 敡捨
p楥捥 of 捯n瑥t琠wi瑨in 卩瑥捯r攠楳 愠un楱u攠慳s整e 瑨e

software is not “page”
b慳敤㬠;nd r慴a敲 楴⁡汬lws 瑨攠捯mbin慴楯n of 捯n瑥n琠from 塍i
r数os楴ir楥猠瑯 b攠sh慲敤 慣ross mu汴楰汥lw敢 s楴isK


㈵2



䅵瑯ma瑥t 汩l瑩ngs th慴a慬汯w 捲敡瑩tn of 愠p楥捥 of
捯n瑥t琠th慴a捡n 瑨en b攠sor瑥t 慳散敳s慲yI d楳p污y楮g
v慲楯us p楥捥s of m整慤慴愠asso捩慴cd w楴h 瑨攠捯n瑥t琮t



NK i楳瑩ngs 捡n b攠慶a楬慢汥l慳ap慲琠tf 愠p慧攠or 慳⁡ s瑡td
-
慬an攠p慧攮 2K 䙬數楢汥le
nough 瑯 慬汯w for v慲楯us 汥le汳
of 瑡tonomy bas敤 on fo汤敲 or s敧men瑡t楯nI or bo瑨K




奥猬Y瑨is 楳 捯mp汥瑥ly suppor瑥t by th攠捲敡瑩tn of 瑡g f楥汤s 瑨rough 瑨攠
卩S散or攠T敭p污瑥l䵡nag敲 for 敡捨 捯n瑥t琠typ攮

Th敳攠f楥ids typ敳⁣慮 b攠
mu汴楬is琬t瑲e
敬楳ts, 捨散k汩l瑳, drop 汩l琬t整挮, 慬氠f敥d from glob慬a汩l琠tf
捡瑥tory va汵es manag敤 by ex瑥tn慬asour捥s or by 慤mins of 瑨攠卩S散or攠
慰p汩捡瑩ln.

Th攠捡瑥tor楺慴楯n v慬u敳⁣an th敮 b攠us敤 慳⁤ynam楣i
n慶ig慴楯n v慬ues, s敡r捨 ind數 fi汴敲s, 整挮



10. Authentication/Personalization and User Submitted Content Requirements

and Vendor Responses



S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
21


1.

r.

Login authentication system available for all pages and links for
pages, including confirmation of emails during login process,
second e
-
mail field to m
inimize entry errors, common login but
restricted access based on predetermined site segmentation, etc.





Sitecore uses the .NET security provider model for
authentication and authorization. Authentication performed from
any external source can be propag
ated by allowing the
authentication token provided by that system to map to the
appropriate role / user in a Sitecore domain.

2.

b.

Ability to display content based on segmentation of logged in
users, allowing personalized pages.




Sitecore provides a
role based security layer which provides the
ability to explicit personalize content based on extranet security
settings.

Administrators can set access rights to content.

Sitecore
also provides the rendering of content based on metadata values
(i.e. recomm
endation of related content), as well as a
combination of the two.

3.

c.

Allowing user
-
selectable language preferences on pages where
other languages are available. Login should not be required to set
preference, and preference should be persistent (cooki
e
-
based).




The Sitecore web CMS product has been localized to 7
languages for the use by multilingual content authors and
admins. Sitecore also provides a rich workflow engine and
manual content translation user interfaces for the management of
all
translation activities.

Because Sitecore completely separates
content from presentation, administrators and content authors
will be able to use the same presentation layers for each device
but have the content syndicated into the present components be
lang
uage specific based on the visitor of the site.


4.

a.

Ability to create processes in which users can submit content via
forms, which then can be reviewed and published on Web pages
through normal workflow channels.




Yes, Sitecore provides the ability t
o have form data reviewed in
the Publishing workflow prior to approval. This process can
include language specific versions of forms, as well as prebuilt
validation rules for specific field types.

Sitecore offers complete
flexibility for developers to ext
end the module as well.

5.

b.

Ability for users to submit files, photos, and associated with their
login or contact information in MSCRM.




Yes, Sitecore does just this internally with MS CRM and our
integration with the Sitecore Developer Network.

6.

i.

Ability to allow Web
-
based submission of both content and photos
in such a way that they can automatically show up in either a pre
-
published or published state.




Yes,

Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



22

7.

ii.

Photo submission allows for tagging or segmenting of photos so
that they can

appear in galleries based on their
tagging/segmentation.




奥猬Ys敥
ht瑰㨯:睷w.magnumpho瑯s.捯m/

䵡gnum Pho瑯, 愠
卩S散or攠捬楥c琠獩瑥tfor 數ampl攮



11.
Customization Requirements and Vendor Responses


8.

a.

Ability to incorporate html code for
embedded video, Flash, JavaScript, custom
Google maps, and other customization and
extension of functionality.




Sitecore is shipped with an HTML editor which provides complete freedom for individuals’
know汥lg攠on how

瑯 work wi瑨 䡔䵌K

Th楳 敤楴ir prov楤es 捯mp汥瑥l慣捥ss 瑯 慬氠䡔䵌 瑡gsI
汩lksI 整挮

Th攠敤楴ir 慬獯 prov楤敳⁴e攠慢楬楴y 瑯 慤d 慮d r敳楺攠im慧esI 楮s敲琠楆tam敳Ⱐ瑡tl敳Ⱐ
f污lhI 慮d formsK i慳alyI 卩瑥tor攠楳 sh楰p敤 w楴h va汩l慴楯n wh楣h v慬楤慴as 慬氠
䡔䵌 捯d攠pr楯r
瑯 pub汩lh b慳敤 on t3C s瑡nd慲dsK





b慳y 捲敡瑩tn of 愠v慲楥iy of ad
-
ho挠t敢
formsI wi瑨 f汥x楢楬楴y b整w敥n f楥汤s 瑨慴a
f敥d 瑨攠捥n瑲慬a䵓jo䴠捯nt慣琠t慴慢慳攠
慮d f楥汤s th慴af敥d 愠s数慲慴攠瑡t汥lor
sys瑥m th慴aonly r敬慴es 瑯 瑨慴

formK
Ab楬楴y 瑯 surveyK




卩S散or攠fully suppor瑳 瑨攠慢楬楴y 瑯 捲敡瑥t m慩n瑡tn, 慮d pub汩lh in瑥t慣瑩v攠w敢 forms by non
-
瑥捨n楣慬ius敲s by us攠of th攠S楴散ir攠䙯rms 䵯du汥l

Th攠卩S散or攠䙯rms 䵯du汥l捡n b攠
imp汥m敮瑥t in 2 ways.


Th攠f楲s琠獣敮慲楯
prov楤敳⁵s敲s wi瑨 瑨攠慢楬ity 瑯 dr慧 慮d drop f楥汤s
慮d 捯mmand bu瑴tns 瑯 捲敡瑥t瑨敳攠forms, wh楬攠th攠s散ond s捥n慲楯 uses 瑨攠w敢 敤楴imod攬
wh楣h 楳 愠v楳u慬ar数r敳敮瑡瑩tn of th攠s楴攠楴s敬f, 慮d 瑨攠us攠of non
-
瑥thn楣慬i啉s 瑯 捲敡瑥tnew
forms a
捲oss 瑨攠s楴攠慮d 捲敡t攠f楥汤s, 捯mmands, 慮d v慬楤慴楯n ru汥猠wh楬攠in th楳 敤楴ir.

S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
23


10.

c.

Integrated forum, blogging functionality
with comments.




Sitecore provides the Sitecore Forum module for the management and rendering of public facing
message
boards. This module provides 100% extensible markup, styles and design.

Sitecore also
provides this function through other applications (3rd party tools) that can be easily integrated
with Sitecore.



Example:


The Knot



Sitecore & ADCIEO Response to

North American Mission Board, SBC

Content Management Solution

Request for Proposal



24

11.

d.

Ability to create pages
or sections of the
site that are not visible within main
navigation but remain accessible to
individuals with the correct URL.




Th攠卩S散or攠卥捵r楴y 䵯d敬ep敲m楴i 慤min楳瑲慴ars 瑯 慬汯w or d敮y 慣捥ss 瑯 慬mos琠t汬⁡sp散瑳
of 愠w敢 si瑥t 楮捬ud楮g bo瑨

con瑥t琠tnd func瑩tn慬af敡tur敳e

卩S散or攠prov楤敳⁡ soph楳瑩捡t敤 s散ur楴y mod敬ed敳楧n敤 瑯 m楲ror r敡氠wor汤 bus楮ess
r敱u楲emen瑳.


Th攠mod敬e楮c汵d敳⁣on捥p瑳 for:



Domain


r敦敲s 瑯 愠s整eof 啳敲s 慮d oo汥猬lusua汬y asso捩慴敤 w楴h 愠sp散楦楣iw敢 s
楴攠
or 卩p散or攠捬楥c瑳



User


愠nam敤 楮div楤u慬awho 慣捥ss敳⁴e攠卩p散or攠捬楥c琠or 愠w敢 si瑥t



Role


愠nam敤 s整eof 慣捥ss r楧h瑳



Right


瑨攠慢楬ity 瑯 man楰u污瑥t慮 f瑥m in 愠捥r瑡楮 way

Th攠卩p散or攠卥捵r楴y 䵯d敬ein捬ud敳

N5 r楧h瑳I th攠S mos琠t
ommon r楧h瑳 慲攠b敬ew㨠




Th攠楬汵s瑲慴楯n d楳p污ys 瑨攠righ瑳 慳⁴hey may 慰p敡r 楮

卩p散or攻ehowev敲I non攠of th敳e

h慶攠
b敥n 數p汩捩瑬y s整e

They 慲攠as fo汬lws:





Read

Refers to the ability to view an Item.



Write

Refers to the ability to modify an Item.



Rename

R
efers to the ability to change the name of an Item.



Create

Refers to the ability to create child Items underneath the selected Item.





Delete

Refers to the ability to remove an Item.


IMPORTANT
:

The Delete command

also deletes all child Items, even if the User has
been denied Delete rights for one or more of the sub
-
items.






Administer

Refers to the ability to change the security rights for an Item.




S i t e c o r e | A D C I E O R e s p o n s e t o
N o r t h A m e r i c a n M i s s i o n B o a r d, S B C
C M S R F P


P a g e

|
25


12.

e.

Ability to create ad
-
hoc “Friendly”
shortcut URLs that would redirect to any
page. Multiple URLs should be permitted
for any page.




All URLs created in Sitecore are
search friendly.

Sitecore does not implore the use of Query
string parameters with regards to the URLs.

Sitecore also provides users with the ability to create
alias URLs for enhanced usability and to make the URLs a bit more manageable with regards to
mar
keting initiatives.


13.

f.

Options to include links on each page for a
printable version, email content to a friend,
or change the font size.





These options are supported (and used on
www.sitecore.net
).