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 1033127
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T14:11:07+00:00 2026-05-16T14:11:07+00:00

Ok, I know the answer for this question may not be objective but I

  • 0

Ok, I know the answer for this question may not be objective but I couldn’think for a best place to post it. However, I think it can be approached from an objective point of view and the discussion may turn into a very nice guide to the subject.

So, the question is: How would you position web development skills from the bottom until the very top, according to challenge, fees and another relevant criteria?

I’m thinking about something like:

  1. HTML
  2. CSS
  3. JavaScript (Client script)
  4. PHP, RoR, J2EE (Server script)
  5. MySQL (DataBases and persistence)
  6. XM, JSON, SOAP (Web Services and APIS development)
  7. Widgets
  8. …

Btw, feel free to edit the answer if you feel like.

  • 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-16T14:11:08+00:00Added an answer on May 16, 2026 at 2:11 pm

    While I agree that this is fairly subjective, and it may be justified to close it, there are a few things that can be said about the hierarchy.

    You need to understand HTML to do CSS.

    CSS (or at least its most common application) requires you to have at least a fundamental understanding of HTML and browser layout systems.

    You need to understand HTML to make (client side) JavaScript useful.

    While people keep building up abstraction layers removing this requirement (e.g. Objective J & Cappuccino), you should still have an understanding of the DOM tree and the meanings of all the tags you’re creating, whether you’re creating them directly or indirectly.

    You need to understand HTML to make serverside applications (PHP, RoR, etc.) useful to humans.

    I say to humans because I suppose you can make a server side application such as an API that does not use HTML.

    In the context of web development, you need to know some server side language to make databases useful.

    You can’t communicate directly between the client and a database yet, so you therefore need some way of interacting with the database on the serverside. I suppose this is coming with local storage in HTML5.

    XML & JSON are transports – they are useless without knowledge of server side languages on at least one end of the transport.

    That said, if you’re simply interested in USING API’s, you can probably get away with only knowing either serverside or clientside, as most APIs nowadays have JSONP support.

    So more or less, if you want to get into web dev:

    Start with HTML, then take your pick between CSS, JavaScript or server side language.

    From there, learn another one of those three, rinse, repeat.

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

Sidebar

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.