Public Website Admin Tools: Divide and Conquer

home
asp.net
view story

3 Kicks

Public Website Admin Tools: Divide and Conquer(sitepoint.com)

submitted by wwb_99(870) 4 years, 8 months ago

One of the first steps when designing a web application is figuring out how to administer the beast and where these admin tools should live. Often this comes down to one key question: should the public website itself also be the administrative tool? While there is no single approach that works in every situation, I generally find that keeping the administrative tools separate makes more sense than embedding the tools within the public facing website. And here's why.

2 comments |category: ASP.NET |Views: 2
Tweet

tags: SitePoint another

Everyones tags:

Your Tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

MarthaBass(490) -

gavinjoyce(25.7k) -

wwb_99(870)

Comments:

posted by crpietschmann(11.3k) 4 years, 8 months ago 0

I disagree!

I can understand the security concerns of having two seperate apps. One for “public” UI and one for Admin. But it really depends on what type of functionality your application offers. Does it really make sense to have a seperate tool to administer a Content Management System? Why not just put an “Edit” button on the pages when the user is logged in using an Admin account? There are plenty of other cases that would be easier to have a single app, but that’s probably the most common.

posted by gavinjoyce(25.7k) 4 years, 8 months ago 0

There are benefits both ways, it depends on context as with a lot of things. In the context of this site, integrated admin functionallity fits the bill.

Most Active Users

What's this?