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

Documentation #20

Open
1 of 3 tasks
bbengfort opened this issue Aug 26, 2016 · 8 comments
Open
1 of 3 tasks

Documentation #20

bbengfort opened this issue Aug 26, 2016 · 8 comments

Comments

@bbengfort
Copy link
Member

bbengfort commented Aug 26, 2016

@samgoodgame has started the process of documenting our work. As a result of his pull request, I've given him access as a contributor to the repository. Thanks @samgoodgame!

We still have a couple of steps on this issue:

  • Finish up the user guide
  • Do a walk through of the admin site
  • Post the documentation to ReadTheDocs.org
@bbengfort
Copy link
Member Author

@samgoodgame please assign yourself to this issue when you accept the team invite!

@samgoodgame
Copy link
Contributor

samgoodgame commented Aug 26, 2016

@bbengfort it appears as though as a team member, I only have read access; unless there's another way to assign the issue to myself, it appears as though I am unable. Screenshot:

screen shot 2016-08-26 at 11 21 15 am

(There's no checkbox that I can use to assign)

@bbengfort
Copy link
Member Author

@samgoodgame strange - I'll look into it, but I've added you.

@bbengfort
Copy link
Member Author

@samgoodgame ok, you should now have write access.

@samgoodgame
Copy link
Contributor

samgoodgame commented Aug 26, 2016

@bbengfort Awesome, I assigned it to myself. Thanks!

@samgoodgame
Copy link
Contributor

@bbengfort should I point the readthedocs site at our development or master branch? Master currently doesn't have much on it, but I'm not sure if you want to hold off posting develop until we release it/merge with master

@bbengfort
Copy link
Member Author

I'd say post it to develop for now, and we can start having different
releases of documentation with the next push to production.

On Fri, Aug 26, 2016 at 1:31 PM, Sam Goodgame notifications@github.com
wrote:

@bbengfort https://github.com/bbengfort should I point the readthedocs
site at our development or master branch? Master currently doesn't have
much on it, but I'm not sure if you want to hold off posting develop until
we release it/merge with master


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#20 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAth7ikNYEDR8HyNQbjDv3P5CN1ZV-8lks5qjyLvgaJpZM4JtrVe
.

@samgoodgame
Copy link
Contributor

samgoodgame commented Aug 26, 2016

Ok-- it's currently visible at this URL:

http://partisan-discourse.readthedocs.io/en/develop/

The regular URL (http://partisan-discourse.readthedocs.io/) just links to the placeholder that we have in the master branch (that says "this is the future home of the PD documentation")

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

2 participants