Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1028195
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T12:21:00+00:00 2026-05-16T12:21:00+00:00

Hi I have to do a small CMS application in MS ASP.NET using WebForms.

  • 0

Hi I have to do a small CMS application in MS ASP.NET using WebForms.
I do everything on my own: front-end and back-end and Data Base schema.

Now that I want to develop the site, I wonder if I should start from front-end first, or back-end.

Considering this is a small project, could you guys give me a list of steps I do better following to help to determinate what is the best order for developing my application?

Thanks once again for your time.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T12:21:01+00:00Added an answer on May 16, 2026 at 12:21 pm

    You’ll develop all tiers as you go most of the time

    For some page you may first create database schema and fill it up with some dummy data and than work your way up.

    For others you may start with a page itself and then write functionality that’s needed to get it working. Especially when this page hasn’t been envisioned enough. This is not bad nor good. It’s just the way development tends to be.

    Some considerations

    Follow agile development

    1. Write down some requirements in a form of user stories (and keep track of them), that don’t give any info about page, data etc. Just something like As a user I would like to have primary navigation on my page. This kind of a story will permit later changes to code/pages without the story becoming invalid.
    2. Don’t haste into something fully functional at first. Don’t over-engineer your code. Because you’ll end up doing changes later = follow YAGNI. For instance don’t fully design your DB at first. Do just as much as you need per story being developed. But do think of future things that you’ll have to integrate into existing codebase.
    3. Refactor existing code right away when you see something should be changed.
    4. If you have someone to test your code, let them do it. Don’t develop next stories before existing bugs have been fully resolved. You’ll be grateful for this later.
    5. If your code is semi-complex I suggest you write unit tests, so future code changes won’t break existing functionality.

    Most of all: learn as you go and change existing code while doing so. Since you’re learning these technologies I suggest you stick to simplicity at first. You’ll add more complex things when needed. Some of them won’t get done at all. So in the end youl realise YIDNI (yep, I didn’t need it).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am building a small cms system in MVC.NET, and I have some editable
We have a small company and we have developed our own CMS in PHP/MySQL.
I have a small site I developed for a friend that uses ASP.Net MVC
I have small script in bash, which is generating graphs via gnuplot. Everything works
I have small question. When I started to programm my application, I grouped types
I have small database of business and their addresses. Using the Google Geocode API
I'm building a application that supports different domains. A small CMS that supports different
I have a small project for which I need to offer a CMS UI/storage
I recently started working on a small CMS. I usually develop .NET applications in
I have been using Turbogears 1 for prototyping small sites for the last couple

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.