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

Generally improve the README #10

Open
getdave opened this issue Jan 4, 2013 · 3 comments
Open

Generally improve the README #10

getdave opened this issue Jan 4, 2013 · 3 comments
Assignees

Comments

@getdave
Copy link

getdave commented Jan 4, 2013

Reading this project I don't find the README file easy to follow.

Would it be possible for someone for the owner to run over this and write clearer documentation?

My scenario is that I'd like to setup so that I can deploy to dev/stage/production servers from my local MBP.

I have WP Skelton, I've installed Capistrano but the installation of Stack isn't clear for me.

Any update would be much appreciated.

Thanks for your hard work on this.

@ghost ghost assigned markjaquith Jan 4, 2013
@paynecodes
Copy link

Unfortunately, I must second this. I am not so sure that the docs are inadequate. I suppose it's my dispersed knowledge of full stack development. Git, Capistrano, CDN's, etc. are all familiar, but new concepts for me. That being said they are all things I am making room for in development, but I am having a difficult time getting WP Stack going w/ WP Skeleton.

@getdave
Copy link
Author

getdave commented Jan 23, 2013

I'm sure you are right. Docs are probably fine for someone familiar with this but when starting out I'd rather not have to go through a long trial and error process.

If I work this out then I'll submit a pull request but I doubt I'll have time...

@paynecodes
Copy link

Well, if you do or don't get the time, thank you for your time and response. I must say, I have still not successfully implemented WP-Stack, WP Skeleton, and Capistrano for my dev/stage/production workflow successfully. Primary reason for this is that I have just been playing around with the workflow. If this was something I needed for client work, I'm quite sure I would have already made it through more iterations of trial and error to make this work.

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

No branches or pull requests

3 participants