Changing the Base of the gh-pages site. #893
Comments
missyschoenbaum
added this to the V3.3.1 Vaccination Priorities and Variable Rings milestone
|
Will we be rearranging all those items that are currently in the gh-page branch? If so, I can start on changing the links I think we will need this eventually, but let's keep the priority behind the bug fixes. Bottom line, yes, we will need this at some point in the future. |
missyschoenbaum
modified the milestones:
V3.3.1 Vaccination Priorities and Variable Rings,
Maintenance FY 2019
Changing the github pages base from markdown to html. This includes two new folders, a _site_assets folder for developer editing, and a _site folder for the compiled site. Jekyll will build the _site folder - so don't edit anything in there. _config.yml was edited to support these changes.
After the previous commit it became apparent that the site was still trying to use the old index.html and about.md. This edit to the _config.yml file should exclude those original files from the site build.
Exclusion did not work, removing from _config.yml. Going to rename the old files in an attempt to remove them from the scope of Jekyll, this should force the site to use the _site files.
The github version of the site is not getting the html code from the same source as my local version of the site. These Gemfiles should fix that issue.
|
If you need something to post, here's the one page publicity flyer. |
These files should be generated by Jekyll when the server compiles, but looking in the gh-pages repo, it doesnt seem they are being generated. Adding them manually may point Jekyll in the right direction when it goes to make the site live.
It seems the online version of the site is using index.html as the base page instead of _site/index.html. This commit changes the root index.html to redirect to _site/index.html. This will remove all formatting that might have been saved from the original gh-pages setup, but will allow it to be far more customizable in the future.
|
Looks like the live version is actually using about.md as the base page, interesting! I'm now looking into a way to either redirect a markdown file to html or get the live version of the site to use index.html as the base page instead. |
I believe that jekyll is trying to use the _site files despite the fact that the live site cannot find those files (404). Hopefully by removing these config lines it will just use the root index.html
Removing all files from failed attempts, this will keep the branch nice and clean so future developers don't get confused with what is going on when debugging.
|
That got it! Time to spend a bit of time formatting the website so it actually has content. |
No new content added (imported old content from about.md), just some simple formatting. More formatting to come in the near future.
Added PDF databank, no PDF links currently added. All style changes conform to rules set in fontandcolorguide.pdf currently located in the gh-pages branch.
Added more information to the left column. Also added more intelligent formatting so future changes to the two-column design will be less difficult.
|
This is ready for any content to be added. @missyschoenbaum I'm going to leave you with this thread and add it to testing. I think if we leave it in development as long as we think there will be more content to add it will be in the development pipeline forever. I've sent you an email asking about what pdf files you want to add right away. |
|
I posted the one page overview earlier in this issue. The text is about the same as the text that is posted, but it would let us try posting something. |
|
First note - PDF databank wording becomes Reference Databank. Addtional Databanks for training and other languages can be added. |
|
I have "Basicsofstochaticmodeling.pdf" ready to go up into the reference material. It is slightly different than the wiki, but close enough. |
|
@missyschoenbaum Can you upload that "Basicsofstochaticmodeling.pdf" to the gh-pages fork? I see a "Basicsofstochaticmodeling.docx" but I'm not sure if that's the most updated version of the file or I would just convert it myself. |
|
Did I put this in the wrong place? |
|
Nope, that's exactly where it should be. I've already got it linked into the Reference Databank. |
|
@missyschoenbaum What else do you have for this ticket? General document requests probably don't belong in this thread. |
|
Want to teach me where to add more? I just got another one cleaned up and moved up. |
|
I've added in-file help text to make adding new files very easy. Simply open up the gh-pages branch and edit "pdf_bank.html" to find the help text. |
|
@ConradSelig I made an attempt, but it doesn't seem to be working. There are 2 parts of this: Good thing I am not writing html for a living. |
|
Update - NAADSM training part is working. Training part is not. |
|
I'll take a look at this tomorrow morning. I'm sure we can get it working |
|
@ConradSelig no rush, I didn't crater it |
Fixed a syntax error in naadsm_training.html and added ADSM Overview training block.
|
@missyschoenbaum That should fix it. Let me know if it doesn't look like what you want it to. |
|
@ConradSelig Perfect! Should we move this ticket to testing? |
|
I would say yes. Even if you have more training material to add it should be fairly cut and dry from here on out. |
After spending some time figuring out how the gh-page works, I made a few discoveries about why editing it has been so difficult - and why future edits at the site's current state would continue to be difficult.
First off, the content on the site is compiled from a .md (mark-down) file. Formatting mark-down to get it to look just right is complicated, and styling it to look like the app would be impossible as .css classes cannot be applied.
There is good news however, I have found a way to transfer the content to .html pages instead of .md pages. This means we can apply css, add images, include links, and much more - just like we do in the app.
Only problem here is that the structure of the site needs several big changes, so instead of just going ahead and making them, I'm looking for input and approval. If the change is made, the GitHub page would continue forward just like an .html page would.
Also a note to developers looking to make changes to the site, a local version can be run using Jekyll from Ruby. Here is the link I used to get it working for me: http://kbroman.org/simple_site/pages/local_test.html
The text was updated successfully, but these errors were encountered: