PHP Laravel Build

Hi, 

 

I need a quote and timeline for the following: 

 

–We have an existing platform built within PHP Laravel and would like to make additional changes to the site, this platform is used for registration for a convention.

It includes

A user interface to register tickets for participants of the convention

An Admin interface to manage the different ticket types, users and participants

Current external dependencies

Stripe payment gateway

Existing link - https://registration.glasgow2024.org/login



Overview of the changes required

New Events section, each of these will be type of election what participants may part take in, events have multiple election type, with different voting systems and processes; additionally, some offline options where the votes take place physically at the convention;
payment required for some of the events;

Significate changes to the admin roles, with new roles that break up what users may access what.

New Admin tools around tallying votes and managing participants



You must abide by the following guidance when making your additions:

No livewire.

Frontend

2.1. Laravel mix, should use Laravel mix with webpack instead of vite (Unless specified as a react project) frontend should be built using the following libraries: 

2.1.1. Blade  

2.1.2. Bootstrap – Frontend must use as bootstrap much as possible, before custom scss is added, bootstrap variables should be overridden instead of css overriden. 

2.1.3. bootstrap icons and/or font awesome – These should be used for Standard Icons within the build. 

2.1.4. jQuery – For any frontend interactivity. 

2.1.5. jquery-validation. 

2.1.6. rollbar – Should be configured to accept rollbar token in build and send errors to rollbar.

 



2.2. These additional libraries are approved for use: 

 

2.2.1. moment 

2.2.2. mustache 

2.2.3. fullcalendar 

2.2.4. jquery-ui 

2.2.5. quill 

2.2.6. slick-carousel 

2.2.7. Select2 

 

2.3. Any libraries not in this list will need to be reviewed, please make sure they are popular > 2K downloads, have either no outstanding issue or issues have to be responded to in the last month. 

2.4. Backend 

The following Dependencies should be used: 

2.4.1. dgoring/laravel-inherit-resource, all resource controllers should use this package. 

2.4.2. laravel/ui, for authorization make sure to override views with bootstrap html. 

2.4.3. Validation, ensure all fields submitted are validated even if they are optional, i.e., max text length etc.


2.4.4. Preferably in controller function with validate with function
look at the docs on dgoring/laravel-inherit-resource for how to do for the resource controllers. 

2.4.5. Any external APIs should be connected via a swapperable interface
PHP interface’s must be used for each interaction between the API and the Laravel backend. 

2.4.6. ModelPolicy gates must be defined for each model. 

2.4.7. Data passed from the backend must be on a need-to-know basis, please consider security around inputs and outputs. 

2.4.8. Unless specified to do differently here, use all facilities of laravel (database migrations, console commands, mail system etc) to achieve functionality. 

 

2.4.9. Delivery to be via your own private github repo which we will fork into our account and so we can both add are own changes but also merge your changes. 

 



2.5. Payment method: 

1.30% Deposit 

2.30% STAXO Staging Server 

3.40% Upon Sign Off 

 

2.6. Process: 

1.Complete build – Communicate weekly progress updates on build. 

2.CRM/App internal review for snags. 

3.internal snags to be actioned/signed off. 

4.Migrate to STAXO staging server. 

5. Demo 

6.Snags actions/signed off. 

 

The work will be white label and must not be used in any portfolios etc of your own. 

If this is of interest and you agree to complete white label, please provide us with a quote and timeline for the project.