--I am pretty sure the answer is "yes of course!" but having only built a fairly straightrorward site in Umbraco, I do not know exactly how to approach this - anyway... --
Lets just suppose I have a customer with 100 national outlets. Each one of which has a few pages on the main company website which need to be kept up to date by users at each location. Users at each location should only have access to their own pages and not to anybody elses.
Each location would have some standard contact profile information as well as more detailed information for each of their team members. Team members would appear on a listiing page and their listing would link to a more detailed page. Obvioulsy the format and general style for the pages at each location would be be the same.
Until I discovered umbraco, I would of course do all this in asp.net, sql server etc but umbraco has a such a nice UI out of the box so I would like to to learn how to approach a project like this.
How would you store the data? Do you add to the Umbraco database or do you set up a separate db.
Is it possible to control access to specific content pages depending on login?
"Yes of course" would be the answer, right? No, seriously...
I don't see why you shouldn't be able to manage everything from within umbraco. Don't worry about the number of pages, that shouldn't be an issue at all. umbraco can handle quite a large number of pages (if you're talking about 100 outlets, each having a few pages...)
If you use the standard features from umbraco, then you shouldn't worry about how data is stored, it'll be done for you (use of document types, templates)
Granting access to users based on their location is also not an issue, umbraco comes with features oob to handle permission based access.
I do recommend to think about your structure upfront, it may be quite important if you're thinking of access restrictions (for example, you can set a start node for a user (so he/she can only update data below that structure), but this is restricted to only one "parent" node. If you'd want to allow users to be able to manage multiple "parent" nodes (let's call them outlet nodes), then you'll be in trouble (just because you only set a single parent node as the start node)
Also, in regards of the structure, make sure to know upfront what data should be shared across all "outlets", you may for example have content that should be reused across different outlets, then it would be advisable to put that info into a separate structure, and have the outlet retrieve that info from there (sort of relating data)
Is umbraco suitable for...
...large projects like...
--I am pretty sure the answer is "yes of course!" but having only built a fairly straightrorward site in Umbraco, I do not know exactly how to approach this - anyway... --
Lets just suppose I have a customer with 100 national outlets. Each one of which has a few pages on the main company website which need to be kept up to date by users at each location. Users at each location should only have access to their own pages and not to anybody elses.
Each location would have some standard contact profile information as well as more detailed information for each of their team members. Team members would appear on a listiing page and their listing would link to a more detailed page. Obvioulsy the format and general style for the pages at each location would be be the same.
Until I discovered umbraco, I would of course do all this in asp.net, sql server etc but umbraco has a such a nice UI out of the box so I would like to to learn how to approach a project like this.
How would you store the data? Do you add to the Umbraco database or do you set up a separate db.
Is it possible to control access to specific content pages depending on login?
Can anyone give me some ideas?
Cheers
Julian
"Yes of course" would be the answer, right? No, seriously...
I don't see why you shouldn't be able to manage everything from within umbraco. Don't worry about the number of pages, that shouldn't be an issue at all. umbraco can handle quite a large number of pages (if you're talking about 100 outlets, each having a few pages...)
If you use the standard features from umbraco, then you shouldn't worry about how data is stored, it'll be done for you (use of document types, templates)
Granting access to users based on their location is also not an issue, umbraco comes with features oob to handle permission based access.
I do recommend to think about your structure upfront, it may be quite important if you're thinking of access restrictions (for example, you can set a start node for a user (so he/she can only update data below that structure), but this is restricted to only one "parent" node. If you'd want to allow users to be able to manage multiple "parent" nodes (let's call them outlet nodes), then you'll be in trouble (just because you only set a single parent node as the start node)
Also, in regards of the structure, make sure to know upfront what data should be shared across all "outlets", you may for example have content that should be reused across different outlets, then it would be advisable to put that info into a separate structure, and have the outlet retrieve that info from there (sort of relating data)
Sample structure of your site could be:
-Content
--Outlet 1
--- Company info
--- ...
--Outlet 2
--- Company info
...
--Reusable content
...
Feel free to ask more questions if still unclear.
Hope this helps.
Regards,
/Dirk
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.