The technology should match the tasks of the website and its ability to maintain it. The new one does not in itself determine whether the solution will be convenient for the editorial board, stable and developable.
Save requirements without toolnames
Instead of starting a conversation with a particular library, describe the task of the service. Does the editor publish every day? Does the offer download data from another system? Does the recipient have an account and perform complex operations? Answers allow to distinguish the company page from the application requiring much more extensive architecture.
It is also worth defining limitations: the environment available, knowledge of the team, deadlines and maintenance budget. The solution convenient for the author of the prototype will not always be as simple for those responsible for the service later.
Ask for daily support and updates
Compare the proposals based on specific actions. Ask to show how the subpage is added, changes the common element and checks the change before publication. Please note which tasks the editor performs and which require a programmer.
- Who is responsible for updating the components used?
- How are changes checked before they are launched in public?
- Can you restore the environment from the project documentation?
- What elements depend on external services and their charges?
It is not enough to say that the system is modern. A description of how it is maintained is needed.
Check the project transfer capability
Documentation, repository, environment configuration and access to data should be discussed before you start working. Also, set rules for the use of ready-to-use items and the scope of code and permission transfer. These are design cases that do not solve the choice of popular tool alone.
Make a small test of the most difficult requirements
If the decision depends on an unusual integration, first test it on a limited example. This test should have a condition of success and the limitations recorded. It allows you to assess risk before the entire page is created. It is also helpful comparison of the finished solution with the dedicated solutionGood technology does not need to be the latest; it should allow safe implementation of the agreed scope and understandable after implementation.
