Hi Alessandro, 

 To model Websites in LeanIX, we first need to clarify what specific aspects of these Websites you're looking to capture that wouldn't already be served by an application Factsheet. Understanding your detailed requirements will help us determine the most appropriate way to model this information within LeanIX. Here are a few points to consider:

1. What specific attributes of the Websites do you want to model?
   - Are there unique aspects of the Websites that are not covered by existing FactSheets in LeanIX?

2. How do these Websites relate to the rest of the metamodel?
   - Do these Websites directly support a particular business capability, or do they support applications within your architecture?
   - Are there other relationships, such as dependencies on other IT components or user interactions, that need to be captured?

3. Which other FactSheets of the metamodel would these Websites relate to?
   - Are there interactions or dependencies with business processes, data objects, interfaces, or specific technical components that need to be modeled?

4. What kind of report visualization are you looking to have?
   - How do you intend to use this data? Are you aiming for high-level overviews, detailed dependency maps, or impact analyses?
   - What insights or decisions will these reports support?

Attaching a decision tree of IT component VS Application that might help solve this question: 

Hi Alessandro,

We also manage our Websites as applications in leanIX. It was decided to do so before I joined, and the main requirement was driven by our cybersecurity team. They wanted to document the protection level of all websites we have created (more than 100 today).

We are flagging our websites using a custom field, but if I had to redo our set-up today, I would either keep those websites as applications, but using a sub-type instead, OR create a custom factsheet type to completely isolate the websites since they serve a specific purpose in our case.