All geek questions in one place

What is the best practice for separating GUI design from server development when developing modern web applications?

We are currently developing several web applications and allow our designers to convert signed paper prototypes into static web pages. In addition to hyperlinks between pages, designers started adding jquery calls to update elements on pages, extracting data from static json files. As soon as the designers complete and submit the submitted complete web pages, CSS and JavaScript files; server-side developers then edit the pages and replace links to local static json documents with links to live json URLs that return the same json data structures.

My question is: What are the effective ways to separate GUI design from serveride dev and reduce integration time and effort? Some examples:

  • Do you have developers to manually change each json link on the prototype web pages of designers?
  • Are you adding a global variable somewhere so that designer pages can easily switch between using static and dynamic data?
  • Are you sure that web pages should be aware of when they work from a web server or just somewhere in a folder?
+3
source share
3 answers

, . , , . ? , . , ?

, . , , . - script, , .

+1

, , "url/path" (dev vs test vs production ..), "proto" ( proto.mycoolapp.company.int), URL-, .

, , , , // + [ url] (, json ..).

UI .

, (, , ). URL- (, ..) proto.mycoolapp.company.int/frontend/login/securelogin? = GrayWizardX. , , , ( ..) , .

, , - "proto" . var, .

0

, ( html - php?), ...

HTML + javascript, , , javascript include , . , (, ), , . GUI include. , , , .

, , , .

0

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

More articles:


All Articles