Contact person: Business Client

Phone:Show

Email:Show

Location: COLCHESTER, United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Please bid the complete amount, not indicative figures.

1. Project overview

We are building a web portal on Google Cloud to aggregate content from a single group into multiple external sites. The portal will act as a central control plane where we can:
• Register and log in different user types
• Manage permissions and content
• Continuously upload and curate links and quotes
• Visualise “opportunities” on a map, driven by underlying database records

The front end should leverage the design language of this UI kit (or similar) as a reference for layout, components, and visual style:
[login to view URL]

The outcome we want is a production-ready, maintainable portal deployed on our Google Cloud environment, with clear documentation and handover.


2. What we already have vs what you will do

You deliver (end-to-end):
• Technical architecture and implementation on GCP
• Database design and build
• Back-end services / APIs
• Front-end implementation aligned with the design kit
• User management and permissions
• Mapping visualisation and filters
• Basic admin tooling and documentation

3. Target tech stack (open to your recommendations)
• Cloud platform: Google Cloud Platform
• Possible services:
• Compute: Cloud Run or App Engine (containerised app)
• Database: Firestore (NoSQL) or Cloud SQL (PostgreSQL/MySQL), depending on your proposal
• Auth: Google Identity Platform or equivalent custom auth layer
• Storage: Cloud Storage for any file assets
• Monitoring & logs: Cloud Logging / Cloud Monitoring

We are open to you proposing the most appropriate combination, but it must be standard, maintainable GCP tooling.


4. Core functional requirements

4.1 Authentication, registration and permissions
• User registration and login (email/password, with optional SSO plug-in potential later).
• Role-based access control, e.g.:
• Admin
• Content Manager / Editor
• Standard User / Viewer
• (Optional) External Partner
• Ability for Admin to:
• Create, edit, deactivate users
• Assign roles / permissions
• Reset passwords

4.2 Portal layout & navigation
• Home screen structured as a 5x4 grid (5 categories x 4 “tiles” each, or equivalent concept), each tile linking into a specific section or site grouping.
• Responsive design for desktop primarily, with acceptable behaviour on tablet/mobile.
• Use of UI components in line with the Envato management dashboard kit (cards, tables, filters, sidebars, modals).

4.3 Content aggregation & links
• Ability for authorised users to continuously upload links (e.g. external websites, documents, resources), with metadata:
• Title
• Description
• Source / organisation
• Category / subcategory
• Tagging (multi-tag)
• Associated opportunity (where relevant)
• Links must be stored in the database and displayed in relevant tiles/sections of the portal.
• Basic filters and search: by category, tag, source, and date added.

4.4 Quotes database
• Database structure to store quotes from different sources, including:
• Quote text
• Source (person, organisation)
• Context / category
• Date
• Optional link to an external source
• Optional link to a specific opportunity or site
• Simple CRUD UI within the portal for authorised users to manually add, edit, and delete quotes.
• Display of quotes in relevant sections (e.g. rotating quote component, tables, or cards).

4.5 Opportunities & map visualisation
• Database structure to store opportunities, including at minimum:
• Title
• Description / summary
• Category / type
• Status (open, closed, in-review, etc.)
• Geographic location (country, city, coordinates)
• Related site / portal tile
• Relevant links / documents
• Interactive map view showing all opportunities, with:
• Pins/markers derived from the database (no hard-coded coordinates)
• Filters (e.g. by category, status, country)
• Click on a pin to open a detail panel or modal with full opportunity information and associated links/quotes
• Implementation using a mapping solution (e.g. Google Maps or similar), integrated into the front end.

4.6 Admin area
• Admin dashboard to manage:
• Users and roles
• Categories, tags, taxonomies (e.g. opportunities categories, quote tags)
• Links / resources
• Quotes
• Opportunities
• Simple analytics panel (even if basic) for:
• Number of users
• Volume of links, quotes, and opportunities
• Activity log (who created/edited what, when)

5. Non-functional requirements
• Clean, modular codebase (clear separation of front end, back end, and infrastructure).
• Secure handling of authentication and user data.
• Environment setup for dev / staging / production within our GCP project.
• Documentation:
• System architecture overview
• Database schema
• Deployment instructions (CI/CD if proposed)
• Short admin/user guide (how to manage content and users).

6. Deliverables
1. Technical design pack
• High-level architecture
• Chosen GCP services and rationale
• Database schema (ERD or equivalent)
2. Working portal deployed on GCP
• Authentication and role-based access
• 5x4 layout implemented
• Content aggregation module (links)
• Quotes module
• Opportunities module and map view
• Admin area
3. Source code & configuration
• Code in a Git repository (our GitHub/GitLab/Bitbucket)
• Infrastructure-as-code templates if used (optional but preferred)
4. Handover
• Documentation pack
• One live handover session (screen-share) walking through architecture, deployment, and admin flows.

87 What to include in your proposal
• Brief description of your experience with:
• Google Cloud (which services you’ve used)
• Role-based portals / dashboards
• Mapping / geo-visualisation
• Proposed tech stack and architecture in 3–5 bullet points.
• Rough delivery plan with phases (discovery, build, test, deploy).
• Ballpark budget and time estimate." (client-provided description)