You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each performance recording by an artist on a given episode will be extracted from the main file and given special pages on http://brother.ly, so that artists can directly link their performances from elsewhere on the Web. Although this implementation is pretty straightforward, there's still some questions regarding creating the best URL routing scheme for this feature. Ideally, a performance URL would look something like http://brother.ly/performances/some-artist-at-brotherly-xxx, but this may be a bit too long even if it's human readable. Perhaps we could use http://brother.ly/episodes/one/performances/some-artist as an alternative.
From a SEO perspective, it seems a better choice to have a URL with less "tiers". Performance pages are likely going to be hit the most, given they're the easiest things to share, so we want to make sure that we're deploying a feature that is optimized both for direct Web searches and sharing over social media networks like Twitter and Facebook.
Mock up layout for performance pages
Implement in performance show views
Slice existing video and audio recordings into performances
Create data migration to batch-upload content to the staging server
After QA, run the batch upload on production after deployment of v2.1.0
The text was updated successfully, but these errors were encountered:
Each performance recording by an artist on a given episode will be extracted from the main file and given special pages on http://brother.ly, so that artists can directly link their performances from elsewhere on the Web. Although this implementation is pretty straightforward, there's still some questions regarding creating the best URL routing scheme for this feature. Ideally, a performance URL would look something like http://brother.ly/performances/some-artist-at-brotherly-xxx, but this may be a bit too long even if it's human readable. Perhaps we could use http://brother.ly/episodes/one/performances/some-artist as an alternative.
From a SEO perspective, it seems a better choice to have a URL with less "tiers". Performance pages are likely going to be hit the most, given they're the easiest things to share, so we want to make sure that we're deploying a feature that is optimized both for direct Web searches and sharing over social media networks like Twitter and Facebook.
The text was updated successfully, but these errors were encountered: