Zhenke Wu's Research Website: click to view
-
[2025/06/11]
- Search bar font can be changed in
_includes/search-form-global.htmlor_includes/search-form.html - Font in the top and bottom navbars are controlled in
assets/themes/lab/css/style.scss. Check:the last body{}. Currently it isRoboto. This is not a clean solution. - Font in all other places follows the order specified in
$font-stack: jinkaiFont, "museo-sans", Optima, sans-serif;in the fileassets/themes/lab/css/style.scss - The fonts are stored in the folder:
assets/themes/lab/fonts. The fileassets/themes/lab/styles/font.cssrefers to these files. This structure andjinkaiFontfollows manateelazycat.github.io .
- Search bar font can be changed in
-
[2025/05/28] Added IpMeta and Google Tag Manager.
-
[2024/10/26] Added paper by topic; it uses
pages_list_paperandtags_list_paperinJBfolder. They will look fortagsin papers.- when specifying tags, please use lower cases; it is painful to implement sorting in a case insensitive way (if you know, let me know!)
- once you click
Topicin thepaperstab, you should be able to see the keywords with counts at the top and the list of papers by the keywords below.
-
[2023/12/16] Added search function; a useful reference is here and here. Need to do the following:
- Put the the javascript file at
./js/search-scripts.js, which is based on theSimpleJekyllSearchwhich specifies options for doing additional operations on the search results, e.g., sorting. - Put the javascript file at
./js/search-result.jswhich defines asimple_search()function that calls theSimpleJekyllSearch()function above, with additional specifications of how the search inputs and outputs would be. The inputs and results will be processed bysearch-form-global.htmlorsearch-form.htmlbelow to be included into a page to render search bar and display search results - Put
search-form-global.htmlinto the_includefolder and put the following into where you'd like your search bar to be<div> {% include search-form-global.html %} </div>- The above is to search globally (based on
search-global.jsonwhich pulls data from posts in all of the website and produce an actual.jsonfile with the same name in the generated static site folder named_site); if you want to only search for a subset of posts, e.g., papers, you can modify the json file into what you want, e.g.,search.jsonin the main directory is a separate json file to pull data on posts in the papers category only. Please feel free to modify the Liquid commands or include additional info to be pulled. To include search bar only for the subset of posts, ew need to use a include a different html statement to insert the search bar where you'd like to be. For example, I included only the paper search bar on the paper pages:<div> {% include search-form-global.html %} </div>
- The optional settings: currently I use sorting function argument
sortMiddlewareinsearch-form.htmlandsearch-form-global.html, where the former is for papers only (order by year), the latter is for the entire website (order by category and year). You will need to specify thesort_currfunction to define your desired sorting mechanism inJavascript.
- Put the the javascript file at
-
After cloning the repo to your local folder, you'll need to install jekyll to build and test your modified site.
-
fonts
- Use Typekit to publish fonts you like; register an Adobe account;
- Modify
$font-stackin/assets/themes/lab/css/style.scssto include your fonts. Extra font names are used as fallbacks.
-
posts
- To add a post, e.g., a new paper, follow the format of the existing
.mdfiles - Comment out
</div>if there are a multiple of three papers in each subsection; otherwise, there will be errors of indentation.
- To add a post, e.g., a new paper, follow the format of the existing
-
tracking
- To link your site to Google analytic services (Google Analytics 4), modify the
tracking_idin_config.ymlfile in the root directory so that it points to your website. - Replace the
tracking_idwith your own id in the following block of codes in_config.yml
analytics : provider : google google : tracking_id : G-XXXXXXX - To link your site to Google analytic services (Google Analytics 4), modify the
-
twitter feed:
- Follow the instructions here and here. The basic idea is to locally use the following to embed a tweet.
<div class='jekyll-twitter-plugin' align="center"> {% twitter https://twitter.com/anaik96 maxwidth=500 limit=5 %} </div>Run
bundle exec jekyll serverto generate a subfolder_site/and then find the generated.htmlfile that contains the code block for embedding your tweet. Copy the code block such as<blockquote class="twitter-tweet" data-width="500"><p lang="en" dir="ltr">For our first ever <a href="https://twitter.com/hashtag/StudentSpotlight?src=hash&ref_src=twsrc%5Etfw">#StudentSpotlight</a>, we're excited to feature Tim NeCamp who graduated in May and is an official <a href="https://twitter.com/hashtag/alum?src=hash&ref_src=twsrc%5Etfw">#alum</a>! Tim’s interests lie in the areas of experimental design, causal inference, intensive longitudinal data, and....<br>Read More: <a href="https://t.co/NYfWov7wDk">https://t.co/NYfWov7wDk</a> <a href="https://t.co/S6D3sM2vo7">pic.twitter.com/S6D3sM2vo7</a></p>— Statistics (@UMichStatistics) <a href="https://twitter.com/UMichStatistics/status/1144334755506401283?ref_src=twsrc%5Etfw">June 27, 2019</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
and replace the above
divblock. -
MathJax (also see here )
- To properly display the math expressions rendered by MathJax,
- Add
kramdownafter on the line ofmarkdown:in_config.yml; this prevents markdown language to intervene with LaTex commands; Also putgem 'kramdown'inGemfile;
- Add
- Add the following code block to /_includes/themes/lab/default.html, before
</head>
- To properly display the math expressions rendered by MathJax,
<!-- Math via MathJax -->
<script type="text/x-mathjax-config">
MathJax.Hub.Config({
extensions: ["tex2jax.js"],
jax: ["input/TeX", "output/HTML-CSS"],
tex2jax: {
inlineMath: [ ['$','$'], ["\\(","\\)"] ],
displayMath: [ ['$$','$$'], ["\\[","\\]"] ],
processEscapes: true
},
"HTML-CSS": { availableFonts: ["TeX"] }
});
</script>
<script src="https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML" type="text/javascript"></script>
- projects
- Research projects (federal, non-profit, philanthropy, and other sponsors) live in
projects/_posts/. Each project is one markdown post withlayout: project. Copy the front matter from an existing file in that folder. Fields:title,description,funder,funder_type(federal/non-profit/philanthropy/other),status(activeorcompleted). Optional:short_title,image(icon inassets/images/projects/),icon(Font Awesome class if there is no image),role,pi,years,grant_number,grant_url,website,collaborators,related. The Projects tab groups posts byfunder_typeand shows each project's icon and description. - The PCORI RL project page (
/projects/pcori-rl) is also a resource hub. Publications come from existing paper posts: addprojects: [pcori-rl]to a paper inpapers/_posts/(the same post can list multiple projects). For presentations, workshops, conferences, and advisory materials, createpcori-rl/_posts/YYYY-MM-DD-slug.mdwithlayout: project-resource,hub: pcori-rl, andtypeone ofpresentation,workshop,conference,advisory. Copypcori-rl/_posts/1970-01-01-_template.md. Files go inassets/pdfs/projects/pcori-rl/. - Legacy GitHub-software project pages: for each repo in
/_data/projects.yml, theurlshould not end with/. For example, useurl: /projects/baker, instead ofurl: /projects/baker/
- Research projects (federal, non-profit, philanthropy, and other sponsors) live in
- navigation:
- For example, the "papers" tab is specified in the folder "papers/". At the top,
titleis for tab name;groupcan be eithernavigationorsubnavigationdepending on whether you want to show this tab or collapse into the "More" tab;navorderspecifies the order appearing in the navigation bar (1 for the first tab).
- For example, the "papers" tab is specified in the folder "papers/". At the top,
- team
- Member pages live in
team/_posts/YYYY-MM-DD-name.mdwithlayout: member. Copy an existing post and delete unused keys. Omit empty fields. - For photos, set roughly 200px wide and 300px height, with resolution 144. The width requirement is to help display the photo properly on an individual's page.
- Fields (keep this small set):
- Always:
title,role,field,position,institution. roleis the listing bucket:PhD,MS,Undergrad,Research Staff, orPrincipal Investigator.fieldis the current field (biostat,stat, …).positionis the caption under the photo (e.g.PhD Student (Stat)).institutionis usuallyUMich(the profile page expands this to University of Michigan).endyear: year they left the lab. Omit if they are current. Current vs alumni is inferred from this (no separatealumflag).- Prior stages in this lab (omit if not applicable):
ms_year: they did MS here, then continued to PhD.ug_year: they were an undergrad here.ug_field: undergraduate field, only if it differs fromfield.paper: true: undergrad wrote a paper with the lab (adds*on the team page).
- After leaving:
placement(first destination). Addcurrent_placementonly if it later changed. - Optional links, only when present:
email,web,github,twitter,scholar,image,cv,thesis_title,thesis_url. handle: only if it differs fromtitle(used to match news/blogauthor_handle; otherwisetitleis used).
- Always:
- How the team page lists people (
team/index.md):- Current: no
endyear. Current undergrads also haverole: Undergrad; everyone else in Current is the photo grid. - Past / alumni: has
endyear. - Former PhD: has
endyearandrolecontainsPhD. - Former MS, terminal: has
endyearandrole: MS. - Former MS, continued in lab: has
ms_yearandrolecontainsPhD(they may still be current PhD students, or later alumni). - Former undergrad, left after undergrad: has
ug_yearandrole: Undergrad. - Former undergrad, continued in lab: has
ug_yearandroleis notUndergrad(e.g. nowPhDorMS). The former-undergrad list showsug_field(falling back tofield) so a later field change does not overwrite the undergrad record. - Former staff: has
endyearandrole: Research Staff.
- Current: no
- Typical edits:
- Current PhD/MS:
role,field,position; noendyear. - Undergrad who leaves: keep
role: Undergrad, setendyear,ug_year,placement, andpaper: trueif they wrote a paper. - Undergrad who stays (e.g. Jianhan): change
role/field/positionto the new stage, keepug_year(andug_fieldif the field changed), omitendyearuntil they leave the lab. - MS who continues to PhD: change
roletoPhD, setms_year, omitendyearuntil they leave.
- Current PhD/MS:
- Member papers on a profile are matched by author first and last name tokens (so
A Bdoes not matchAC B). Emails are printed exactly as in theemailfield (use[arroba]/[punto]if you want obfuscation).
- Member pages live in
categories- refers to the subfolders in the main directory without an underscore
_; - is used to refer to specific locations in the website (my current guess is that the definition of
categoriesships with the engine of jekyll, so no need to user-define categories)
- refers to the subfolders in the main directory without an underscore
- style sheets
- There are two that matter:
/assets/themes/lab/css/style.scssand/assets/themes/css/style.scss; The former works for posts, the latter for pages PRIOR to entering posts. - This might best be fixed, but I don't have time now to check how they are currently used in different pages.
- There are two that matter:
- team page
- Currently the landing page of the Team is four-column circular headshots (without stacking if the screen is wider than 576px). The circular image is achieved via
border-radius: 50%- one may remove this to return to rectangular. - Please check here and here for making changes regarding the landing page of Team based on the Bootstrap grid system.
- Currently the landing page of the Team is four-column circular headshots (without stacking if the screen is wider than 576px). The circular image is achieved via