Once you’ve determined the purpose of the project, try to work with its structure. What sections will be on your site, how will they be called and what information will they contain? Study the sites of your competitors and partners. Think about the elements that will be most useful (or vice versa – useless) in your case.
Try not to overload the site with a large number of possibly totally unnecessary functions. For example, why a corporate resource forum? Will your forum will lead a lively discussion, when the Internet and already enough special thematic sites? Why should visitors use your forum, and whether your company has a person who will maintain it?
If you want to get feedback, it makes sense to have a Q&A section, which allows the visitor to ask a question by filling out a form, and after you give your answer, publish the resulting Q&A on the site. How about a simple text-based “Frequently Asked Questions” page? Implementing such a section probably wouldn’t add anything to the estimate.
There are plenty of examples like this. Subscribing to the newsletter is necessary if you are willing to keep it regular and full of really interesting information. Registration and authorization of users – if behind this are useful and important for the visitor functions.
When you provide your vision for the project performer, a good web studio will definitely recommend what to change, what to abandon, and what to bring, if necessary. By combining the structure that you identified for yourself, as well as the developer’s recommendations, you can more clearly understand which sections and features on your site are really needed.