I am currently evaluating umbracoand have the following
question.
1. we have a existing site written in asp.net mvc and
would like to use umbraco as a repository of content. So we won't be using
umbraco "from the ground up". ex. we won't build a entire page fromumbraco , is that doable? Can I just grab the content I want for umbraco using some API?
2. ideally, we would like to set up umbraco in
dev/staging/production environment. Is there any easy way in umbraco to
export a changeset across environment. Meaning that once I made a
change in dev/staging, I can click a button in umbraco and have the same
content change in production?
2. Yes and no. In terms of content, the best approach is to use Courier to sync content between staging/production. My advice would be to speak with Umbraco HQ about a PRO license, as they'll give you additional support, etc.
Templates and other static files are easy to deploy... Templates, XSLT, User Controls, CSS, JavaScript, etc.
The difficult ones to keep in sync are data-types, document-types (media-types), macros, etc. To my knowledge those are manual changes. My advice is to try to get your content schemas (document-types) nailed down before you deploy to production. (I know that isn't always realistic).
Newbie questions
Hi,
I am currently evaluating umbracoand have the following question.
1. we have a existing site written in asp.net mvc and would like to use umbraco as a repository of content. So we won't be
using umbraco "from the ground up". ex. we won't build a entire page fromumbraco , is that doable? Can I just grab the content I want for umbraco using some API?
2. ideally, we would like to set up umbraco in dev/staging/production environment. Is there any easy way in umbraco to export a changeset across environment. Meaning that once I made a change in dev/staging, I can click a button in umbraco and have the same content change in production?
Hi Herman,
1. Yes you can use the various APIs to pull content from Umbraco. Typically you would use the "nodeFactory" class.
Depending on your architecture, whether Umbraco is locally accessible, you could expose content nodes via the /Base interface.
http://our.umbraco.org/wiki/reference/umbraco-base
There are many ways to approach it.
2. Yes and no. In terms of content, the best approach is to use Courier to sync content between staging/production. My advice would be to speak with Umbraco HQ about a PRO license, as they'll give you additional support, etc.
Templates and other static files are easy to deploy... Templates, XSLT, User Controls, CSS, JavaScript, etc.
The difficult ones to keep in sync are data-types, document-types (media-types), macros, etc. To my knowledge those are manual changes. My advice is to try to get your content schemas (document-types) nailed down before you deploy to production. (I know that isn't always realistic).
Good luck, Lee.
Thanks Lee, will definitely look into Base/ and Courier.
is working on a reply...