railcore / railcore.github.io Goto Github PK

We should remake the wiring diagrams as png files so that they can be shown in-browser and embedded in a page. I think we should probably make new diagrams rather than just converting the PDF so we can retain higher resolution of the upstream Duet images.

http://railcore.github.io/build_and_troubleshoot/RailCore_wiring_diagram_with_12v_enablement-v2.pdf

There's now more than one page that describes proper belt tensioning, and not all are giving the same recommendation (as better apps/techniques have been found).

We should create a single page on belt tensioning and link the other pages to it so that we have our story straight site-wide.

Migrating railcore.org from a wiki-backed site to GitGub has been discussed on Facebook and IRC. This post seeks to develop a plan to actually get that done.

I believe there is consensus to convert the site to use GitHub Pages rather than a wiki, for various reasons. Primarily, to stop vandalism, but also to centralize all Railcore data and contributions in one place/platform/workflow.

Steps to move forward:

• 1. Rename this repo as railcore.github.io Github will then host the gh_pages branch at http://railcore.github.io

• 2. Add Jekyll configuration to the repo Github pages uses Jekyll to generate pages. We'll need to add that configuration to the repo and configure it for development/contribution.

• 3. Pick a Jekyll Theme for the site I suggest we settle on one of the supported themes just in the name of simplicity and ease of getting going.

• 4. Update existing content for jekyll We will probably want to reformat and reorganize the existing content somewhat to work better with GitHub Pages

• 5. Import wiki content from railcore.org There appears to only be about 30 pages of actual content on the wiki, so we can probably just move it by hand and clean up the formatting as volunteer effort allows.''

• 6. Setup railcore.org as a custom domain with GitHub pages Once railcore.github.io is working as desired, we can setup both GitHub pages and DNS for railcore.org to point to the new page

• 7. Establish contributing guidelines for the site Once we are over the hump with this, we should establish guidelines for how to organize pages on the site. In particular, how/where to post user-specific content such as mods or build logs.

With the proliferation of various extruder, aluminum parts, and hotend combinations, it's gotten to where it's fairly complicated for new users to collect all the correct parts for their build and successfully assembly.

We could create pages with documentation on individual setups, and then add an index page listing them. Each such setup needs to include specific, reproducible descriptions of aluminum parts and direct links to specific stl files for printable parts. Just linking someone to a thingiverse page with 15 files (of which they need 2) won't be enough to prevent further questions/mistakes/frustrations.

Done well, this should make supporting new users a lot easier than what is involved now.

From a discussion in #railcore where I mentioned keeping track of who has what Railcore (or not) in the channel, it was pointed out by JohnOCFII that Prusa MK2 Users 3030 Haribo Edition keep a public registry on Github.

I'm thinking it might be nice to do something similar?