Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the README #44

Open
matthewdking opened this issue Nov 4, 2017 · 9 comments
Open

Fix the README #44

matthewdking opened this issue Nov 4, 2017 · 9 comments

Comments

@matthewdking
Copy link
Member

As part of improving the repo it has been raised that the README is in dire need of improvement. Maybe we should comment here on the things that need to be added to the README.

@shiryz
Copy link
Member

shiryz commented Nov 5, 2017

I would edit the description, add a photo of one of the meals and delete the the links as they are now, add them in the description as links, ("You'd find meals in the recipes folder ranging from mains, breakfast, dessert etc"), it wouldn't be as readable when we have more recipes.

@m4v15
Copy link
Contributor

m4v15 commented Nov 5, 2017

Hmmm while I agree with you to an extent @shiryz I would say I quite like the layout as it is, a kind of contents page, and is better and easier to use effectively as a user coming across the repo. Maybe there will be an issue with scalability in the future but I think anything under 30 recipes will still be very readable and I think provides a better UX than having to click through to find a list of recipes.

@finnhodgkin
Copy link
Contributor

I think a combination of the two could be nice 👍.

A simple contents section with links to all the recipes and a bunch of photos plus some general information about the aims of Nazareth Recipes.

@matthewdking
Copy link
Member Author

Links to the contributing guide and vision statement (#47) when it is created should also be included

@mattlub
Copy link
Contributor

mattlub commented Nov 6, 2017

My vote would be to keep it simple, just a brief introduction and then the recipes.

My key principles:

  • a welcoming, succinct, collaboration-encouraging intro
  • recipes are easily and immediately accessible

If others wanted a longer/more in depth intro section, I would campaign for a contents section so the actual recipes can still be found immediately.

@m4v15
Copy link
Contributor

m4v15 commented Nov 6, 2017

img_1199
img_0763

These are the only photo's I have

@shiryz
Copy link
Member

shiryz commented Nov 6, 2017

@m4v15 @mattlub @matthewdking @finnhodgkin @Karyum , hope I didn't miss any of you.
I have an idea for the menu on the readme (inspired by Finn):
Have only the latest meal of each and the folders can be links as well, so if the last breakfast merged was omelette then we'll only have omelette in the breakfast section.
that way it looks like menu of the day and we wouldn't have too many recipes in there.
Every pr should also update the readme with the link to the meal

@Karyum
Copy link
Contributor

Karyum commented Nov 6, 2017

@m4v15 what the hell is that photo mate 😆 don't put that on the README

@m4v15 m4v15 added the Creamy label Nov 11, 2017
@Karyum
Copy link
Contributor

Karyum commented Jan 5, 2018

Creamy README 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants