Skip to content

Instantly share code, notes, and snippets.

Avatar
🏠
Working from home

Joao Garin joaogarin

🏠
Working from home
View GitHub Profile
@joaogarin
joaogarin / jobiqo-component.md
Last active Apr 8, 2021
Page and component structure
View jobiqo-component.md

Summary

This document explains a generic approach to component structures in jobiqo-decoupled.

Naming pattern

Every component should use PascalCase naming in the folder (which is also required in react for components) like ResumeCompleteness but pages use a kebab-case like job-apply this is because folders map to URL's and so makes it cleaner and simpler to have proper urls like this in nextjs

@joaogarin
joaogarin / gist:c1aba92b91634806ea7913f5038c83fa
Last active Jun 29, 2019
Technical proposal : Job Search Facet SEO
View gist:c1aba92b91634806ea7913f5038c83fa

We would essentially treat each occupation & region as a “category” of a job search. Inside category all other filters would be excluded. That would mean that in the front-end we have a route like /jobs/:arg1/:arg2

Meaning that we basically need to ask drupal what our arg1 and arg2 are. So when getting something like /manager/wien we call Drupal with this and drupal will respond like :

[
  "arg1" : "occupation"
  "arg2" : "region"