dansinker / tacofancy

community-driven taco repo. stars stars stars.

tacofancy

This is a community-driven, object-oriented taco recipe repo. Please fork and submit your own recipes, because the more there are, the more delicious it gets.

This repository contains a few different directories:

• full tacos
  • This contains full descriptions of tacos. Those tacos may contain additional elements from other directories.
• base layers
  • This is where you'll find meats, beans, tofu, and other things that make up the 'base' of your taco goodness.
• mixins
  • The base is important, but what you add to it is what makes the taco glow.
• condiments
  • Do you make a motherfucking salsa? Do you know how to pickle your own jalapeños? Yeah, put it here.
• seasonings
  • Hot and spicy? Rubs and mixes? It's all in here.
• shells
  • Your base layers and mixins and condiments have to go into something, right? Put your tortilla recipes here.
• like_tacos
  • A collection of things that are like tacos, either in shape or flavor, but actually aren't.

Full Index

Want to see all the recipes in Tacofancy? Hit the full index. WARNING: IT IS CRAZY DELICIOUS.

Full Index

Notes on Writing & Naming Conventions

We want YOU, yes, YOU, to submit your amazing recipes to Tacofancy, so we've made it super easy to fork, create, and submit pull requests with your additions to the repo. But PLEASE read the Writing For Tacofancy document for a full (but quick) explanation on how to best write your recipes.

Writing for Tacofancy

Are You New to Github But Want to Contribute?

No better time than the present to learn Git! Thankfully, this repo is pretty simple. Github makes some amazing guides that are a great starting point. Specifically, I'd recommend you start with the Understanding the Github Workflow guide, which is an awesome top-level explanation of how all this works. From there, pretty much everything you'd want to know to contribute to Tacofancy is contained in Github's very handy Forking Projects guide section. Beyond that, their help section is crazy helpful.

Are you using Tacofancy to Teach Github?

That's awesome! Tacofancy is a great way to teach the basics of the Github workflow. But keep in mind that Tacofancy is also a working repo. Our recommended workflow for teaching from Tacofancy is to create your own fork, have your students fork from that so they are submitting pull requests to you, not us. From there, you can help them through the hard bits, make sure they're operating at maximum deliciousness, and then submit a pull request to this repo with their stuff.

Tacofancy-Inspired Projects

