Разработка сайта и наполнение

Project Overview

Creation of a web platform for hosting projects aimed at recovery.

Key features and characteristics:

• Public data: All visitors (without registration) have full access to information about projects – description, funding needs, status, etc.
  
  

• Personal accounts: Interested parties can register on the platform, create a profile, and add their creative projects and engage interested parties in this project. The account allows managing project information and updating implementation status.
  
  

• Interactive project catalog: Users have access to a filtering and search system for projects by various criteria – industry, region, type (e.g., sponsorship, equity, loan, grant), amount of required funding or materials, stage of implementation, etc. Filters dynamically update the list of projects without reloading the page for convenience.
  
  

• Multilingualism. (there may be software for translation and language creation): The site must support 4 languages for the interface and content – Ukrainian (main), German, English, and Spanish. Each language version will have a complete translation of the content. Implementation of multilingualism – through separate URLs for each language (e.g., site.ua/uk/..., site.ua/en/..., site.ua/es/...) using hreflang for SEO. The language switcher is placed in a prominent location in the interface.
  
  

• Section “Participation/Grants/Sponsorship”: A special section for presenting crowdfunding and charitable initiatives related to recovery (e.g., fundraising for the reconstruction of a specific facility or supporting a small business team). Note: Direct payment integration is not planned (there will be no ability to make payments on the site), but details and external links must be provided so that interested parties can support these initiatives.
  
  

• Connectable/disconnectable section. News and media: A section for publishing Alliance news and media materials – announcements, success stories, analytical articles, photos/videos about the recovery process. This will provide informational support for projects and increase coverage through media and social networks.
  
  

• Integration with social media (SMM): The site provides tools for disseminating information on social networks – “Share” buttons (Facebook, Twitter/X, LinkedIn, etc.) on project and news pages. Open Graph and Twitter Card metadata are configured for correct display when publishing links on social networks. There is also a possibility to subscribe to updates (RSS news feed or newsletters).
  
  

• Traffic and performance: The system is designed for ~100,000 unique visitors per month. This requires performance optimization (caching, CDN, query optimization) and scalability of the architecture to ensure fast page loading even under peak loads.
  
  

• Administration and moderation: An advanced administration system will allow managing content: moderating and approving projects, adding news, analyzing visit statistics and activity. A multi-level access system (administrators, editors, moderators, business users) is implemented to ensure security and quality control of content.
  
  

This technical task describes the structure of the site, functional requirements, technical specifications for implementation, administration aspects, possible integrations, and content requirements. The document is intended for the team of developers, designers, SEO specialists, content managers, and SMM specialists so that all parties have a common understanding of the product.

Site Structure and URL Architecture

The site will have a logical structure of sections, convenient navigation, and readable URLs. Each language version of the site will use its own prefix or subdomain (e.g., https://example.com/uk/ for Ukrainian, /en/ for English, /es/ for Spanish version). The structure of sections is the same for all language versions. Below are the main sections of the site, their functionality, and proposed URLs:

Homepage

• URL: / (with the corresponding language prefix, e.g., /uk/ for the Ukrainian version).
  
  

• Description: Welcome page of the platform. The homepage displays key elements:
  
  

  • Title and short description of the platform: name, slogan, or mission of the platform.
    
    

  • Search and filter projects: key search field (by project name or keywords) and button to go to the project catalog. A quick filter may be provided (e.g., a dropdown list of industries).
    
    

  • “Latest Projects” block: several new or most relevant projects with a short preview (title, image, short description, investment amount, status).
    
    

  • “Participation/Grants” block: a promo block that draws attention to the participation/grants section. Contains a call to support initiatives, briefly mentions one or two relevant initiatives.
    
    

  • News and media: feed of the latest news or announcements (news headlines with dates and thumbnails).
    
    

  • Information blocks: brief information about the organization and partner organizers, contact information, possibly counters (how many projects have been posted, how much investment has been attracted).
    
    

  • Interface language: language switcher (UK, GE | EN | ES ).
    
    

  • Navigation menu: links to main sections – Projects, Donations/Grants, News, About Us, Contacts, Login/Register.
    
    

Note for designers: The homepage should have an attractive hero block at the top (background thematic photo or graphic symbolizing recovery/investments, and a call to action – “Join the Recovery”). The design should be modern, easy to perceive, with an emphasis on key actions (view projects, support initiatives). The page must be fully responsive: on mobile, blocks stack vertically, and the menu transforms into a “hamburger”.

Functional Requirements

This section describes the main functional capabilities of the system, many of which have already been mentioned in the site structure. We will formulate them as requirements:

• FR1: Public access to projects. All visitors (unauthorized) can view the list of projects and detailed project pages without restrictions. Registration is not required to access information.
  
  

• FR2: Registration and login for businesses. The system allows representatives of businesses to create an account. Registration requires email confirmation. The administrator can approve new accounts (configured by moderation policy).
  
  

• FR3: Adding a project. A registered business user can fill out a project addition form through their personal account. Mandatory: support for entering information in three languages (Ukrainian – main, English – preferred for international investors, Spanish – optional). After filling out, the project is sent for moderation.
  
  

• FR4: Moderation of projects. A project added by a business receives the status “Under moderation”. The administrator (or content moderator) checks the content in the admin panel (correctness of data, absence of prohibited materials). After verification, it can be published (making the project visible on the site) or rejected (with a reason given so that the author can correct it).
  
  

• FR5: Editing a project. The author (business) can edit their project. If the project is already published, changes are either published immediately (for fields like status or updates) or require moderation again (for changes in description, amount, etc., that may significantly change the essence of the project).
  
  

• FR6: Filtering and searching for projects. Users can filter by industry, region, type of investment, amount, status (simultaneously by several criteria) and perform full-text search. The combination of filters works correctly (logic “AND” between different categories of filters). Requirement – quick response to filter change (up to 1-2 seconds). The search is case-insensitive, possibly with morphology (for Ukrainian/English – simplified).
  
  

• FR7: Multilingual content. All content of projects, news, static pages is available in Ukrainian, English, Spanish. Implementation: either separate fields for each language in the CMS for each object, or using built-in multilingual capabilities (e.g., in Drupal/WordPress). Field names, menus, interface messages, URLs (preferably) should be translated. Ensure proper hreflang attributes for SEO.
  
  

• FR8: Donations/grants section. Content managers (or administrators) can add entries about charitable initiatives. Visitors view them just like projects (publicly). Interaction: transition via external link for contribution. Multilingualism is also desirable here (at least a short description in three languages).
  
  

• FR9: News and media. Ability to publish news and articles through the content management system. News can be linked to categories/tags. Visitors can read without registration. (Option: the possibility of commenting on news – to be decided additionally, if needed, using third-party widgets to reduce moderation issues).
  
  

• FR10: SMM and dissemination. All public content pages (projects, initiatives, news) have buttons for sharing on social networks. Correct Open Graph metadata should be substituted: title, description, image (e.g., the first image of the project or a specially set preview). The site also has widgets linking to the alliance's official social networks (Facebook page, Twitter account, etc.).
  
  

• FR11: Traffic support and performance. The site must operate stably under a load of 200k unique visitors/month (~6-7k per day) and peak simultaneous sessions of hundreds of users. It is necessary to implement page caching for unauthorized users, optimize database queries, use CDN for static content (images, styles, scripts). These measures will significantly improve loading speed.
  
  

• FR12: Security and reliability. Implement HTTPS encryption for all pages. Protection against major web vulnerabilities: SQL injections, XSS, CSRF, file injections. The content management system/platform must support roles and permissions: business users can only add/edit their projects but cannot publish without verification; content managers can create/edit news; administrators have full rights. Passwords are stored hashed. User data (email, contacts) is not published without their consent. Regular database backups (automated, e.g., daily) are a requirement to prevent data loss.
  
  

FR13: Search engine optimization (SEO). More details in a separate section, but functionally – the ability to set SEO attributes: page title (title tag), meta description