Difference between revisions of "Web Site"
From MgmtWiki
(→Context) |
(→References) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
| − | *While the HTTP protocol can be used for other purposes, they are not included in this | + | *While the HTTP protocol can be used for other purposes, they are not included in this usage. |
*In this wiki a [[Web Site]] can be one or more of: | *In this wiki a [[Web Site]] can be one or more of: | ||
#A [[Resource]] provider or [[Relying Party]] (Those terms are synonyms.) | #A [[Resource]] provider or [[Relying Party]] (Those terms are synonyms.) | ||
| Line 11: | Line 11: | ||
==Problems== | ==Problems== | ||
| + | A [[User]] that wants to get access to [[Resource]]s on the web needs some level of [[Assurance]] that they will not suffer an attack from malicious actors also on the internet. | ||
| + | ==Access to Web Content== | ||
| + | *The most common way for [[User]]s to access a [[Web Site]] is with a web browser from some well-know browser provider either within a device operated by the user, or on a cloud computer under user control. | ||
| + | *A growing form of access to web sites is via a [[Native App]] provided by a source which should provide the security details about the app. | ||
| − | == | + | ==Best Practices for Building One== |
| − | * | + | Choosing between C# and TypeScript for web development depends on the type of website you want to create and your preferred development approach. Here's how they compare: |
| + | |||
| + | ===C# (ASP.NET) – Backend-Focused=== | ||
| + | Best for: Server-side development, enterprise applications, API-driven websites. ✅ Strengths: | ||
| + | * High performance with .NET runtime. | ||
| + | * Strongly typed language with mature tooling. | ||
| + | * Ideal for full-stack development using Blazor. | ||
| + | * Secure and scalable for large web applications. ✅ Common Uses: | ||
| + | * ASP.NET Core MVC/Web API for backend development. | ||
| + | * Blazor for interactive web UI using C#. | ||
| + | * Enterprise applications and intranet systems. | ||
| + | |||
| + | ===TypeScript (Frontend-Focused)=== | ||
| + | Best for: Client-side development, dynamic user interfaces, modern web apps. ✅ Strengths: | ||
| + | * JavaScript-compatible with static typing. | ||
| + | * Better maintainability for large-scale JavaScript projects. | ||
| + | * Works seamlessly with frameworks like React, Angular, and Vue.js. | ||
| + | * Great for frontend-heavy applications needing complex interactions. ✅ Common Uses: | ||
| + | * React with TypeScript for dynamic UI development. | ||
| + | * Angular with TypeScript for structured web applications. | ||
| + | * Progressive Web Apps (PWAs) needing client-side logic. | ||
| + | ===Which One to Choose?=== | ||
| + | * If you're building a backend-heavy website or enterprise-grade app ➝ C# (ASP.NET). | ||
| + | * If you need a modern frontend UI with rich interactivity ➝ TypeScript (React/Angular). | ||
| + | * If you want full-stack development ➝ Combine ASP.NET (C#) for backend + TypeScript for frontend. | ||
==References== | ==References== | ||
| + | *The page [[Web Site Identity]] explains the really horrendous way in which [[User]]s can determine where there are in the internet is badly broken. | ||
| + | *The page [[Web Site Security]] explains the way in which [[Web Site]]s need to protect and inform [[user]]s so that they can be secure on the web. | ||
| + | * The page [[Web Site Testing]] explains the way to test a [[Web Site]] during development. | ||
| − | + | [[Category: Glossary]] | |
| − | [[Category: | + | [[Category: Best Practice]] |
| + | [[Category: Web]] | ||
Latest revision as of 09:18, 17 May 2025
Contents
Full Title or Meme
A internet service running the HTTP protocol to allow a Subject (natural or legal person) access to a collection of Resources.
Context
- While the HTTP protocol can be used for other purposes, they are not included in this usage.
- In this wiki a Web Site can be one or more of:
- A Resource provider or Relying Party (Those terms are synonyms.)
- A Identifier or Attribute Provider
- An anonymous source of content which is not otherwise the subject of this wiki.
Problems
A User that wants to get access to Resources on the web needs some level of Assurance that they will not suffer an attack from malicious actors also on the internet.
Access to Web Content
- The most common way for Users to access a Web Site is with a web browser from some well-know browser provider either within a device operated by the user, or on a cloud computer under user control.
- A growing form of access to web sites is via a Native App provided by a source which should provide the security details about the app.
Best Practices for Building One
Choosing between C# and TypeScript for web development depends on the type of website you want to create and your preferred development approach. Here's how they compare:
C# (ASP.NET) – Backend-Focused
Best for: Server-side development, enterprise applications, API-driven websites. ✅ Strengths:
- High performance with .NET runtime.
- Strongly typed language with mature tooling.
- Ideal for full-stack development using Blazor.
- Secure and scalable for large web applications. ✅ Common Uses:
- ASP.NET Core MVC/Web API for backend development.
- Blazor for interactive web UI using C#.
- Enterprise applications and intranet systems.
TypeScript (Frontend-Focused)
Best for: Client-side development, dynamic user interfaces, modern web apps. ✅ Strengths:
- JavaScript-compatible with static typing.
- Better maintainability for large-scale JavaScript projects.
- Works seamlessly with frameworks like React, Angular, and Vue.js.
- Great for frontend-heavy applications needing complex interactions. ✅ Common Uses:
- React with TypeScript for dynamic UI development.
- Angular with TypeScript for structured web applications.
- Progressive Web Apps (PWAs) needing client-side logic.
Which One to Choose?
- If you're building a backend-heavy website or enterprise-grade app ➝ C# (ASP.NET).
- If you need a modern frontend UI with rich interactivity ➝ TypeScript (React/Angular).
- If you want full-stack development ➝ Combine ASP.NET (C#) for backend + TypeScript for frontend.
References
- The page Web Site Identity explains the really horrendous way in which Users can determine where there are in the internet is badly broken.
- The page Web Site Security explains the way in which Web Sites need to protect and inform users so that they can be secure on the web.
- The page Web Site Testing explains the way to test a Web Site during development.
