hypothetical roster generator #9
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOT FOR MERGE
Here we show how a server might generate a wide variety of rosters based on parameters it finds in a slug. This requires some ingenuity as the slug is of limited character set but not limited in length.
We will create a large number of rosters where each appears to be on its own page but will instead be generated on demand from search results. We imagine creating a page with a title
Roster chorus-of-voiceswhich is to contain one item, a roster of sites that have the page, Chorus of Voices.The same technique could be used to query any other database of sites for particular subsets based on parameters encoded into the title/slug.