Soroush Neyestani

Software Engineer

Application Architect

Enterprise Application Developer

Technical Author & Educator

Soroush Neyestani

Software Engineer

Application Architect

Enterprise Application Developer

Technical Author & Educator

Download CV Contact Me

Gufeli — Multilingual Village Community Portal

WordPress · HTML · Community CMS · Multilingual Publishing · Local Hosting · WebView Delivery

A multilingual community portal created around 2014 for the village of Gufel, designed to let local residents publish and maintain village information, news, photos, memories, events, geography, marketplace content, and community updates. The project began as a simple HTML prototype, was approved by the community, and was then rebuilt as a WordPress-based publishing system that remained publicly available for approximately three to four years.

1. Project Overview

Gufeli was a community information portal created for the village of Gufel around 2014.

The original request was straightforward:

Create a digital place where the village can introduce itself and publish anything relevant to local life.

The system was intended to support content such as:

  • village information,
  • news,
  • photos,
  • events,
  • memories,
  • geography,
  • local marketplace content,
  • articles,
  • community announcements,
  • and other locally relevant material.

The project started with a very simple HTML prototype.

After the community approved the concept, I rebuilt the solution using WordPress so non-technical users could manage and publish content themselves.

2. Project Evolution

The project followed a simple but effective progression:

Village Requirement
      ↓
Simple HTML Prototype
      ↓
Community Approval
      ↓
WordPress Implementation
      ↓
Local Hosting
      ↓
Public Community Portal

This was a practical example of validating the idea before investing in a richer CMS implementation.

3. Period

Approximate development period:

2014

The project then remained publicly accessible for approximately:

3–4 years

4. Community Context

The project was created for a local village community.

At the time, social platforms were not used locally in the same way they are today.

A dedicated community website acted as a shared digital space for:

  • village identity,
  • local information,
  • photos,
  • announcements,
  • community history,
  • and services.

5. Main Goal

The primary goal was:

Give the village its own digital publishing platform.

The community wanted to be able to add new information without depending on a developer for every update.

This made a CMS-based solution a natural fit.

6. Initial HTML Prototype

The first version was intentionally minimal.

It was created in HTML to demonstrate:

  • page structure,
  • navigation,
  • basic visual identity,
  • information categories,
  • and the overall concept.

The prototype was not intended to be the permanent system.

Its purpose was:

Show Idea
   ↓
Get Approval
   ↓
Build Proper CMS

7. WordPress Migration

After approval, the system was rebuilt using WordPress.

This allowed:

  • easier publishing,
  • image uploads,
  • article creation,
  • category-based content,
  • editorial updates,
  • and independent content management by local users.

This was a practical upgrade from a static site to a maintainable content platform.

8. My Role

I handled the complete technical delivery.

Confirmed responsibilities included:

  • HTML prototype,
  • web design,
  • WordPress installation,
  • WordPress configuration,
  • theme customization,
  • page structure,
  • navigation,
  • multilingual setup,
  • content structure,
  • server setup,
  • deployment,
  • access configuration,
  • and operational handover.

There was no separate technical team.

9. Logo Ownership

The Gufeli logo was created by my father.

My work covered:

  • the website,
  • implementation,
  • CMS,
  • deployment,
  • and overall digital product.

This ownership boundary should remain explicit.

10. Languages

The portal supported three languages:

  • Persian
  • English
  • Kurmanji Kurdish

This made the project multilingual rather than a single-language village website.

11. Why Multilingual Support Mattered

The site had to serve a community with different language needs.

A multilingual structure supported:

  • local residents,
  • people living outside the village,
  • visitors,
  • and potentially members of the community who preferred different languages.

This expanded the site beyond a purely local-language portal.

12. Content Areas

Known sections included concepts such as:

  • Home
  • Village introduction
  • News
  • Images
  • Geography
  • Articles
  • Marketplace
  • Memories
  • Events / occasions
  • Contact
  • About
  • Shop
  • Login
  • Requests

The exact structure evolved over time.

13. News

The portal could publish village news.

This allowed local updates to be communicated through a dedicated platform instead of relying on informal channels.

14. Photos

Image publishing was a major part of the portal.

The community uploaded photographs related to:

  • village life,
  • people,
  • events,
  • landscape,
  • history,
  • and local activities.

These photographs were considered sensitive or personally important by some local users, which later influenced how the archive was handled.

15. Memories

The site included space for memories and historical/community stories.

This gave the portal a cultural and archival role, not only an informational one.

16. Geography

The project included geographical or village-location content.

This helped describe the physical context of the village.

17. Marketplace

A marketplace/community-commerce section was also implemented.

This allowed local commercial or exchange-oriented information to be published inside the same community portal.

18. Shop

A shop-related section existed in the later structure.

This expanded the site beyond simple informational publishing.

19. Events and Occasions

The original requirement explicitly included publishing occasions and events.

This made the portal useful for:

  • local announcements,
  • celebrations,
  • community dates,
  • and shared events.

20. Community Publishing

One of the most important aspects of the WordPress implementation was that local users could manage content themselves.

The site was not designed as a developer-only publishing system.

After deployment, community members could add:

  • news,
  • photos,
  • articles,
  • and other content.

21. Local Hosting

The application was installed on infrastructure associated with the village telecommunications facility.

This effectively acted as the local server environment.

The portal was therefore not hosted as a conventional cloud SaaS product.

22. Server Ownership

I handled the server-side setup as part of the overall deployment.

This included making the WordPress installation available to the users who needed access.

23. Shared Access

The local server environment allowed multiple authorized community members to access and manage the system.

This supported community-managed publishing.

24. Public Operation

The project was not only a prototype.

The WordPress version was made public and remained active for approximately three to four years.

This is important portfolio evidence because it demonstrates:

  • real deployment,
  • real users,
  • real content,
  • and long-term operation.

25. Why the Project Became Less Active

The platform gradually became less useful because of significant migration away from the village.

As the local population and community participation declined, content activity also declined.

The project did not stop because of a technical failure.

26. Social Context

At the time, dedicated community portals had more practical value in some regions because mainstream social platforms were not always the primary place for local digital community activity.

Gufeli functioned as:

a village-owned digital community space

rather than simply a brochure website.

27. Mobile / WebView Requirement

The project also had a mobile delivery expectation.

The requested mobile approach was a WebView-style wrapper around the web portal rather than a fully independent mobile product.

At the time, Nokia/Symbian devices were still important for the target users.

The surviving evidence primarily documents the web/CMS side, so the mobile layer should be described conservatively.

28. Why WebView Made Sense

For a content-driven platform, a WebView-style delivery model reduced duplication.

Instead of maintaining:

Website Content
+
Separate Mobile Content

the same CMS could serve both.

This was practical for a small community project.

29. Design Evolution

The visual design evolved from a very simple early layout to a more polished community portal.

The surviving screenshots show:

  • an early village-header layout,
  • later dark/green visual design,
  • Persian navigation,
  • village imagery,
  • and structured content sections.

30. Typography Note

Some current screenshots do not display the original typography exactly because the historical fonts are no longer installed on the current machine.

The screenshot should therefore be treated as archival evidence rather than a pixel-perfect reconstruction of the original visual presentation.

31. Content Management

WordPress was selected because it gave the community a practical way to manage content without requiring custom development.

This included:

  • creating posts,
  • publishing images,
  • organizing sections,
  • editing pages,
  • and maintaining the portal.

32. Build-vs-Custom Decision

The project demonstrates a useful engineering decision:

Use a CMS when the primary problem is publishing and content management.

A custom application would have created unnecessary maintenance.

The actual business need was:

Community Publishing

not:

Custom Software Complexity

33. Full Delivery Ownership

This project is a good example of broad ownership rather than deep technical complexity.

The work covered:

Prototype
+
Design
+
CMS
+
Multilingual Structure
+
Server
+
Deployment
+
User Access
+
Operational Handover

34. Community-Centered Design

The system was designed for non-technical users.

That meant the interface and publishing workflow needed to remain simple.

WordPress helped make this possible.

35. Information Architecture

The portal grouped different kinds of village information into understandable categories.

This included both informational and social content.

Conceptually:

Village
├── News
├── Photos
├── Geography
├── Memories
├── Articles
├── Events
├── Marketplace
├── Shop
└── Community Services

36. Cultural Archive Role

Because the portal stored:

  • local photos,
  • memories,
  • village information,
  • and community history,

it also functioned as a lightweight cultural archive.

This became more significant as people migrated away from the village.

37. Data Sensitivity

Some local photographs were considered sensitive or personally important by community members.

For that reason, after the system stopped being actively maintained, I did not attempt to recover or republish the historical archive.

This is the correct ownership boundary.

38. Source Availability

The original WordPress database and deployed system are no longer available in my current archive.

The surviving evidence includes:

  • logo,
  • screenshots,
  • early prototype visuals,
  • and project memory.

This should be stated honestly.

39. Technology Stack

Confirmed:

  • HTML
  • CSS
  • WordPress
  • multilingual content
  • local server deployment
  • browser-based CMS
  • WebView-oriented mobile delivery concept

The exact historical:

  • WordPress version,
  • PHP version,
  • database version,
  • theme framework,

are not currently documented.

40. Project Status

Recommended status:

Production / Public Community Portal — Operated ~3–4 Years

Later discontinued primarily because of declining local participation following migration.

41. Portfolio Positioning

Recommended title:

Gufeli — Multilingual Village Community Portal

Alternative:

Gufeli — WordPress Community Publishing Platform

42. Portfolio Classification

Primary:

  • Community Platform
  • WordPress
  • CMS
  • Multilingual Web

Secondary:

  • Local Hosting
  • Web Design
  • Information Architecture
  • WebView
  • Community Publishing

43. CV Relevance

Recommended:

Tier C — Breadth / Early Production Project

The implementation itself was relatively simple.

However, it is useful evidence of:

  • early client-facing delivery,
  • complete ownership,
  • multilingual publishing,
  • real deployment,
  • and multi-year public operation.

44. Career Evidence

The project demonstrates:

  • End-to-End Delivery
  • WordPress
  • CMS Architecture
  • HTML/CSS
  • Multilingual Publishing
  • Server Setup
  • Deployment
  • Information Architecture
  • User Handover
  • Production Operation

45. Website Hero

Gufeli — Multilingual Village Community Portal

WordPress · HTML · Multilingual CMS · Community Publishing

Built and deployed a multilingual community portal for the village of Gufel, beginning with a simple HTML prototype and evolving into a WordPress-based publishing platform where local users could manage news, photos, memories, events, marketplace content, and village information.

46. Website Project Card

Gufeli

WordPress · Multilingual Community Portal

Designed, deployed, and operated a Persian/English/Kurmanji village portal that enabled local users to publish news, photos, events, memories, marketplace content, and community information.

47. Short Website Card

Gufeli Community Portal

A multilingual WordPress community platform for village news, photos, events, history, local information, and marketplace content.

48. One-Line Description

Built and deployed a multilingual WordPress community portal for the village of Gufel that remained publicly active for approximately three to four years.

49. CV Entry

Gufeli — Multilingual Village Community Portal / WordPress

Designed and delivered a multilingual community publishing platform for the village of Gufel around 2014. Started with an HTML prototype, then installed and customized WordPress, configured the content structure, multilingual publishing, local server deployment, and user access. The public portal supported Persian, English, and Kurmanji content including news, photos, memories, events, geography, marketplace and shop sections, and remained active for approximately three to four years.

50. Short CV Entry

Built and deployed a Persian/English/Kurmanji WordPress community portal for a village, supporting local publishing and remaining publicly active for ~3–4 years.

51. Interview Story — Situation

A village community wanted its own digital platform where residents could publish and share local information.

They needed something flexible enough to support many content types.

52. Interview Story — Task

Create an easy-to-use system for:

  • village introduction,
  • photos,
  • news,
  • events,
  • memories,
  • marketplace content,
  • and future content types.

53. Interview Story — Action

I first built a very simple HTML prototype to validate the concept.

After approval, I installed and configured WordPress, built the site structure, implemented multilingual support, handled the deployment and server setup, and enabled local users to publish content themselves.

54. Interview Story — Result

The portal was publicly used for approximately three to four years.

It became less active later because migration reduced participation in the local community.

55. Technical Interview Version

“Around 2014, a village community asked me to create a platform where they could publish anything related to the village—news, photos, memories, events, local businesses, geography, and so on. I first made a simple HTML prototype so they could approve the concept. After that I moved the system to WordPress, handled the theme and site structure, multilingual support in Persian, English and Kurmanji, local server deployment, and user access. The community could then manage content themselves. It stayed public for around three to four years.”

56. Architecture Lesson

The project demonstrates:

Validate cheaply, then implement with the right platform.

The path was:

HTML Prototype
      ↓
Approval
      ↓
WordPress CMS

This avoided overbuilding before the requirement was validated.

57. Platform Selection Lesson

A CMS was the correct architecture because the dominant requirement was content publishing.

The community needed:

Create
Edit
Upload
Organize
Publish

WordPress already solved those problems.

58. Operational Lesson

The long-term success of a community platform depends not only on technology but also on:

  • population,
  • participation,
  • contributors,
  • and continued local engagement.

The platform remained technically usable, but social conditions changed.

59. Multilingual Lesson

Multilingual content adds complexity in:

  • navigation,
  • page structure,
  • content duplication,
  • editorial workflow,
  • and typography.

Even a simple CMS project becomes more substantial when several languages are involved.

60. Historical Value

The project is also useful in a portfolio because it shows early experience with:

  • client requirements,
  • production deployment,
  • community users,
  • and operational longevity.

It provides context for later, more complex systems.

61. Suggested Tags

WordPress
HTML
CSS
CMS
Multilingual
Persian
English
Kurmanji
Community Portal
Village Portal
Local Hosting
WebView
Content Management
Information Architecture
Web Design
Deployment

62. Suggested Website Metadata

Page Title

Gufeli — Multilingual Village Community Portal

Meta Description

A multilingual WordPress community portal created for the village of Gufel, supporting local news, photos, memories, events, geography, marketplace content, and community-managed publishing in Persian, English, and Kurmanji.

Suggested Slug

/gufeli-community-portal

63. Evidence Boundaries

Safe to claim:

  • approximately 2014,
  • village of Gufel,
  • HTML prototype,
  • WordPress implementation,
  • WordPress installed/configured by me,
  • server/deployment handled by me,
  • multilingual Persian/English/Kurmanji,
  • local users could publish content,
  • public for approximately 3–4 years,
  • news/photos/events/memories/geography/marketplace/shop functionality,
  • logo created by my father,
  • local telecommunications infrastructure used as server environment,
  • WebView-style mobile requirement,
  • later decline caused by reduced local participation/migration.

Avoid claiming without recovered source:

  • exact traffic,
  • exact number of users,
  • exact WordPress/plugin versions,
  • exact Symbian application implementation details,
  • exact uptime,
  • exact content volume.

64. Final Portfolio Statement

Around 2014, I designed and delivered Gufeli, a multilingual community portal for the village of Gufel. The project began as a simple HTML prototype used to validate the concept, then evolved into a WordPress-based publishing system that I installed, customized, deployed, and configured end-to-end. The portal supported Persian, English, and Kurmanji content and allowed local users to publish village news, photographs, memories, events, geography, marketplace information, shop content, and other community material. It was hosted on local village telecommunications infrastructure and remained publicly active for approximately three to four years. The project later became less active as migration reduced local participation. The logo was created by my father; all web/CMS implementation and deployment work was mine.

65. One-Line Summary

Built and operated a multilingual WordPress village community portal that remained public for approximately three to four years.

66. Ultra-Short Portfolio Label

Gufeli — WordPress · Multilingual Community Portal · Local Publishing

Tags: