
Web App Creation with beautiful UX design & Open Source Modules
- or -
Post a project like this$5.0k
- Posted:
- Proposals: 51
- Remote
- #4270720
- Expired
Full-stack Developer/ Shopify/ WordPress/ Product Uploading,Admin Support,Data Scraping, Mining, Extraction, Data Entry, Researcher
Top-Rated Web & Graphic Designer | Database Expert | Business Analysis| Python Developer


Expert Web Developer - N8N, Wordpress, Shopify, Opencart, Laravel, Vue, React, PHP

Web & Mobile App Developer | PHP, Laravel, Flutter, iOS, WordPress, Andriod Expert


Flutter | WordPress |Designer |Recruitment | Shopify | Wix | PHP | Laravel | ReactJs | | VueJS | Cross Platform | Digital Marketing | SEO

4846464102179698579517352228470808511193042937407615862099344823887796424336
Description
Experience Level: Expert
We need to develop a new online web app. Our current solution is built on WordPress and is outgrowing the native functionality of WordPress. Moreover, WordPress isn't designed for the specific use case, so we're finding it quite constraining. We are considering solutions that use open source elements to build a whole new app or adapt WordPress functionality significantly to be fit for our purpose. The system has the following modules:
1. Login
Security is very important. Use widely available frameworks such as Passport, Keycloak etc.
2. User management
Five levels of users: admins, editors, team lead, team member, team reviewer. Admin, editor and team lead interface is back-end, but team lead appointing team members and team reviewers must be front-end and well designed. A number of parameters specific to each user will be entered by the team lead and team members.
3. Teams and access permissions
Admins can create teams and appoint a team lead. Team leads can add team members and team reviewers. Access permissions need to be set to prevent teams from viewing any info about other teams. Only admins and editors can view info across teams. Team leads can view info of team members.
4. AI prompt creation and response handling
Admins or editors will write AI prompts in the back-end. The system must be designed to accept multiple parameters from admin or editors for teams and individual team members. The editors will either ask the system to find all team members who match certain parameters or manually select which team members to include for each prompt - this may range from 1 to 100s. The system will then generate unique prompts for each team member based on the parameters provided. The system will send the prompt to the AI - such as Chat GPT / Open AI), accept AI responses, and generate information in a user-friendly format. This information must be editable by the team members, which means a text input and editing functionality is needed, along with text character limit checks.
5. Image creation and editing
We will create two types of images - 1. open 2. branded. For the branded images, we will pre-define certain templates and users will be able to upload backgrounds and text. For the open images, we'd like AI to find and select royalty-free images. Users should also be able to upload their own images. Simple image editing functionality needed to accept image uploads, and allow users to input text to overlay images. Must allow text background, font, size and colour editing. Also provide simple image correction - crop, resize, contrast editing by user. Again, use open source modules such as GIMP or PhotoDemon.
6. Scheduling calendar & workflow
Calendar view and scheduling functionality where users can view and edit what information goes out on which days and at what times. Flexible workflows will be set up by the admin to allow completed information to be sent to team reviewers for approval before the scheduling is finalised. Reviewers should be able to add comments and information back to team members for correction. Admin should be able to define custom workflows, e.g. editor -> team member -> (rejected) editor -> team member -> reviewer -> scheduled.
7. API interaction
Once the user has completed work on the AI response and image editing, and the team reviewers have approved the work, the information will be sent to 1-4 different APIs. The API calls are very simple and straightforward via REST API. The system must interface with the APIs, provide information in the pre-defined formats and register the API's acceptance or rejection of the information. If the information is rejected, a user-friendly prompt will need to be generated. API connections will require teams to renew authentication every 60 days, which will need to be built into the user interface.
8. Web and mobile interface - user and admin back-end
Speed of functionality and a simple but beautiful user interface are very important. We will expect a designer to work on this and we want to see framework designs and UX options. We will provide brand guidelines. The interface will require minor personalisation for teams too - e.g. a team image, different header / menu background colour.
9. Reporting
Basic reporting to admin, team leaders and team members showing how much information has been processed and successfully scheduled. Some APIs will allow us to view further stats for the information shared. In those cases we will also like to see those stats at the team member, team, and admin level.
The system must be created with free / open source modules and should use code and frameworks that are already available as far as possible. Clear documentation and best practices for code required. Must be setup on Github.
You will be required to sign an NDA before details of the nature of this project are disclosed.
1. Login
Security is very important. Use widely available frameworks such as Passport, Keycloak etc.
2. User management
Five levels of users: admins, editors, team lead, team member, team reviewer. Admin, editor and team lead interface is back-end, but team lead appointing team members and team reviewers must be front-end and well designed. A number of parameters specific to each user will be entered by the team lead and team members.
3. Teams and access permissions
Admins can create teams and appoint a team lead. Team leads can add team members and team reviewers. Access permissions need to be set to prevent teams from viewing any info about other teams. Only admins and editors can view info across teams. Team leads can view info of team members.
4. AI prompt creation and response handling
Admins or editors will write AI prompts in the back-end. The system must be designed to accept multiple parameters from admin or editors for teams and individual team members. The editors will either ask the system to find all team members who match certain parameters or manually select which team members to include for each prompt - this may range from 1 to 100s. The system will then generate unique prompts for each team member based on the parameters provided. The system will send the prompt to the AI - such as Chat GPT / Open AI), accept AI responses, and generate information in a user-friendly format. This information must be editable by the team members, which means a text input and editing functionality is needed, along with text character limit checks.
5. Image creation and editing
We will create two types of images - 1. open 2. branded. For the branded images, we will pre-define certain templates and users will be able to upload backgrounds and text. For the open images, we'd like AI to find and select royalty-free images. Users should also be able to upload their own images. Simple image editing functionality needed to accept image uploads, and allow users to input text to overlay images. Must allow text background, font, size and colour editing. Also provide simple image correction - crop, resize, contrast editing by user. Again, use open source modules such as GIMP or PhotoDemon.
6. Scheduling calendar & workflow
Calendar view and scheduling functionality where users can view and edit what information goes out on which days and at what times. Flexible workflows will be set up by the admin to allow completed information to be sent to team reviewers for approval before the scheduling is finalised. Reviewers should be able to add comments and information back to team members for correction. Admin should be able to define custom workflows, e.g. editor -> team member -> (rejected) editor -> team member -> reviewer -> scheduled.
7. API interaction
Once the user has completed work on the AI response and image editing, and the team reviewers have approved the work, the information will be sent to 1-4 different APIs. The API calls are very simple and straightforward via REST API. The system must interface with the APIs, provide information in the pre-defined formats and register the API's acceptance or rejection of the information. If the information is rejected, a user-friendly prompt will need to be generated. API connections will require teams to renew authentication every 60 days, which will need to be built into the user interface.
8. Web and mobile interface - user and admin back-end
Speed of functionality and a simple but beautiful user interface are very important. We will expect a designer to work on this and we want to see framework designs and UX options. We will provide brand guidelines. The interface will require minor personalisation for teams too - e.g. a team image, different header / menu background colour.
9. Reporting
Basic reporting to admin, team leaders and team members showing how much information has been processed and successfully scheduled. Some APIs will allow us to view further stats for the information shared. In those cases we will also like to see those stats at the team member, team, and admin level.
The system must be created with free / open source modules and should use code and frameworks that are already available as far as possible. Clear documentation and best practices for code required. Must be setup on Github.
You will be required to sign an NDA before details of the nature of this project are disclosed.
Projects Completed
32
Freelancers worked with
27
Projects awarded
71%
Last project
30 Mar 2026
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

Hi, if you want to move away from WordPress, would you consider .net based solution? Thanks
-

Hello Farhad,
Do you have any preferences for the UI/UX design style or color schemes?
Are there any existing systems or APIs that the new web app needs to integrate with?
within what timeframe are you looking to get this done?
11087961108737
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies