-
Notifications
You must be signed in to change notification settings - Fork 27
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
Convert the ActivateHub.org wordpress site to Jekyll #34
Comments
Hi Daniel, it's good to see you making so much progress with the project, I set up a blog using Jekyll ( http://edrex.github.io/ ) and have a really ps check out my article http://edrex.github.io/2013/07/16/jekyll-pages-prose/ |
You should show me your workflow when you get back (I'm out of time for a little while). Whatever the solution is, it has to be easy for Lindsay to fork the project in GitHub and make basic text changes or create a blog post via a template. It should also be possible for anyone else to work on a fork of the repo without requiring permission or special access in advance. I should've mentioned that there is a time deadline for this ticket, which is about the 12th or 13th. We really need things cleaned up before we leave to do the Detroit and San Francisco launches. |
Eric! You're in Northern Idaho right now? Me too, until about 5am tomorrow I'd love to see your workflow as well (I've also tried Prose and I'm a fan Thanks, |
I have a todo item to bundle up the workflow stuff I've set up for my own site into a starter repo for Jekyll + Prose sites on Github, and this is sufficient impetus to put it at the top. The template will be ready to go with:
@dhedlund to answer your questions about the workflow, Prose can edit files in any repo/branch one has access to after an initial OAuth exchange with Github. It is essentially a markdown/Jekyll focused replacement for the builtin Github editor, and can be used alongside it. Check out the article linked above for more about that. @techieshark I am near Sandpoint, you? |
Ok, this morning I took some time getting this to a point where Lindsay can start porting content.
Kick the tires and let me know if you run into any issues! |
Also, once this is live we can have a staging copy where we make changes and then use a pull request to launch them. |
One other thing: the starter site is missing some features still for a "1.0" release (tags/categories and default post metadata, mainly), which I'll be adding shortly. At that point I'll rebase the activate site on the new upstream and force push, which will require anyone with a checked out copy to do fancy Git stuff to get back in sync. |
Nice! Looks like we're ready for content and design. Eric, how much of that are you planning on working on? If you wants an example of another pre-existing site ported to Jekyll, here's one:
(Eric, I was in Cour d'Alene, but just for the weekend. Hope you had a good trip!) |
Is the idea just to do a straight-across port of the existing Wordpress * On Wed, Aug 7, 2013 at 5:04 PM, Peter W notifications@github.com wrote:
|
Use your best judgement as far as what content gets copied across and how "If we replaced the wordpress site with this right now, does this feel as Thanks!
|
Yes, mostly.... Certainly like the general look & feel of existing site,
#2 is exciting and interesting. I would love to see a mock-up wireframe on Lindsay Caron Epstein On Wed, Aug 7, 2013 at 9:37 PM, Eric Drechsel notifications@github.comwrote:
|
By which I mean, yes? Just migrate existing look + feel + content! |
Nobody is currently maintaining the wordpress site and it needs a makeover pretty badly. A decision was made to try migrating the content of the wordpress site over to Jekyll and host it in another git repository as part of GitHub Pages. This will make it easier for anyone in the community to help maintain the site, while also maintaining a peer review process.
The goal of this ticket is to take the essence of the wordpress site and re-architect it in whatever way makes sense to the person who decides to tackle the ticket (merging the general and development blogs together, etc). Once most of the content is in Jekyll and its own repository, we can decide where and how to improve on it from there with GitHub tickets attached to that project.
References to get you started:
The text was updated successfully, but these errors were encountered: