CASE FILE / ROCKFORCE

One clear Rockforce site for customers, employers, and workforce applicants.

Rockforce's owner tried to build the site himself on WordPress.com, but practical build limits took time away from the business. FunkPd handled the build and clear paths for customers and workforce applicants within the existing platform, so the site could serve both audiences without a platform move.

PlatformWordPress with Elementor
ScopeAbout five or six pages, plus a blog
EditingFamiliar WordPress editing with shared site parts
01 // Interface preview

The finished site and the workforce application work together.

The public site routes customers and employers to the right service path. The workforce application gives candidates a structured next step inside the same WordPress.com build.

Rockforce finished desktop site showing customer, employer, and workforce audience paths
Route customers, employers, and applicants to the right next step.
Rockforce workforce application showing structured role, experience, availability, and CV fields
Collect role, experience, availability, and a CV before the first review.
02 // The brief

Positioning and structure made the constraint workable.

The owner needed business time back without moving platforms. FunkPd shaped the positioning, structured the pages, and implemented the forms and application inside WordPress.com.

The client supplied the site copy. FunkPd wrote some blog posts and kept the editing path familiar through WordPress and Elementor.

03 // What was built

Clear routes, a structured application, and practical editing.

  • Audience routingSeparate routes for employers, contractors and recruitment, joining the workforce, and general contact keep each visitor on the right next step.
  • Structured workforce intakeThe application form asks for role, experience, availability, and CV, giving the first review more useful screening context.
  • Shared editable layoutsShared header and footer parts can be edited once, then reused across the site. Focused Elementor controls support normal content and layout edits.
  • Familiar editingThe build extends the existing WordPress and Elementor platform, so normal updates stay in a familiar editing path.
04 // Scope boundary

A clear fit for one customer and applicant site.

Who this fits: Businesses serving customers and applicants through one site. The approach keeps both paths clear, then leaves normal edits in the hands of the people running the business. See the WordPress rebuild path.

05 // Next step

Tell me what the site needs to do and who will run it.

Share what you need and when you need it. I'll define the scope and next step.

Operator Identity

Built and fixed by one person.

You work with Nolan Phelps directly. He does the diagnosis, scope, build, fixes, and handoff himself.

No sales layer. No project manager. No outsource chain.

Since 2017WinnipegWordPress rescue
Nolan Phelps

Nolan Phelps

FunkPd