Hi Theresa, thank you for your question (and sorry for my slow reply here)
It's absolutely ok to reference parts of a production site you're working on and highlight the bits you are responsible for. In fact, I'd argue this is preferable to a demo site full of generic to-do apps and calculators.
What I am looking for is clear evidence that an individual has the skills and competency their CV says they have - a series of blog posts or similar detailing how you implemented new features or tracked down tricky bugs would be an excellent way to demonstrate this.
It's literally better to have no portfolio site than a sub-standard portfolio site or a site you have threw together for the sake or having one.
Hi Theresa, thank you for your question (and sorry for my slow reply here)
It's absolutely ok to reference parts of a production site you're working on and highlight the bits you are responsible for. In fact, I'd argue this is preferable to a demo site full of generic to-do apps and calculators.
What I am looking for is clear evidence that an individual has the skills and competency their CV says they have - a series of blog posts or similar detailing how you implemented new features or tracked down tricky bugs would be an excellent way to demonstrate this.
It's literally better to have no portfolio site than a sub-standard portfolio site or a site you have threw together for the sake or having one.
Hope that's useful! :)
Thank you, it was super useful!