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

Post Launch #5

Closed
wants to merge 9 commits into from
Closed

Post Launch #5

wants to merge 9 commits into from

Conversation

almereyda
Copy link
Collaborator

This PR adds

transformap_keikreutler_github com_fundus_jrichter_home_-_2015-05-02_02 18 55

Please note local master is transformap/master and not transformap.github.io/master.

  • Prose.io customizations evaluated

almereyda added 2 commits May 2, 2015 01:39
Conflicts:
src/layouts/default.html.eco
@almereyda almereyda changed the title Deployment settings Post Launch May 1, 2015
@almereyda
Copy link
Collaborator Author

Please defer for now.

Repository owner locked and limited conversation to collaborators May 2, 2015
@almereyda
Copy link
Collaborator Author

We're very happy with the current Prose integration, as it already navigates editors to the editing place of the texts on the site. About _prose.yml

For the next iteration of the editing workflow there are several possible directions to explore:

  1. Running DocPad as a Node webservice and integrating it into a GitHub Post Receive Hook pipeline which allows for automatic regeneration and deployment to the live site after Prose edits.
  2. Giving editors the ability to change chosen parts of site and page structures by finding ways to abstract the partials and render contents. Currently opening Prose will lead to editing the partials, where a wiki approach would more think of the pages in `
  3. Reverting 8a83052 from above to be able to deploy to gh-pages also from these personal forks, thus rethinking the git development and publishing model around an always deployable source branch on https://github.com/TransforMap/transformap.github.io with @thoka and @species to not be pushing to TransforMap/source anymore, but working and deploying from local forks/branches (which are in sync with master) as before. Then we can correctly issue PRs for new features to be peer reviewed.

Issues raised reviewing this PR:

Before doing any of the above, I will first tackle #1 to finally move issue related workflows over to https://waffle.io/TransforMap/transformap.github.io .

Repository owner unlocked this conversation May 3, 2015
@almereyda
Copy link
Collaborator Author

Well, you can always pull yourself and also push to the branch.

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

Successfully merging this pull request may close these issues.

2 participants