It's not just the tacos on Tacofancy that are open source, but the idea and the code too. There are some cool projects that are spinning off of Tacofancy, and it's worth collecting them here (if you're working on a tacofancy-inspired project, feel free to add it to this README)

• The Taco Randomizer need inspiration? the Taco Randomizer leverages Tacofancy to build a randomly created full taco (and can also supply it as JSON).

• Tacofancy API by @evz is a project to create an API from the objects on Tacofancy. The API drives the Taco Randomizer.

• @tacobot is a work-in-progress Twitter bot that tweets when a new file is added to the Tacofancy repo.

• the_great_taco_hunt is a repo dedicated to documenting great taco locations, inspired by Tacofancy.

Endnotes

This whole thing began on a cold November evening with the warmth of some steak, sweet potato, and apple tacos aglow in my belly. It started with just three recipes in it. Now it has well over a hundred. Nice job, world.

Oh hi, I'm @dansinker.

tacofancy's Issues

Brand Name Ingredients

Are brand name ingredients allowed within a recipe? Or is everything to be "from scratch"? An example would be a brand specific taco shell combined with other regular items to make a full taco.

New spicy sauce

Current is too little spicy

Add a service hook to automagically update taco randomizer

Github has this kinda nifty thing they do to make it simple to integrate your repos with other apps. In the settings for your repo (which can be accessed by clicking this thing

just to the right over there) you should see a menu on the left that includes an item called "Service Hooks":

Click that and it should take you to something that looks really impossibly complicated, like this:

The thing that you want is the top item, "Webhook URLs". If you add http://taco-randomizer.herokuapp.com/cook/ in there like so:

It'll make the randomizer get updated whenever the tacofancy repo gets updated. Now, there is a chance that it won't actually do anything when a pull request is merged (which would make the whole thing pretty silly since it seems like that's how the majority of changes are getting integrated) but we'll never know until we try.

Shirts

On twitter, @sinker said:
I've been thinking of "I FORK TACOS" as the Tacofancy t's.

Which spurred two ideas. First is a taco twin, like the Forktocat, the second would be the symbol font "Fork" sign instead of Fork. So I mashed up two things in photoshop to post here.

And as I type this, I realize that I Fork Tacos, as words, is way funnier and less nerdy and sounds better.

Vaya con dios.

(Note: the pixel art comes from the Iconfactory Copland set, and is not for commercial use. Would need to be redrawn.)

Potential confusion over "Drunken Green Beans"

Regarding "Drunken Green Beans" recipe-

I'm concerned that the presence of words "drunken" and "green" may lead believe casual taco consumers that there is some Irish connection to this one. The latter mention of "surly" and "half beer' (which begs the question; where did the other half go?) could cement the confusion.

The Irish people, as a nation (and culture), rarely endorsee one taco over another (but I don't rule out this possibility in the future...).

Not sure on best approach to a solution, if any, but definitely had to flag.

Include pictures

These recipes are fantastic but I'm left to my imagination on what the end result looks like most of the time... :(

I'm thinking it would be great if new taco submissions included a picture of the tacos in a standardized way (as to not interfere with the tacofancy-api app). Then work towards updating existing recipes with pictures (internet found or homemade). Thoughts?

CONTRIBUTING.md

Adding contribution guidelines in the root (“be sure to update the index along with your PR” for example) could reduce time spent doing triage.

let's talk taco twitter bots

So @meetar built the taco_fancy twitter bot to tweet whenever a new file has been added to the repo, so people can see when something delicious has been added. YAY. But, the user experience isn't super great, since it tweets the commit message, not the actual title of the taco object added.

I'm thinking that @knowtheory's work in automation might make this twitter bot's messages more human-readable, by being able to simply tweet the title of the recipe, which he's deriving to add to the index. That and then a link to the recipe (I believe currently it links to the PR), would be amazing.

THEN, what if we were to use @evz's API to do one better: What if someone could tweet @ the tacobot and get a random taco recipe in return?

TACO ALL THE TWITTERS.

Also, I've managed to get my hands on the tacobot twitter account, which will replace taco_fancy once the right levers have been pulled over at the Big Bird HQ.

UPDATE: tacobot is now the valid twitter account for this effort.

Does markdown require installation on a web server to contribute to tacofancy?

I am making an open source contribution for first time and installed Markdown. Markdown requires one of two web loggers, I decided to use Blosxom weblogging since the only other option is Movable Type, which requires a paid license. Here are the requirements for installing and using Blosxom: httplol://blosxom.sourceforge.net/documentation/users/install/dynamic/isp.html
I am pretty sure that I do not have any space allotted to me by my ISP for my own website where I can run CGI scripts, and I run windows 8 on my only machine, so I am sure the other options discussed here: httplol://blosxom.sourceforge.net/documentation/users/install/dynamic/ do not apply for me.

With this in mind, how can I contribute to this project without paying for additional software / hosting I don't normally use or need?

Arepas should be in the taco-like section

Just assign this to ryansholin

base_layers/morrocoan_lamb.md needs clarification

The Moroccan lamb filling recipe specifies "10g lemon peel." Are we talking:

1. full peels, pith and all;
2. lemon zest only (get out your microplane grater);
3. preserved lemons (definitely Moroccan but instructions required)?

Tags and other metadata in YAML front matter format

The recipes are in markdown. But they also have some metadata (e.g. tags). YAML front matter is a format used by Jekyll and other static site builders to add metadata to a Markdown file. It seems like a good fit for this project.

Add WebHook for twitter feed

IF
You go to https://github.com/sinker/tacofancy/settings/hooks and add http://96.126.108.104/tacofancy.cgi as a WebHook URL

THEN
Whenever you merge a pull request which includes an added file, the cgi will tweet the associated commit message and a link to the commit at http://twitter.com/taco_fancy . (This only works for this repo.)

BUT
Not sure how it will work in practice. Also not sure what happens when you add a file yourself, instead of merging a pull request.

ALSO
You have veto privileges on the twitter account's icon.

Migrating to Organization Repo

So, basically, shit got crazy- this project now has [as of this writing] 432 stars and 108 forks.

In order to keep up participation on open source taco related projects (ie, issue #94), we should probably consolidate all taco related repos into one organization.

@evz / @meetar.

need a few volunteers to keep the index up to date

We can certainly ask contributors to add their material to the index, but until that becomes commonplace, if there are a couple people who'd be willing to double-check that the index.md nicely created by @jessevondoom matches reality, even just once a day, that'd be awesome.

Any chance we can talk data standards?

I'm attempting a tacofancy API over here and quickly realized that all I can reliably grok from the rendered markdown of the recipe pages is the title of the recipe (since it ends up in an h1). I suppose this might be a great opportunity for me to hone my regex skills or I could just be satisfied with the name, URL and text of the recipe but wouldn't it be great to have a web service that you could query by ingredient, preparation time, etc?

Personally, all I want is a taco randomizer which probably doesn't need all that other stuff but if I'm going to put the effort into building this part, I may as well do it right. On the other hand, most of the beauty of this project lies in its simplicity so I'd hate to be the guy that ruins that (in its first week no less).

Missing "taco exoskeleton" directory

Need a home for the tortilla secrets!

ready to move the tacobot to full-time indexing status

Ted, the Tacobot is clearly doing a great job creating the table_of_contents file. Can you now deploy to writing to INDEX.md instead? Let me know and then I'll kill all various references to "update the index" requests.

Breakfast Tacos?

Breakfast Tacos

Is this a directory or a file? Who's gonna bring it?

Migas?

I used to eat a lot of tacos in Austin for breakfast and the best were always filled with "migas" which was a delicious and mysterious filling. Migas should really be included here.

remove "writing for tacofancy" from TOC

So the fancy new table of contents (soon to replace index.md) is fancy, new. However, it's listing the "writing for tacofancy" page as part of its index. Can we make the bot a little less overeager to index all the things??

Style guide

A comment in #40 got me thinking that the recipes could easily be more machine-readable:

[The automatic indexer] wouldn't be able to figure out which recipes are vegetarian unless noted somewhere in the recipe that the extractor could find [...]

Having a bit of structure in the recipe files would allow us to treat the recipes more like a database from which tools can draw. For example, an app could allow a user to say "I have ingredients x, y, and z" and it lists the recipes that can be made.

I wouldn't want to overcomplicate the process of writing recipes—after all, plain text makes it easy for anyone to contribute. Perhaps there can be a balance between ease of writing and parse-ability.

For example, each recipe could contain the following:

• A level-1 header containing the title
• A level-2 header called "Ingredients" followed by a list of ingredients
• A level-2 header "Notes" followed by a list: whether or not the recipe is vegan, prep time, cooking time, etc.

The author could add any other free-form sections they'd like.

Thoughts?

Needs Taquito policy

While they are both like and unlike tacos, Taquitos are necessary to address if this is to be a collaborative encyclopedia on tacos. As a community-created collaborative taco encyclopedia, I would like to advocate for Taquito inclusion.

Have you heard the story of the makloub ?

https://encrypted.google.com/search?q=makloub&hl=en&source=lnms&tbm=isch&sa=X&ei=kLZ1Uui4LaSp7Qa9xoCYDg&ved=0CAkQ_AUoAQ&biw=1366&bih=602&dpr=1#hl=en&q=makloub&tbm=isch