Convert CKAN.org to jekyll and github pages
- Dominant language
- No language data
- Stars
- 39
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Why?
- Easier ability to integrate structured info (e.g. instances, extension registry, members) into one single site (cf what we do on http://okfnlabs.org)
- Easier to manage contribution and support new contribution (anyone can submit a pull request)
- Cleaner setup and static file output means faster, leaner site
- Minor (in RP's opinion)
Why not?
- Its a change so investment of effort required
- Harder for non-"geeks" to contribute to jekyll-based websites (though improving with things like prose)
@rgrp view: overall this looks like a good thing. What do others think? Who else could help make this happen?
/cc @rossjones @wardi @amercader ...
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the current CKAN.org setup and the proposed Jekyll/GitHub Pages approach, then clarify the migration scope and contribution workflow. Done means CKAN.org runs on Jekyll and GitHub Pages with the structured information and contribution goals described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, jekyll
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100