All geek questions in one place

User interface control in many discrete web applications

Currently, our company has 7 separate large Internet-oriented Internet applications.
They all have the following

  • have different views and sensations that represent the branding style of the time when they were built.
  • have different user interface and backend interfaces based on when they were built.
  • separate teams supporting and developing each
  • built on different timelines - up to 10 years

This leads to the following problems

  • Changes to a new brand need to be applied separately - it’s very expensive and usually doesn’t happen
  • Availability problems or other common errors have the same problem.
  • New style and interaction guides should be applied separately - again a problem

I am looking for methods that others have used in a similar environment, so that new applications can be separately built and maintained with a client interface that is still centrally managed without a bottleneck. I was thinking of using the same approach as white marking, where HTML / CSS / Javascript template templates are created and processed. Then each team will use the updated version when it becomes available and will be included during the build. The risk of this is never updated. I guess this is not an unusual situation for large corporations (we are in finance). Can you share with me your technical and technical means that you used?

( /) .

+3
2

, Javascript/CSS - . , .. script.aculo.us jQuery, , , , .

, (, , ) "", HTML, .. , . , , . "" ; , , , "" /, . , javascript < 300kb.

, . , , (, , ). , - . ( ) ( ), , , , . , , , .

, - . -, , .

0

, Sitemesh . , - Sitemesh.

. Visual Example http://www.opensymphony.com/sitemesh/

0

Source: https://habr.com/ru/post/1753009/

More articles:


All Articles