WordPress Developer Needed for Bilingual Media Network and Journalist Sites
Budget / Salary$30–250
TypeFreelance project
LocationRemote
Posted2 hours ago
Website: therightnarrative.net
Languages: English and Arabic — already integrated
Contract: Fixed price with milestone payments
Deadline: Initial operational launch within 7 calendar days
About TRN
The Right Narrative (TRN) is expanding into a bilingual media network covering Sudan, Africa, the Red Sea and international affairs.
We need an experienced WordPress developer to upgrade our existing website into a professional news portal and create dedicated spaces for individual journalists operating under the TRN network.
Our design reference is **aljazeera.net** for news hierarchy, navigation and editorial presentation. The finished website must use TRN’s own branding.
**English:** https://therightnarrative.net/
**Arabic:** https://therightnarrative.net/ar/home-12-العربية/
Arabic is already integrated. Preserve and improve the existing bilingual configuration wherever practical.
## 1. Audit and architecture
- Review the current hosting, theme, page builder, plugins and multilingual configuration.
- Create a full backup, verify recovery and establish protected staging.
- Recommend the architecture for the main network and individual journalist spaces.
- Explain whether these should use one WordPress site with restricted workspaces or WordPress Multisite.
- Identify implications for permissions, bilingual content, maintenance, cost and content sharing.
- Obtain approval before changing the installation architecture or replacing the multilingual plugin.
## 2. Redesign the main TRN website
Create responsive English and Arabic layouts with:
- Header, navigation, search and language switcher.
- Editor-managed lead stories and supporting stories.
- Latest news and topical news strips.
- Breaking-news alerts with scheduling and expiry.
- Sudan, investigations, opinion and analysis sections.
- Video, podcasts and programme destinations.
- Journalist and partner directories.
- Newsletter signup and a complete network footer.
Editors must be able to manage homepage sections without coding. Arabic and English homepages must support independent editorial selection.
## 3. Dedicated journalist mini-sites
Create reusable journalist spaces that function as individual publications within TRN.
Each space should include:
- A dedicated URL, such as `/journalists/name/`, or a justified alternative.
- A personalised homepage, biography, portrait and contact options.
- Articles, investigations, programmes, video and podcast collections.
- Links to the journalist’s social accounts, YouTube and Rumble channels.
- Limited branding options within TRN’s shared design standards.
- A clear TRN network identity and navigation back to the main website.
- Mobile support and Arabic or English presentation as required.
Journalists should be able to:
- Log in to their own workspace.
- Create and manage their own content and media.
- Manage their homepage’s featured content.
- Publish independently where TRN grants that permission, or submit for review.
- Access only the content and settings assigned to them.
TRN administrators must retain control of accounts, permissions, standards and network-wide settings.
Provide a workflow for selecting journalist content for the main TRN homepage. Explain how the implementation avoids unnecessary duplicate content and handles canonical URLs.
**Launch requirement:** Deliver the reusable template and two pilot journalist spaces, plus instructions for creating additional spaces without development work.
## 4. Preserve and improve Arabic integration
- Preserve existing Arabic and English content, media and translation relationships.
- Improve RTL typography, navigation, forms and mobile layouts.
- Support original content in either language without requiring a translation.
- Test language switching across the main website and journalist spaces.
- Preserve working URLs and implement permanent redirects where changes are necessary.
- Review serving the Arabic homepage cleanly at `/ar/`.
## 5. Social media integration
The integration scope should address:
**Facebook, Instagram, X, LinkedIn, TikTok, YouTube, Rumble, Telegram and WhatsApp Channels**, plus any additional existing TRN accounts agreed at kickoff.
Distinguish between:
- TRN-owned network accounts.
- Individual journalists’ accounts.
- Social sharing by website visitors.
- Embedded content and feeds.
- Automated publishing, where supported.
Required functionality:
- Social links and sharing controls.
- Correct social-preview titles, descriptions and images.
- Platform-specific publishing text and media where supported.
- Human approval before automated distribution.
- Scheduling and publication-status tracking where available.
- Failure notifications and a safe retry process that avoids duplicate posts.
- Secure account authorisation without exposing journalists’ credentials.
- Clear control over whether a story goes to TRN accounts, journalist accounts or both.
Use official APIs, n8n or an agreed scheduling service. Do not promise automation where a platform does not support the required action.
**Your proposal must include a platform-by-platform integration matrix** showing supported actions, account requirements, approval requirements, recurring costs and any manual steps.
## 6. YouTube and Rumble connections
Connect TRN’s channels and the channels associated with the pilot journalists.
Provide:
- Dedicated video pages with embedded players.
- Channel links and subscription/follow links.
- Support for programme, playlist or series organisation.
- Video titles, descriptions, thumbnails, publication dates and duration.
- Transcript or caption fields where available.
- A way to associate the same video with its YouTube and Rumble versions.
- A designated primary player and an alternative viewing link.
Where supported by the platform and account permissions:
- Import new channel videos into WordPress as reviewable drafts.
- Detect previously imported videos to prevent duplicates.
- Preserve editorial control over titles, descriptions and website publication.
- Configure approved upload or publishing workflows if included in the agreed scope.
Clearly distinguish **embedding, importing video metadata and uploading videos**. These are separate capabilities. Specify any Rumble limitations and provide a workable manual alternative where automation is unavailable.
Do not download or copy third-party videos without authorisation. Large video originals should not be stored in the public WordPress media library as part of this project.
## 7. Content, SEO and performance
- Preserve existing articles, authors, media and publication dates.
- Populate priority sections with agreed existing content.
- Remove placeholder text and repair navigation issues.
- Organise priority categories and tags.
- Configure titles, descriptions, canonical URLs, hreflang, sitemaps and social metadata.
- Optimise image delivery, caching and mobile performance.
- Test search, forms, players, links and redirects.
State the content-migration and page-population allowance included in your price.
## 8. Security and editorial control
- Configure appropriate administrator, editor and journalist permissions.
- Test that journalists cannot edit another journalist’s content or settings without authorisation.
- Protect staging and account credentials.
- Configure backups and document recovery.
- Provide a review-before-publication option.
- Keep restricted evidence and source information outside public website storage.
The full TRN Intelligence Database and Sudan War Media Archive are separate projects. This website should support future integration through documented fields and interfaces.
## Deliverables
- Operational bilingual TRN website.
- Reusable journalist mini-site template and two functioning pilot spaces.
- Tested journalist permissions and main-network featuring workflow.
- Agreed social integrations and YouTube/Rumble connections.
- Platform integration matrix and configuration documentation.
- Redirect map and preserved existing content.
- Source code and custom assets owned by TRN.
- Plugin/licence inventory and recurring-cost breakdown.
- Backup, deployment and rollback instructions.
- Recorded administrator and journalist training.
- At least 14 days of post-launch bug-fix support.
Use properly licensed software only. Do not modify WordPress core files.
## Required experience
- WordPress news or media websites.
- Arabic RTL and multilingual development.
- Multi-author publishing, permissions and preferably WordPress Multisite.
- Social APIs, n8n or publishing-service integrations.
- YouTube integration and demonstrable understanding of Rumble options.
- SEO-preserving migrations and performance optimisation.
## Include in your proposal
1. Relevant live examples, including Arabic RTL and multi-author/network work.
2. Your recommended architecture and reasons.
3. A realistic seven-day delivery plan and team availability.
4. Your social-platform integration matrix.
5. Your proposed YouTube and Rumble approach.
6. Fixed price and milestone breakdown.
7. All licences, subscription costs, assumptions and exclusions.
8. Required access and materials from TRN.
9. Post-launch support terms.
**Please apply only if you can start immediately and have the capacity to deliver the agreed launch scope within seven days.**
Languages: English and Arabic — already integrated
Contract: Fixed price with milestone payments
Deadline: Initial operational launch within 7 calendar days
About TRN
The Right Narrative (TRN) is expanding into a bilingual media network covering Sudan, Africa, the Red Sea and international affairs.
We need an experienced WordPress developer to upgrade our existing website into a professional news portal and create dedicated spaces for individual journalists operating under the TRN network.
Our design reference is **aljazeera.net** for news hierarchy, navigation and editorial presentation. The finished website must use TRN’s own branding.
**English:** https://therightnarrative.net/
**Arabic:** https://therightnarrative.net/ar/home-12-العربية/
Arabic is already integrated. Preserve and improve the existing bilingual configuration wherever practical.
## 1. Audit and architecture
- Review the current hosting, theme, page builder, plugins and multilingual configuration.
- Create a full backup, verify recovery and establish protected staging.
- Recommend the architecture for the main network and individual journalist spaces.
- Explain whether these should use one WordPress site with restricted workspaces or WordPress Multisite.
- Identify implications for permissions, bilingual content, maintenance, cost and content sharing.
- Obtain approval before changing the installation architecture or replacing the multilingual plugin.
## 2. Redesign the main TRN website
Create responsive English and Arabic layouts with:
- Header, navigation, search and language switcher.
- Editor-managed lead stories and supporting stories.
- Latest news and topical news strips.
- Breaking-news alerts with scheduling and expiry.
- Sudan, investigations, opinion and analysis sections.
- Video, podcasts and programme destinations.
- Journalist and partner directories.
- Newsletter signup and a complete network footer.
Editors must be able to manage homepage sections without coding. Arabic and English homepages must support independent editorial selection.
## 3. Dedicated journalist mini-sites
Create reusable journalist spaces that function as individual publications within TRN.
Each space should include:
- A dedicated URL, such as `/journalists/name/`, or a justified alternative.
- A personalised homepage, biography, portrait and contact options.
- Articles, investigations, programmes, video and podcast collections.
- Links to the journalist’s social accounts, YouTube and Rumble channels.
- Limited branding options within TRN’s shared design standards.
- A clear TRN network identity and navigation back to the main website.
- Mobile support and Arabic or English presentation as required.
Journalists should be able to:
- Log in to their own workspace.
- Create and manage their own content and media.
- Manage their homepage’s featured content.
- Publish independently where TRN grants that permission, or submit for review.
- Access only the content and settings assigned to them.
TRN administrators must retain control of accounts, permissions, standards and network-wide settings.
Provide a workflow for selecting journalist content for the main TRN homepage. Explain how the implementation avoids unnecessary duplicate content and handles canonical URLs.
**Launch requirement:** Deliver the reusable template and two pilot journalist spaces, plus instructions for creating additional spaces without development work.
## 4. Preserve and improve Arabic integration
- Preserve existing Arabic and English content, media and translation relationships.
- Improve RTL typography, navigation, forms and mobile layouts.
- Support original content in either language without requiring a translation.
- Test language switching across the main website and journalist spaces.
- Preserve working URLs and implement permanent redirects where changes are necessary.
- Review serving the Arabic homepage cleanly at `/ar/`.
## 5. Social media integration
The integration scope should address:
**Facebook, Instagram, X, LinkedIn, TikTok, YouTube, Rumble, Telegram and WhatsApp Channels**, plus any additional existing TRN accounts agreed at kickoff.
Distinguish between:
- TRN-owned network accounts.
- Individual journalists’ accounts.
- Social sharing by website visitors.
- Embedded content and feeds.
- Automated publishing, where supported.
Required functionality:
- Social links and sharing controls.
- Correct social-preview titles, descriptions and images.
- Platform-specific publishing text and media where supported.
- Human approval before automated distribution.
- Scheduling and publication-status tracking where available.
- Failure notifications and a safe retry process that avoids duplicate posts.
- Secure account authorisation without exposing journalists’ credentials.
- Clear control over whether a story goes to TRN accounts, journalist accounts or both.
Use official APIs, n8n or an agreed scheduling service. Do not promise automation where a platform does not support the required action.
**Your proposal must include a platform-by-platform integration matrix** showing supported actions, account requirements, approval requirements, recurring costs and any manual steps.
## 6. YouTube and Rumble connections
Connect TRN’s channels and the channels associated with the pilot journalists.
Provide:
- Dedicated video pages with embedded players.
- Channel links and subscription/follow links.
- Support for programme, playlist or series organisation.
- Video titles, descriptions, thumbnails, publication dates and duration.
- Transcript or caption fields where available.
- A way to associate the same video with its YouTube and Rumble versions.
- A designated primary player and an alternative viewing link.
Where supported by the platform and account permissions:
- Import new channel videos into WordPress as reviewable drafts.
- Detect previously imported videos to prevent duplicates.
- Preserve editorial control over titles, descriptions and website publication.
- Configure approved upload or publishing workflows if included in the agreed scope.
Clearly distinguish **embedding, importing video metadata and uploading videos**. These are separate capabilities. Specify any Rumble limitations and provide a workable manual alternative where automation is unavailable.
Do not download or copy third-party videos without authorisation. Large video originals should not be stored in the public WordPress media library as part of this project.
## 7. Content, SEO and performance
- Preserve existing articles, authors, media and publication dates.
- Populate priority sections with agreed existing content.
- Remove placeholder text and repair navigation issues.
- Organise priority categories and tags.
- Configure titles, descriptions, canonical URLs, hreflang, sitemaps and social metadata.
- Optimise image delivery, caching and mobile performance.
- Test search, forms, players, links and redirects.
State the content-migration and page-population allowance included in your price.
## 8. Security and editorial control
- Configure appropriate administrator, editor and journalist permissions.
- Test that journalists cannot edit another journalist’s content or settings without authorisation.
- Protect staging and account credentials.
- Configure backups and document recovery.
- Provide a review-before-publication option.
- Keep restricted evidence and source information outside public website storage.
The full TRN Intelligence Database and Sudan War Media Archive are separate projects. This website should support future integration through documented fields and interfaces.
## Deliverables
- Operational bilingual TRN website.
- Reusable journalist mini-site template and two functioning pilot spaces.
- Tested journalist permissions and main-network featuring workflow.
- Agreed social integrations and YouTube/Rumble connections.
- Platform integration matrix and configuration documentation.
- Redirect map and preserved existing content.
- Source code and custom assets owned by TRN.
- Plugin/licence inventory and recurring-cost breakdown.
- Backup, deployment and rollback instructions.
- Recorded administrator and journalist training.
- At least 14 days of post-launch bug-fix support.
Use properly licensed software only. Do not modify WordPress core files.
## Required experience
- WordPress news or media websites.
- Arabic RTL and multilingual development.
- Multi-author publishing, permissions and preferably WordPress Multisite.
- Social APIs, n8n or publishing-service integrations.
- YouTube integration and demonstrable understanding of Rumble options.
- SEO-preserving migrations and performance optimisation.
## Include in your proposal
1. Relevant live examples, including Arabic RTL and multi-author/network work.
2. Your recommended architecture and reasons.
3. A realistic seven-day delivery plan and team availability.
4. Your social-platform integration matrix.
5. Your proposed YouTube and Rumble approach.
6. Fixed price and milestone breakdown.
7. All licences, subscription costs, assumptions and exclusions.
8. Required access and materials from TRN.
9. Post-launch support terms.
**Please apply only if you can start immediately and have the capacity to deliver the agreed launch scope within seven days.**
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.