Designing the Site?

Solution: Bootstrap

• Turns out theming is easy
• Easy to clone any existing site
• Use Bootstrap for framework

Conditional filtering?

Solution: Liquid

{% if site.audience="administrators" %}
show this to administrators
{% elsif site.audience="analysts" %}
show this to analysts
{% endif %}

Multiple outputs?

Solution: Multiple config files

• Separate config files for each variant
• Each config file has various properties
  (audience, platform, product, version)
• Create scripts that compile build commands

Environment workflows

Solution: Relative URLs

• No permalinks
• All markdown files stored in root directory
• No need to configure url or baseurl properties

Multi-level navigation menu?

Solution: YAML + Navgoco

• Store menu items in YAML file
• "for" loop in HTML layout parses through YAML
• Navgoco component handles other aspects (expand/collapse, cookie, accordion)

Alerts: Notes, tips, cautions?

Solution: Includes with Parameters

• Store note code as include
• Pass parameters with include code

// create the note.html include:

Note: {{include.content}}

//use it like this:

{% include note.html content="My note content goes here ..." %}

Avoiding broken links?

Solution: YAML-based links

• Iterate through TOC to create YAML file to get link names
• Store urls.yml in _data folder
• Reference links like this: {{site.data.urls.myfile.link}}

PDF output?

Solution: Prince XML

• Iterate through sidebar menu to get list of links
• Feed the list of links to Prince XML
• Store command in shell script

Re-use across projects?

Solution: Single project for writers

• All writers work in same project
• Each project stored in its own subfolder
• Still use relative links (redirect index.html in root to project home)
• Put common content in non-excluded directory
• Exclude other directories in each project's config file

Version control workflows?

Solution: Learn the needed workflow

• Focus only on necessary Git commands
• Coordinate more among team members
• Avoid simultaneously editing the same page
• Look regularly at commit logs

Simplicity?

Solution: Stick with Core Jekyll

• Avoid plugins or overly complicated code
• Have all writers work in same project
• Stop changing processes/code each month
• Establish standards and provide training

Search?

Solution: Swiftype or Algolia

• Implementation requires UX skills
• More difficult if content isn't public
• Never got around to implementing

Translation?

Solution: Separate projects

• Separate out UI strings into data file
• Send out Markdown files for translation
• Create new project with translated files

Authentication?

Solution: Involve Engineering

• Recognize that IAM is an entire discipline
• Simple implementations like onelogin.com aren't cheap
• Push back on impossible requirements
• Dynamically pull from AWS S3
• Last resort: Salesforce site.com solution