-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Possible README installation instruction #8175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer option 3 - more verbose but also super clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also think option 3 seems best
- add contributing workflow link already - i would suggest we merge this PR if the workflow guide was reviewed
How come this is still WIP? Would like to merge 😁 |
I played with the markdown formatting a bit, because i couldn't use colours in github markdown. I will update later and then we can merge. |
Pushed some final updates. I have removed the information about the fork url. I think people should follow our git workflow and add their fork as remote stream. The git workflow is also linked in our working with ghost wiki. Tell me if you feel different. |
The installation steps in the README are not optimal right now.
I went over them and found some variants.
^ very short,
npm run init
wraps all necessary commands to install Ghost.^ we show people that they have to run
knex-migrator init
^ we describe all commands
No matter which variant we take, i would like to create a wiki page to have some more detailed descriptions for installation, workflow, testing (e.g. how can a user reset it's database, how can a use run a single test etc). So the README could link to a wiki page with a full guide.
One thing to note
To be able to run
grunt init
, we have to install the Ghost dependencies.This was tested with a fresh clone and zero global or local npm packages.