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

Create basic Pindah project website #46

Open
AtomicPair opened this issue Nov 20, 2013 · 2 comments
Open

Create basic Pindah project website #46

AtomicPair opened this issue Nov 20, 2013 · 2 comments

Comments

@AtomicPair
Copy link
Contributor

I think having a simple project website would help create awareness and (hopefully) increase widespread adoption for the project. We could use Jekyll (or a similar framework) to create a clean, static site and host the assets on GitHub Pages.

I have some site design ideas in my head, but I may not have time to realize them for several weeks. Does anyone want to contribute anything to this idea or tackle the project themselves? :-)

@baroquebobcat
Copy link
Member

I've used middleman for that a couple times and I think it works pretty
well. Do you want a separate repo or do the gh-pages branch thing?
On Nov 19, 2013 11:52 PM, "Adam Parrott" [email protected] wrote:

I think having a simple project website would help create awareness and
(hopefully) increase widespread adoption for the project. We could use
Jekyll (or a similar framework) to create a clean, static site and host the
assets on GitHub Pages.

I have some site design ideas in my head, but I may not have time to
realize them for several weeks. Does anyone want to contribute anything to
this idea or tackle the project themselves? :-)


Reply to this email directly or view it on GitHubhttps://github.com//issues/46
.

@AtomicPair
Copy link
Contributor Author

@baroquebobcat Good question. I don't have any personal experience with creating a new site for an existing project using the gh-pages branch method, so I welcome your thoughts on this. On the one hand, it might help to keep everything centralized under one project repo; on the other, maintainers would need to exercise care when checking out and committing changes to the branch so they don't affect master.

What do you think?

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