diff --git a/404.md b/404.md index 0fb82f8..a7b58c0 100644 --- a/404.md +++ b/404.md @@ -3,4 +3,4 @@ title: "Page Not Found" search: exclude --- -Sorry, but the page you were trying to view does not exist — perhaps you can try searching for it. +Sorry, but the page you were trying to view does not exist. Try searching for it or looking at the URL to see if it looks correct. diff --git a/_config.yml b/_config.yml index 66a26b7..5826729 100644 --- a/_config.yml +++ b/_config.yml @@ -1,39 +1,47 @@ -permalink: /:year/:month/:day/:title/ -# this sets the style for permalinks. The date formatting (/:year/:month/:day/) will only apply to blog posts, while the pages will just show the title. -url: http://idratherbewriting.com -# where you plan to publish your site -baseurl: "/documentation-theme-jekyll" -# any subdirectory that appears after the domain where you're publishing your site + +include: ['_pages'] +# this tag includes all pages from the pages directory and puts them into the root directory + output: web # this property is useful for conditional filtering of content that is separate from the PDF. + topnav_title: Jekyll Documentation Theme # this appears on the top navigation bar next to the home button -site_title: Jekyll theme for designers + +site_title: Jekyll theme for documentation # this appears in the html browser tab for the site title (seen mostly by search engines, not users) + company_name: Your company # this appears in the footer -github_editme_path: tomjohnson1492/documentation-theme-jekyll/blob/gh-pages + +github_editme_path: tomjohnson1492/documentation-theme-jekyll/blob/gh-pages/_pages/ # if you're using Github, provide the basepath to the branch you've created for reviews, following the sample here. if not, leave this value blank. + disqus_shortname: idrbwjekyll # if you're using disqus for comments, add the shortname here. if not, leave this value blank. + host: 127.0.0.1 # the preview server used. Leave as is. + port: 4005 -# the port where the preview is rendered. You can leave this as is unless you have other Jekyll builds using this same port that might cause conflicts. +# the port where the preview is rendered. You can leave this as is unless you have other Jekyll builds using this same port that might cause conflicts. in that case, use another port such as 4006. exclude: - - _site - - _drafts/ - .idea/ + - .gitignore # these are the files and directories that jekyll will exclude from the build feedback_email: tomjohnson1492@gmail.com # used as a contact email for the Feedback link in the top navigation bar -#feedback_disable: true -#feedback_text: "Need help?" -#feedback_link: "http://helpy.io/" -# change feedback link behaviour if you use a support ticketing system or something else +# feedback_disable: true +# if you uncomment the previous line, the Feedback link gets removed + +# feedback_text: "Need help?" +# if you uncomment the previous line, it changes the Feedback text + +# feedback_link: "http://helpy.io/" +# if you uncomment the previous line, it changes where the feedback link points to highlighter: rouge # library used for syntax highlighting @@ -49,7 +57,7 @@ kramdown: collections: tooltips: output: false -# collection declared here. this renders the content in _tooltips and processes it, but doesn't output it as actual files in the output. +# collections are declared here. this renders the content in _tooltips and processes it, but doesn't output it as actual files in the output unless you change output to true defaults: - @@ -79,10 +87,15 @@ defaults: layout: "post" comments: true search: true - sidebar: tags_sidebar + sidebar: home_sidebar # these are defaults used for the frontmatter for these file types +sidebars: +- home_sidebar +- mydoc_sidebar +- product1_sidebar +- product2_sidebar description: "Intended as a documentation theme based on Jekyll for technical writers documenting software and other technical products, this theme has all the elements you would need to handle multiple products with both multi-level sidebar navigation, tags, and other documentation features." # the description is used in the feed.xml file diff --git a/_data/mydoc_urls.yml b/_data/mydoc_urls.yml deleted file mode 100644 index a07ecfe..0000000 --- a/_data/mydoc_urls.yml +++ /dev/null @@ -1,589 +0,0 @@ - - - - - - - - - - - -mydoc_hompepage: - title: "Get started" - url: "/documentation-theme-jekyll/" - link: "Get started" - - - -mydoc_release_notes_50: - title: "5.0 Release notes" - url: "/documentation-theme-jekyll/mydoc_release_notes_50/" - link: "5.0 Release notes" - - - -mydoc_introduction: - title: "Introduction" - url: "/documentation-theme-jekyll/mydoc_introduction/" - link: "Introduction" - - - -mydoc_supported_features: - title: "Supported features" - url: "/documentation-theme-jekyll/mydoc_supported_features/" - link: "Supported features" - - - -mydoc_about: - title: "About the theme author" - url: "/documentation-theme-jekyll/mydoc_about/" - link: "About the theme author" - - - -mydoc_support: - title: "Support" - url: "/documentation-theme-jekyll/mydoc_support/" - link: "Support" - - - - - -mydoc_about_ruby_gems_etc: - title: "About Ruby, Gems, Bundler, etc." - url: "/documentation-theme-jekyll/mydoc_about_ruby_gems_etc/" - link: "About Ruby, Gems, Bundler, etc." - - - -mydoc_install_jekyll_on_mac: - title: "Install Jekyll on Mac" - url: "/documentation-theme-jekyll/mydoc_install_jekyll_on_mac/" - link: "Install Jekyll on Mac" - - - -mydoc_install_jekyll_on_windows: - title: "Install Jekyll on Windows" - url: "/documentation-theme-jekyll/mydoc_install_jekyll_on_windows/" - link: "Install Jekyll on Windows" - - - - - -mydoc_pages: - title: "Pages" - url: "/documentation-theme-jekyll/mydoc_pages/" - link: "Pages" - - - -mydoc_posts: - title: "Posts" - url: "/documentation-theme-jekyll/mydoc_posts/" - link: "Posts" - - - -mydoc_webstorm_text_editor: - title: "WebStorm Text Editor" - url: "/documentation-theme-jekyll/mydoc_webstorm_text_editor/" - link: "WebStorm Text Editor" - - - -mydoc_conditional_logic: - title: "Conditional logic" - url: "/documentation-theme-jekyll/mydoc_conditional_logic/" - link: "Conditional logic" - - - -mydoc_content_reuse: - title: "Content reuse" - url: "/documentation-theme-jekyll/mydoc_content_reuse/" - link: "Content reuse" - - - -mydoc_collections: - title: "Collections" - url: "/documentation-theme-jekyll/mydoc_collections/" - link: "Collections" - - - - - -mydoc_sidebar_navigation: - title: "Sidebar navigation" - url: "/documentation-theme-jekyll/mydoc_sidebar_navigation/" - link: "Sidebar navigation" - - - -mydoc_yaml_tutorial: - title: "YAML tutorial in the context of Jekyll" - url: "/documentation-theme-jekyll/mydoc_yaml_tutorial/" - link: "YAML tutorial in the context of Jekyll" - - - -mydoc_tags: - title: "Tags" - url: "/documentation-theme-jekyll/mydoc_tags/" - link: "Tags" - - - -mydoc_series: - title: "Series" - url: "/documentation-theme-jekyll/mydoc_series/" - link: "Series" - - - - - -mydoc_adding_tooltips: - title: "Tooltips" - url: "/documentation-theme-jekyll/mydoc_adding_tooltips/" - link: "Tooltips" - - - -mydoc_alerts: - title: "Alerts" - url: "/documentation-theme-jekyll/mydoc_alerts/" - link: "Alerts" - - - -mydoc_icons: - title: "Icons" - url: "/documentation-theme-jekyll/mydoc_icons/" - link: "Icons" - - - -mydoc_images: - title: "Images" - url: "/documentation-theme-jekyll/mydoc_images/" - link: "Images" - - - -mydoc_labels: - title: "Labels" - url: "/documentation-theme-jekyll/mydoc_labels/" - link: "Labels" - - - -mydoc_hyperlinks: - title: "Links" - url: "/documentation-theme-jekyll/mydoc_hyperlinks/" - link: "Links" - - - -mydoc_navtabs: - title: "Navtabs" - url: "/documentation-theme-jekyll/mydoc_navtabs/" - link: "Navtabs" - - - -mydoc_tables: - title: "Tables" - url: "/documentation-theme-jekyll/mydoc_tables/" - link: "Tables" - - - -mydoc_syntax_highlighting: - title: "Syntax highlighting" - url: "/documentation-theme-jekyll/mydoc_syntax_highlighting/" - link: "Syntax highlighting" - - - - - -mydoc_commenting_on_files: - title: "Commenting on files" - url: "/documentation-theme-jekyll/mydoc_commenting_on_files/" - link: "Commenting on files" - - - - - -mydoc_build_arguments: - title: "Build arguments" - url: "/documentation-theme-jekyll/mydoc_build_arguments/" - link: "Build arguments" - - - -mydoc_themes: - title: "Themes" - url: "/documentation-theme-jekyll/mydoc_themes/" - link: "Themes" - - - -mydoc_title_checker: - title: "Check page title consistency" - url: "/documentation-theme-jekyll/mydoc_title_checker/" - link: "Check page title consistency" - - - -mydoc_generating_pdfs: - title: "Generating PDFs" - url: "/documentation-theme-jekyll/mydoc_generating_pdfs/" - link: "Generating PDFs" - - - -mydoc_help_api: - title: "Help APIs and UI tooltips" - url: "/documentation-theme-jekyll/mydoc_help_api/" - link: "Help APIs and UI tooltips" - - - -mydoc_search_configuration: - title: "Search configuration" - url: "/documentation-theme-jekyll/mydoc_search_configuration/" - link: "Search configuration" - - - -mydoc_iterm_profiles: - title: "iTerm profiles" - url: "/documentation-theme-jekyll/mydoc_iterm_profiles/" - link: "iTerm profiles" - - - -mydoc_push_build_to_server: - title: "Pushing builds to server" - url: "/documentation-theme-jekyll/mydoc_push_build_to_server/" - link: "Pushing builds to server" - - - -mydoc_no_password_prompts_scp: - title: "Getting around the password prompts in SCP" - url: "/documentation-theme-jekyll/mydoc_no_password_prompts_scp/" - link: "Getting around the password prompts in SCP" - - - -mydoc_publishing_github_pages: - title: "Publishing on Github Pages" - url: "/documentation-theme-jekyll/mydoc_publishing_github_pages/" - link: "Publishing on Github Pages" - - - - - -mydoc_kb_layout: - title: "Knowledge-base layout" - url: "/documentation-theme-jekyll/mydoc_kb_layout/" - link: "Knowledge-base layout" - - - -mydoc_glossary: - title: "Glossary layout" - url: "/documentation-theme-jekyll/mydoc_glossary/" - link: "Glossary layout" - - - -mydoc_faq_layout: - title: "FAQ layout" - url: "/documentation-theme-jekyll/mydoc_faq_layout/" - link: "FAQ layout" - - - - - -mydoc_troubleshooting: - title: "Troubleshooting" - url: "/documentation-theme-jekyll/mydoc_troubleshooting/" - link: "Troubleshooting" - - - - - -mydoc_tag_archives_overview: - title: "Tag archives overview" - url: "/documentation-theme-jekyll/mydoc_tag_archives_overview/" - link: "Tag archives overview" - - - -tag_formatting: - title: "Formatting pages" - url: "/documentation-theme-jekyll/tag_formatting/" - link: "Formatting pages" - - -tag_navigation: - title: "Navigation pages" - url: "/documentation-theme-jekyll/tag_navigation/" - link: "Navigation pages" - - -tag_content_types: - title: "Content types pages" - url: "/documentation-theme-jekyll/tag_content_types/" - link: "Content types pages" - - -tag_publishing: - title: "Publishing pages" - url: "/documentation-theme-jekyll/tag_publishing/" - link: "Publishing pages" - - -tag_special_layouts: - title: "Special layout pages" - url: "/documentation-theme-jekyll/tag_special_layouts/" - link: "Special layout pages" - - -tag_collaboration: - title: "Collaboration pages" - url: "/documentation-theme-jekyll/tag_collaboration/" - link: "Collaboration pages" - - -tag_troubleshooting: - title: "Troubleshooting pages" - url: "/documentation-theme-jekyll/tag_troubleshooting/" - link: "Troubleshooting pages" - - - - - - - - - - - - - - - - - - - - -p1_landing_page: - title: "Product 1 home" - url: "/documentation-theme-jekyll/p1_landing_page/" - link: "Product 1 home" - - - -p1_sample1: - title: "Sample 1" - url: "/documentation-theme-jekyll/p1_sample1/" - link: "Sample 1" - - - -p1_sample2: - title: "Sample 2" - url: "/documentation-theme-jekyll/p1_sample2/" - link: "Sample 2" - - - -p1_sample3: - title: "Sample 3" - url: "/documentation-theme-jekyll/p1_sample3/" - link: "Sample 3" - - - - - -p1_sample4: - title: "Sample 4" - url: "/documentation-theme-jekyll/p1_sample4/" - link: "Sample 4" - - - -p1_sample5: - title: "Sample 5" - url: "/documentation-theme-jekyll/p1_sample5/" - link: "Sample 5" - - - -p1_sample6: - title: "Sample 6" - url: "/documentation-theme-jekyll/p1_sample6/" - link: "Sample 6" - - - -p1_sample7: - title: "Sample 7" - url: "/documentation-theme-jekyll/p1_sample7/" - link: "Sample 7" - - - - - - - - - - - - - - - - - - - - - -p2_landing_page: - title: "Product 2 home" - url: "/documentation-theme-jekyll/p2_landing_page/" - link: "Product 2 home" - - - -p2_sample1: - title: "Sample 1" - url: "/documentation-theme-jekyll/p2_sample1/" - link: "Sample 1" - - - -p2_sample2: - title: "Sample 2" - url: "/documentation-theme-jekyll/p2_sample2/" - link: "Sample 2" - - - - - -p2_sample3: - title: "Sample 3" - url: "/documentation-theme-jekyll/p2_sample3/" - link: "Sample 3" - - - -p2_sample4: - title: "Sample 4" - url: "/documentation-theme-jekyll/p2_sample4/" - link: "Sample 4" - - - - - -p2_sample5: - title: "Sample 5" - url: "/documentation-theme-jekyll/p2_sample5/" - link: "Sample 5" - - - -p2_sample6: - title: "Sample 6" - url: "/documentation-theme-jekyll/p2_sample6/" - link: "Sample 6" - - - -p2_sample7: - title: "Sample 7" - url: "/documentation-theme-jekyll/p2_sample7/" - link: "Sample 7" - - - - - - - - - - - - - -news: - title: "News" - url: "news" - link: "News" - - - - - - - - - - - - - - - - - - - - -mydoc_introduction: - title: "Jekyll Documentation Theme" - url: "mydoc_introduction" - link: "Jekyll Documentation Theme" - - - -p1_landing_page: - title: "Product 1" - url: "p1_landing_page" - link: "Product 1" - - - -p2_landing_page: - title: "Product 2" - url: "p2_landing_page" - link: "Product 2" - - - - diff --git a/_data/otherlinks.yml b/_data/otherlinks.yml new file mode 100644 index 0000000..1d71a74 --- /dev/null +++ b/_data/otherlinks.yml @@ -0,0 +1,21 @@ + +# Follow the pattern here for the URLs -- no slash at the beginning, and include the .html. The link here is rendered exactly as is in the Markdown references. + +entries: +- title: other + folders: + + - title: Other Links + folderitems: + + - title: Automated links bookmark + exact_url: mydoc_hyperlinks.html#automatedlinks + ref: mydoc_hyperlinks-automatedlinks + + - title: Bookmark links + exact_url: mydoc_hyperlinks.html#bookmarklinks + ref: mydoc_hyperlinks-bookmarklinks + + - title: Some link bookmark + exact_url: mydoc_pages.html#someIdTag + ref: someIdTag diff --git a/_data/sidebars/home_sidebar.yml b/_data/sidebars/home_sidebar.yml index e914ce4..63d7d82 100644 --- a/_data/sidebars/home_sidebar.yml +++ b/_data/sidebars/home_sidebar.yml @@ -8,20 +8,15 @@ entries: - title: Products output: web folderitems: - - title: Home - url: / - output: web - type: homepage - title: News - url: /news/ + url: /news output: web - title: Theme instructions - url: /mydoc_introduction/ + url: /mydoc_introduction output: web - title: Product 1 - url: /p1_landing_page/ + url: /p1_landing_page output: web - title: Product 2 - url: /p2_landing_page/ + url: /p2_landing_page output: web - diff --git a/_data/sidebars/mydoc_sidebar.yml b/_data/sidebars/mydoc_sidebar.yml index 2af1e89..a638369 100644 --- a/_data/sidebars/mydoc_sidebar.yml +++ b/_data/sidebars/mydoc_sidebar.yml @@ -3,7 +3,7 @@ entries: - title: sidebar product: Jekyll Doc Theme - version: 5.0 + version: 6.0 folders: - title: @@ -11,11 +11,11 @@ entries: type: frontmatter folderitems: - title: - url: /titlepage/ + url: /titlepage output: pdf type: frontmatter - title: - url: /tocpage/ + url: /tocpage output: pdf type: frontmatter @@ -24,32 +24,35 @@ entries: folderitems: - title: Get started - url: / - type: homepage - output: web, pdf - - - title: 5.0 Release notes - url: /mydoc_release_notes_50/ - output: web, pdf - - - title: Sample page - url: /samplepage/ + url: /index output: web, pdf - title: Introduction - url: /mydoc_introduction/ + url: /mydoc_introduction output: web, pdf - title: Supported features - url: /mydoc_supported_features/ + url: /mydoc_supported_features output: web, pdf - title: About the theme author - url: /mydoc_about/ + url: /mydoc_about output: web, pdf - title: Support - url: /mydoc_support/ + url: /mydoc_support + output: web, pdf + + - title: Release Notes + output: web, pdf + folderitems: + + - title: 6.0 Release notes + url: /mydoc_release_notes_60 + output: web, pdf + + - title: 5.0 Release notes + url: /mydoc_release_notes_50 output: web, pdf - title: Installation @@ -57,184 +60,200 @@ entries: folderitems: - title: About Ruby, Gems, Bundler, etc. - url: /mydoc_about_ruby_gems_etc/ + url: /mydoc_about_ruby_gems_etc output: web, pdf - title: Install Jekyll on Mac - url: /mydoc_install_jekyll_on_mac/ + url: /mydoc_install_jekyll_on_mac output: web, pdf - title: Install Jekyll on Windows - url: /mydoc_install_jekyll_on_windows/ + url: /mydoc_install_jekyll_on_windows output: web, pdf - title: Authoring output: web, pdf - + folderitems: - title: Pages - url: /mydoc_pages/ + url: /mydoc_pages output: web, pdf - title: Posts - url: /mydoc_posts/ + url: /mydoc_posts output: web, pdf - - title: WebStorm Text Editor - url: /mydoc_webstorm_text_editor/ + - title: Lists + url: /mydoc_lists output: web, pdf - title: Conditional logic - url: /mydoc_conditional_logic/ + url: /mydoc_conditional_logic output: web, pdf - title: Content reuse - url: /mydoc_content_reuse/ + url: /mydoc_content_reuse output: web, pdf - title: Collections - url: /mydoc_collections/ + url: /mydoc_collections + output: web, pdf + + - title: WebStorm editor tips + url: /mydoc_webstorm_text_editor + output: web, pdf + + - title: Atom editor tips + url: /mydoc_atom_text_editor output: web, pdf - title: Navigation output: web, pdf - + folderitems: - title: Sidebar navigation - url: /mydoc_sidebar_navigation/ + url: /mydoc_sidebar_navigation output: web, pdf - title: YAML tutorial in the context of Jekyll - url: /mydoc_yaml_tutorial/ + url: /mydoc_yaml_tutorial output: web, pdf - title: Tags - url: /mydoc_tags/ + url: /mydoc_tags output: web, pdf - title: Series - url: /mydoc_series/ + url: /mydoc_series output: web, pdf - title: Formatting output: web, pdf - + folderitems: - title: Tooltips - url: /mydoc_adding_tooltips/ + url: /mydoc_adding_tooltips output: web, pdf - title: Alerts - url: /mydoc_alerts/ + url: /mydoc_alerts output: web, pdf - title: Icons - url: /mydoc_icons/ + url: /mydoc_icons output: web, pdf - title: Images - url: /mydoc_images/ + url: /mydoc_images + output: web, pdf + + - title: Code samples + url: /mydoc_code_samples output: web, pdf - title: Labels - url: /mydoc_labels/ + url: /mydoc_labels output: web, pdf - title: Links - url: /mydoc_hyperlinks/ + url: /mydoc_hyperlinks output: web, pdf - title: Navtabs - url: /mydoc_navtabs/ + url: /mydoc_navtabs output: web, pdf - title: Tables - url: /mydoc_tables/ + url: /mydoc_tables output: web, pdf - title: Syntax highlighting - url: /mydoc_syntax_highlighting/ + url: /mydoc_syntax_highlighting + output: web, pdf + + - title: Workflow maps + url: /mydoc_workflow_maps output: web, pdf - title: Handling reviews output: web, pdf - + folderitems: - title: Commenting on files - url: /mydoc_commenting_on_files/ + url: /mydoc_commenting_on_files output: web, pdf # - title: Git collaboration -# url: /mydoc_git_collaboration/ +# url: /mydoc_git_collaboration # output: web, pdf - title: Publishing output: web, pdf - + folderitems: - title: Build arguments - url: /mydoc_build_arguments/ + url: /mydoc_build_arguments output: web, pdf - title: Themes - url: /mydoc_themes/ + url: /mydoc_themes output: web, pdf - title: Check page title consistency - url: /mydoc_title_checker/ + url: /mydoc_title_checker output: web, pdf - title: Generating PDFs - url: /mydoc_generating_pdfs/ + url: /mydoc_generating_pdfs output: web, pdf - title: Help APIs and UI tooltips - url: /mydoc_help_api/ + url: /mydoc_help_api output: web, pdf - title: Search configuration - url: /mydoc_search_configuration/ + url: /mydoc_search_configuration output: web, pdf - title: iTerm profiles - url: /mydoc_iterm_profiles/ + url: /mydoc_iterm_profiles output: web, pdf - title: Pushing builds to server - url: /mydoc_push_build_to_server/ + url: /mydoc_push_build_to_server output: web, pdf - title: Getting around the password prompts in SCP - url: /mydoc_no_password_prompts_scp/ + url: /mydoc_no_password_prompts_scp output: web, pdf - title: Publishing on Github Pages - url: /mydoc_publishing_github_pages/ + url: /mydoc_publishing_github_pages output: web, pdf - title: Special layouts output: web, pdf - + folderitems: - title: Knowledge-base layout - url: /mydoc_kb_layout/ + url: /mydoc_kb_layout output: web, pdf - title: Glossary layout - url: /mydoc_glossary/ + url: /mydoc_glossary output: web, pdf - title: FAQ layout - url: /mydoc_faq_layout/ + url: /mydoc_faq_layout output: web, pdf - title: Troubleshooting output: web, pdf - + folderitems: - title: Troubleshooting - url: /mydoc_troubleshooting/ + url: /mydoc_troubleshooting output: web, pdf - title: Tag archives @@ -242,7 +261,7 @@ entries: folderitems: - title: Tag archives overview - url: /mydoc_tag_archives_overview/ + url: /mydoc_tag_archives_overview output: web subfolders: @@ -251,29 +270,29 @@ entries: subfolderitems: - title: Formatting pages - url: /tag_formatting/ + url: /tag_formatting output: web - title: Navigation pages - url: /tag_navigation/ + url: /tag_navigation output: web - title: Content types pages - url: /tag_content_types/ + url: /tag_content_types output: web - title: Publishing pages - url: /tag_publishing/ + url: /tag_publishing output: web - title: Special layout pages - url: /tag_special_layouts/ + url: /tag_special_layouts output: web - title: Collaboration pages - url: /tag_collaboration/ + url: /tag_collaboration output: web - title: Troubleshooting pages - url: /tag_troubleshooting/ - output: web \ No newline at end of file + url: /tag_troubleshooting + output: web diff --git a/_data/sidebars/product1_sidebar.yml b/_data/sidebars/product1_sidebar.yml index 2ea2436..e679b68 100644 --- a/_data/sidebars/product1_sidebar.yml +++ b/_data/sidebars/product1_sidebar.yml @@ -12,11 +12,11 @@ entries: type: frontmatter folderitems: - title: - url: /titlepage/ + url: /titlepage output: pdf type: frontmatter - title: - url: /tocpage/ + url: /tocpage output: pdf type: frontmatter @@ -24,19 +24,19 @@ entries: output: web, pdf folderitems: - title: Product 1 home - url: /p1_landing_page/ + url: /p1_landing_page output: web - title: Sample 1 - url: /p1_sample1/ + url: /p1_sample1 output: web, pdf - + - title: Sample 2 - url: /p1_sample2/ + url: /p1_sample2 output: web, pdf - + - title: Sample 3 - url: /p1_sample3/ + url: /p1_sample3 output: web, pdf - title: Another heading @@ -44,17 +44,17 @@ entries: folderitems: - title: Sample 4 - url: /p1_sample4/ + url: /p1_sample4 output: web, pdf - + - title: Sample 5 - url: /p1_sample5/ + url: /p1_sample5 output: web, pdf - + - title: Sample 6 - url: /p1_sample6/ + url: /p1_sample6 output: web, pdf - + - title: Sample 7 - url: /p1_sample7/ - output: web, pdf \ No newline at end of file + url: /p1_sample7 + output: web, pdf diff --git a/_data/sidebars/product2_sidebar.yml b/_data/sidebars/product2_sidebar.yml index a30959e..2eefda3 100644 --- a/_data/sidebars/product2_sidebar.yml +++ b/_data/sidebars/product2_sidebar.yml @@ -12,11 +12,11 @@ entries: folderitems: - title: - url: /titlepage/ + url: titlepage output: pdf type: frontmatter - title: - url: /tocpage/ + url: tocpage output: pdf type: frontmatter @@ -25,7 +25,7 @@ entries: folderitems: - title: Overview - url: /p2_landing_page/ + url: /p2_landing_page output: web - title: Simple Workflow @@ -33,23 +33,23 @@ entries: folderitems: - title: Sample 1 - url: /p2_sample1/ + url: /p2_sample1 output: web, pdf - title: Sample 2 - url: /p2_sample2/ + url: /p2_sample2 output: web, pdf - title: Sample 3 - url: /p2_sample3/ + url: /p2_sample3 output: web, pdf - title: Sample 4 - url: /p2_sample4/ + url: /p2_sample4 output: web, pdf - title: Sample 5 - url: /p2_sample5/ + url: /p2_sample5 output: web, pdf - title: Complex Workflow @@ -57,37 +57,37 @@ entries: folderitems: - title: Sample 6 - url: /p2_sample6/ + url: /p2_sample6 output: web, pdf - title: Sample 7 - url: /p2_sample7/ + url: /p2_sample7 output: web, pdf - title: Sample 8 - url: /p2_sample8/ + url: /p2_sample8 output: web, pdf - title: Sample 9 - url: /p2_sample9/ + url: /p2_sample9 output: web, pdf - title: Sample 10 - url: /p2_sample10/ + url: /p2_sample10 output: web, pdf - title: Sample 11 - url: /p2_sample11/ + url: /p2_sample11 output: web, pdf - title: Sample 12 - url: /p2_sample12/ + url: /p2_sample12 output: web, pdf - title: Sample 13 - url: /p2_sample13/ + url: /p2_sample13 output: web, pdf - title: Sample 14 - url: /p2_sample14/ + url: /p2_sample14 output: web, pdf diff --git a/_data/sidebars/tags_sidebar.yml b/_data/sidebars/tags_sidebar.yml deleted file mode 100644 index bc37ae9..0000000 --- a/_data/sidebars/tags_sidebar.yml +++ /dev/null @@ -1,54 +0,0 @@ - -entries: -- title: Tags Sidebar - product: Tags - version: all products - levels: one - output: web - folders: - - - title: News - output: web - folderitems: - - title: News - url: /news/ - output: web - - title: News archive - url: /news_archive/ - output: web - - title: Tags - output: web - folderitems: - - title: Collaboration - url: /tag_collaboration/ - output: web - - title: Content Types - url: /tag_content_types/ - output: web - - title: Formatting - url: /tag_formatting/ - output: web - - title: Getting started - url: /tag_getting_started/ - output: web - - title: Mobile - url: /tag_mobile/ - output: web - - title: Navigation - url: /tag_navigation/ - output: web - - title: News - url: /tag_news/ - output: web - - title: Publishing - url: /tag_publishing/ - output: web - - title: Single sourcing - url: /tag_single_sourcing/ - output: web - - title: Special layouts - url: /tag_special_layouts/ - output: web - - title: Troubleshooting - url: /tag_troubleshooting/ - output: web \ No newline at end of file diff --git a/_data/topnav.yml b/_data/topnav.yml index f66735d..51806a2 100644 --- a/_data/topnav.yml +++ b/_data/topnav.yml @@ -4,7 +4,7 @@ topnav: - title: Topnav items: - title: News - url: /news/ + url: /news #Topnav dropdowns topnav_dropdowns: @@ -25,11 +25,8 @@ topnav_dropdowns: - title: Products folderitems: - title: Jekyll Documentation Theme - url: /mydoc_introduction/ + url: /mydoc_introduction - title: Product 1 - url: /p1_landing_page/ + url: /p1_landing_page - title: Product 2 - url: /p2_landing_page/ - - - + url: /p2_landing_page diff --git a/_data/urls.yml b/_data/urls.yml deleted file mode 100644 index 12fd3a7..0000000 --- a/_data/urls.yml +++ /dev/null @@ -1,686 +0,0 @@ - - - - - - - - - - - - - -mydoc_release_notes_50: - title: "5.0 Release notes" - url: /documentation-theme-jekyll/mydoc_release_notes_50/ - link: 5.0 Release notes - - - -samplepage: - title: "Sample page" - url: /documentation-theme-jekyll/samplepage/ - link: Sample page - - - -mydoc_introduction: - title: "Introduction" - url: /documentation-theme-jekyll/mydoc_introduction/ - link: Introduction - - - -mydoc_supported_features: - title: "Supported features" - url: /documentation-theme-jekyll/mydoc_supported_features/ - link: Supported features - - - -mydoc_about: - title: "About the theme author" - url: /documentation-theme-jekyll/mydoc_about/ - link: About the theme author - - - -mydoc_support: - title: "Support" - url: /documentation-theme-jekyll/mydoc_support/ - link: Support - - - - - -mydoc_about_ruby_gems_etc: - title: "About Ruby, Gems, Bundler, etc." - url: /documentation-theme-jekyll/mydoc_about_ruby_gems_etc/ - link: About Ruby, Gems, Bundler, etc. - - - -mydoc_install_jekyll_on_mac: - title: "Install Jekyll on Mac" - url: /documentation-theme-jekyll/mydoc_install_jekyll_on_mac/ - link: Install Jekyll on Mac - - - -mydoc_install_jekyll_on_windows: - title: "Install Jekyll on Windows" - url: /documentation-theme-jekyll/mydoc_install_jekyll_on_windows/ - link: Install Jekyll on Windows - - - - - -mydoc_pages: - title: "Pages" - url: /documentation-theme-jekyll/mydoc_pages/ - link: Pages - - - -mydoc_posts: - title: "Posts" - url: /documentation-theme-jekyll/mydoc_posts/ - link: Posts - - - -mydoc_webstorm_text_editor: - title: "WebStorm Text Editor" - url: /documentation-theme-jekyll/mydoc_webstorm_text_editor/ - link: WebStorm Text Editor - - - -mydoc_conditional_logic: - title: "Conditional logic" - url: /documentation-theme-jekyll/mydoc_conditional_logic/ - link: Conditional logic - - - -mydoc_content_reuse: - title: "Content reuse" - url: /documentation-theme-jekyll/mydoc_content_reuse/ - link: Content reuse - - - -mydoc_collections: - title: "Collections" - url: /documentation-theme-jekyll/mydoc_collections/ - link: Collections - - - - - -mydoc_sidebar_navigation: - title: "Sidebar navigation" - url: /documentation-theme-jekyll/mydoc_sidebar_navigation/ - link: Sidebar navigation - - - -mydoc_yaml_tutorial: - title: "YAML tutorial in the context of Jekyll" - url: /documentation-theme-jekyll/mydoc_yaml_tutorial/ - link: YAML tutorial in the context of Jekyll - - - -mydoc_tags: - title: "Tags" - url: /documentation-theme-jekyll/mydoc_tags/ - link: Tags - - - -mydoc_series: - title: "Series" - url: /documentation-theme-jekyll/mydoc_series/ - link: Series - - - - - -mydoc_adding_tooltips: - title: "Tooltips" - url: /documentation-theme-jekyll/mydoc_adding_tooltips/ - link: Tooltips - - - -mydoc_alerts: - title: "Alerts" - url: /documentation-theme-jekyll/mydoc_alerts/ - link: Alerts - - - -mydoc_icons: - title: "Icons" - url: /documentation-theme-jekyll/mydoc_icons/ - link: Icons - - - -mydoc_images: - title: "Images" - url: /documentation-theme-jekyll/mydoc_images/ - link: Images - - - -mydoc_labels: - title: "Labels" - url: /documentation-theme-jekyll/mydoc_labels/ - link: Labels - - - -mydoc_hyperlinks: - title: "Links" - url: /documentation-theme-jekyll/mydoc_hyperlinks/ - link: Links - - - -mydoc_navtabs: - title: "Navtabs" - url: /documentation-theme-jekyll/mydoc_navtabs/ - link: Navtabs - - - -mydoc_tables: - title: "Tables" - url: /documentation-theme-jekyll/mydoc_tables/ - link: Tables - - - -mydoc_syntax_highlighting: - title: "Syntax highlighting" - url: /documentation-theme-jekyll/mydoc_syntax_highlighting/ - link: Syntax highlighting - - - - - -mydoc_commenting_on_files: - title: "Commenting on files" - url: /documentation-theme-jekyll/mydoc_commenting_on_files/ - link: Commenting on files - - - - - -mydoc_build_arguments: - title: "Build arguments" - url: /documentation-theme-jekyll/mydoc_build_arguments/ - link: Build arguments - - - -mydoc_themes: - title: "Themes" - url: /documentation-theme-jekyll/mydoc_themes/ - link: Themes - - - -mydoc_title_checker: - title: "Check page title consistency" - url: /documentation-theme-jekyll/mydoc_title_checker/ - link: Check page title consistency - - - -mydoc_generating_pdfs: - title: "Generating PDFs" - url: /documentation-theme-jekyll/mydoc_generating_pdfs/ - link: Generating PDFs - - - -mydoc_help_api: - title: "Help APIs and UI tooltips" - url: /documentation-theme-jekyll/mydoc_help_api/ - link: Help APIs and UI tooltips - - - -mydoc_search_configuration: - title: "Search configuration" - url: /documentation-theme-jekyll/mydoc_search_configuration/ - link: Search configuration - - - -mydoc_iterm_profiles: - title: "iTerm profiles" - url: /documentation-theme-jekyll/mydoc_iterm_profiles/ - link: iTerm profiles - - - -mydoc_push_build_to_server: - title: "Pushing builds to server" - url: /documentation-theme-jekyll/mydoc_push_build_to_server/ - link: Pushing builds to server - - - -mydoc_no_password_prompts_scp: - title: "Getting around the password prompts in SCP" - url: /documentation-theme-jekyll/mydoc_no_password_prompts_scp/ - link: Getting around the password prompts in SCP - - - -mydoc_publishing_github_pages: - title: "Publishing on Github Pages" - url: /documentation-theme-jekyll/mydoc_publishing_github_pages/ - link: Publishing on Github Pages - - - - - -mydoc_kb_layout: - title: "Knowledge-base layout" - url: /documentation-theme-jekyll/mydoc_kb_layout/ - link: Knowledge-base layout - - - -mydoc_glossary: - title: "Glossary layout" - url: /documentation-theme-jekyll/mydoc_glossary/ - link: Glossary layout - - - -mydoc_faq_layout: - title: "FAQ layout" - url: /documentation-theme-jekyll/mydoc_faq_layout/ - link: FAQ layout - - - - - -mydoc_troubleshooting: - title: "Troubleshooting" - url: /documentation-theme-jekyll/mydoc_troubleshooting/ - link: Troubleshooting - - - - - -mydoc_tag_archives_overview: - title: "Tag archives overview" - url: /documentation-theme-jekyll/mydoc_tag_archives_overview/ - link: Tag archives overview - - - -tag_formatting: - title: "Formatting pages" - url: /documentation-theme-jekyll/tag_formatting/ - link: Formatting pages - - -tag_navigation: - title: "Navigation pages" - url: /documentation-theme-jekyll/tag_navigation/ - link: Navigation pages - - -tag_content_types: - title: "Content types pages" - url: /documentation-theme-jekyll/tag_content_types/ - link: Content types pages - - -tag_publishing: - title: "Publishing pages" - url: /documentation-theme-jekyll/tag_publishing/ - link: Publishing pages - - -tag_special_layouts: - title: "Special layout pages" - url: /documentation-theme-jekyll/tag_special_layouts/ - link: Special layout pages - - -tag_collaboration: - title: "Collaboration pages" - url: /documentation-theme-jekyll/tag_collaboration/ - link: Collaboration pages - - -tag_troubleshooting: - title: "Troubleshooting pages" - url: /documentation-theme-jekyll/tag_troubleshooting/ - link: Troubleshooting pages - - - - - - - - - - - - - - - - - - -p1_landing_page: - title: "Product 1 home" - url: /documentation-theme-jekyll/p1_landing_page/ - link: Product 1 home - - - -p1_sample1: - title: "Sample 1" - url: /documentation-theme-jekyll/p1_sample1/ - link: Sample 1 - - - -p1_sample2: - title: "Sample 2" - url: /documentation-theme-jekyll/p1_sample2/ - link: Sample 2 - - - -p1_sample3: - title: "Sample 3" - url: /documentation-theme-jekyll/p1_sample3/ - link: Sample 3 - - - - - -p1_sample4: - title: "Sample 4" - url: /documentation-theme-jekyll/p1_sample4/ - link: Sample 4 - - - -p1_sample5: - title: "Sample 5" - url: /documentation-theme-jekyll/p1_sample5/ - link: Sample 5 - - - -p1_sample6: - title: "Sample 6" - url: /documentation-theme-jekyll/p1_sample6/ - link: Sample 6 - - - -p1_sample7: - title: "Sample 7" - url: /documentation-theme-jekyll/p1_sample7/ - link: Sample 7 - - - - - - - - - - - - - - - - - -p2_landing_page: - title: "Simple Workflow" - url: /documentation-theme-jekyll/p2_landing_page/ - link: Simple Workflow - - - -p2_sample1: - title: "Sample 1" - url: /documentation-theme-jekyll/p2_sample1/ - link: Sample 1 - - - -p2_sample2: - title: "Sample 2" - url: /documentation-theme-jekyll/p2_sample2/ - link: Sample 2 - - - -p2_sample3: - title: "Sample 3" - url: /documentation-theme-jekyll/p2_sample3/ - link: Sample 3 - - - -p2_sample4: - title: "Sample 4" - url: /documentation-theme-jekyll/p2_sample4/ - link: Sample 4 - - - -p2_sample5: - title: "Sample 5" - url: /documentation-theme-jekyll/p2_sample5/ - link: Sample 5 - - - - - -p2_sample6: - title: "Sample 6" - url: /documentation-theme-jekyll/p2_sample6/ - link: Sample 6 - - - -p2_sample7: - title: "Sample 7" - url: /documentation-theme-jekyll/p2_sample7/ - link: Sample 7 - - - -p2_sample8: - title: "Sample 8" - url: /documentation-theme-jekyll/p2_sample8/ - link: Sample 8 - - - -p2_sample9: - title: "Sample 9" - url: /documentation-theme-jekyll/p2_sample9/ - link: Sample 9 - - - -p2_sample10: - title: "Sample 10" - url: /documentation-theme-jekyll/p2_sample10/ - link: Sample 10 - - - -p2_sample11: - title: "Sample 11" - url: /documentation-theme-jekyll/p2_sample11/ - link: Sample 11 - - - -p2_sample12: - title: "Sample 12" - url: /documentation-theme-jekyll/p2_sample12/ - link: Sample 12 - - - -p2_sample13: - title: "Sample 13" - url: /documentation-theme-jekyll/p2_sample13/ - link: Sample 13 - - - -p2_sample14: - title: "Sample 14" - url: /documentation-theme-jekyll/p2_sample14/ - link: Sample 14 - - - - - - - - - - - - - -news: - title: "News" - url: "news" - link: "News" - - - - - - - - - - - - - - - - - - - - -mydoc_introduction: - title: "Jekyll Documentation Theme" - url: "mydoc_introduction" - link: "Jekyll Documentation Theme" - - - -p1_landing_page: - title: "Product 1" - url: "p1_landing_page" - link: "Product 1" - - - -p2_landing_page: - title: "Product 2" - url: "p2_landing_page" - link: "Product 2" - - - - - - - - - - - - - -news: - title: "News" - url: "news" - link: "News" - - - - - - - - - - - - - - - - - - - - -mydoc_introduction: - title: "Jekyll Documentation Theme" - url: "mydoc_introduction" - link: "Jekyll Documentation Theme" - - - -p1_landing_page: - title: "Product 1" - url: "p1_landing_page" - link: "Product 1" - - - -p2_landing_page: - title: "Product 2" - url: "p2_landing_page" - link: "Product 2" - - - diff --git a/_includes/custom/sidebarconfigs.html b/_includes/custom/sidebarconfigs.html index cc1b8f3..36167ad 100644 --- a/_includes/custom/sidebarconfigs.html +++ b/_includes/custom/sidebarconfigs.html @@ -10,9 +10,6 @@ {% elsif page.sidebar == "mydoc_sidebar" %} {% assign sidebar = site.data.sidebars.mydoc_sidebar.entries %} -{% elsif page.sidebar == "tags_sidebar" %} -{% assign sidebar = site.data.sidebars.tags_sidebar.entries %} - {% else %} {% assign sidebar = site.data.sidebars.home_sidebar.entries %} {% endif %} diff --git a/_includes/custom/usermap.html b/_includes/custom/usermap.html index 581332c..f90b5c2 100644 --- a/_includes/custom/usermap.html +++ b/_includes/custom/usermap.html @@ -1,15 +1,14 @@
This is just dummy text ... Your first steps should be to get started. You will need to do the following:
If you run into any of these setup issues, you must solve them before you can continue on.
@@ -45,9 +45,9 @@In order to configure your widgets, you will need to follow these topics:
output: web
(rather than output: pdf
) in the list of attributes in your sidebar. The prince-list.txt file that loops through the mydoc_sidebar.yml file to grab the URLs of each page that should appear in the PDF will skip over any items that do not list output: pdf
in the item attributes. For example, you might not want your tag archives to appear in the PDF, but you probably will want to list them in the online help navigation. {{site.data.alerts.end}}
+{% include note.html content="If you have any files that you do not want to appear in the PDF, add output: web
(rather than output: pdf
) in the list of attributes in your sidebar. The prince-list.txt file that loops through the mydoc_sidebar.yml file to grab the URLs of each page that should appear in the PDF will skip over any items that do not list output: pdf
in the item attributes. For example, you might not want your tag archives to appear in the PDF, but you probably will want to list them in the online help navigation." %}
## 4. Customize your headers and footers
@@ -120,7 +120,7 @@ a[href*="mailto"]::after, a[data-toggle="tooltip"]::after, a[href].noCrossRef::a
```
{% endraw %}
-{{site.data.alerts.tip}} If you have a link to a file download, or some other link that shouldn't have a cross reference (such as link used in JavaScript for navtabs or collapsible sections, for example, add `noCrossRef` as a class to the link to avoid having it say "page 0" in the cross reference.{{site.data.alerts.end}}
+{% include tip.html content="If you have a link to a file download, or some other link that shouldn't have a cross reference (such as link used in JavaScript for navtabs or collapsible sections, for example, add `noCrossRef` as a class to the link to avoid having it say \"page 0\" in the cross reference." %}
This style specifies that after links to web resources, the URL should be inserted instead of the page number:
@@ -314,19 +314,14 @@ The prince script issues a command to the Prince utility. JavaScript is enabled
Make sure that the path to the prince-list.txt is correct. For the output directory, I like to output the PDF file into my project's source (into the files folder). Then when I build the web output, the PDF is included and something I can refer to.
-{{site.data.alerts.note}} You might not want to include the PDF in your project files, since you're likely committing the PDF to Github and as a result saving the changes from one PDF version to another with each save. {{site.data.alerts.end}}
+{% include note.html content="You might not want to include the PDF in your project files, since you're likely committing the PDF to Github and as a result saving the changes from one PDF version to another with each save." %}
## 6. Add conditions for your new builds in the sidebarconfigs.html file
In the \_includes/custom/sidebarconfigs.html file, there's a section that looks like this:
```
-
-{% comment %}
-sidebar configuration for print files
-{% endcomment %}
-
-{% if site.product == "mydoc" %}
+{% raw %}{% if site.product == "mydoc" %}
{% assign sidebar_pdf = site.data.sidebars.mydoc_sidebar.entries %}
{% endif %}
@@ -336,7 +331,7 @@ sidebar configuration for print files
{% if site.product == "product2" %}
{% assign sidebar_pdf = site.data.sidebars.product2_sidebar.entries %}
-{% endif %}
+{% endif %}{% endraw %}
```
Add your own condition here that points to your sidebar.
@@ -377,7 +372,7 @@ javascript content here ...
```
{% endraw %}
-For more detail about using `unless` in conditional logic, see {{site.data.mydoc.mydoc_urls.mydoc_conditional_logic.link}}. What this code means is "run this code unless this value is the case."
+For more detail about using `unless` in conditional logic, see [Conditional logic][mydoc_conditional_logic]. What this code means is "run this code unless this value is the case."
## Overriding Bootstrap Print Styles
@@ -397,3 +392,5 @@ This is problematic for code snippets that have syntax highlighting. I decided t
If you update Bootrap, make sure you make this edit. (Sorry, admittedly I couldn't figure out how to simply overwrite the `*` selector with a later style.)
I did, however, remove the color from the alerts and lighten the background shading for `pre` elements. The printstyles.css has this setting.
+
+{% include links.html %}
diff --git a/mydoc/mydoc_git_collaboration.md b/_pages/mydoc/mydoc_git_collaboration.md
similarity index 99%
rename from mydoc/mydoc_git_collaboration.md
rename to _pages/mydoc/mydoc_git_collaboration.md
index 5b42aa4..fc30d35 100644
--- a/mydoc/mydoc_git_collaboration.md
+++ b/_pages/mydoc/mydoc_git_collaboration.md
@@ -5,7 +5,7 @@ tags: collaboration
keywords: git, github, collaboration, interaction, file sharing, push
published: false
sidebar: mydoc_sidebar
-permalink: /mydoc_git_collaboration/
+permalink: mydoc_git_collaboration
folder: mydoc
---
@@ -180,3 +180,6 @@ From the interface, you can also create a pull request to merge all of the chang
| see what has changed since last commit | `git diff` |
| commit changes | `git commit` |
| | |
+
+
+{% include links.html %}
diff --git a/mydoc/mydoc_glossary.md b/_pages/mydoc/mydoc_glossary.md
similarity index 74%
rename from mydoc/mydoc_glossary.md
rename to _pages/mydoc/mydoc_glossary.md
index 9461374..9ff0b20 100644
--- a/mydoc/mydoc_glossary.md
+++ b/_pages/mydoc/mydoc_glossary.md
@@ -2,10 +2,10 @@
title: Glossary layout
tags: [formatting, special_layouts]
keywords: definitions, glossaries, terms, style guide
-last_updated: March 20, 2016
+last_updated: July 3, 2016
summary: "Your glossary page can take advantage of definitions stored in a data file. This gives you the ability to reuse the same definition in multiple places. Additionally, you can use Bootstrap classes to arrange your definition list horizontally."
sidebar: mydoc_sidebar
-permalink: /mydoc_glossary/
+permalink: mydoc_glossary
toc: false
folder: mydoc
---
@@ -15,53 +15,39 @@ You can create a glossary for your content. First create your glossary items in
Then create a page and use definition list formatting, like this:
-```html
-This is just dummy text ... Your first steps should be to get started. You will need to do the following:
+ + +If you run into any of these setup issues, you must solve them before you can continue on.
+ ++ + +myModal3" tabindex="-1" role="dialog" aria-labelledby="myModalLabel"> + + +2. For each topic where you want the modal to appear, insert the following properties in your frontmatter: + ++ --- + title: Sample 6 Topic + keywords: sample + summary: "This is just a sample topic..." + sidebar: product2_sidebar + permalink: p2_sample6 + complex_map: true + map_name: usermapcomplex + box_number: 1 + toc: false + folder: product2 + --- ++ + When your frontmatter contains `complex_map` equal to `true`, the following code gets activated in the page layout.html file: + + ``` + In the page.html layout, the following code gets activated when `map` equals `true`: + + ``` + {% raw %}{% if page.complex_map == true %} + + + + {% include custom/{{page.map_name}}.html %} + + {% endif %}{% endraw %} + ``` + ``` + +{% include links.html %} \ No newline at end of file diff --git a/mydoc/mydoc_yaml_tutorial.md b/_pages/mydoc/mydoc_yaml_tutorial.md similarity index 97% rename from mydoc/mydoc_yaml_tutorial.md rename to _pages/mydoc/mydoc_yaml_tutorial.md index 9b12d32..b47faab 100644 --- a/mydoc/mydoc_yaml_tutorial.md +++ b/_pages/mydoc/mydoc_yaml_tutorial.md @@ -4,7 +4,7 @@ tags: [formatting] keywords: search summary: "YAML is a format that relies on white spacing to separate out the various elements of content. Jekyll lets you use Liquid with YAML as a way to parse through the data. Storing items for your table of contents is one of the most common uses of YAML with Jekyll." sidebar: mydoc_sidebar -permalink: /mydoc_yaml_tutorial/ +permalink: mydoc_yaml_tutorial folder: mydoc --- ## Overview @@ -27,7 +27,7 @@ YAML itself doesn't do anything on its own — it's just a way of storing yo ## YAML basics You can read about YAML from a lot of different sources. Here are some basic characteristics of YAML: -* YAML ("**Y**AML **A**in't **M**arkup **L**anguage") doesn't use markup tags. This means you won't see any kind of angle brackets. It uses white space as a way to form the structure. This makes YAML much more human readable. +* YAML ("YAML Ain't Markup Language") doesn't use markup tags. This means you won't see any kind of angle brackets. It uses white space as a way to form the structure. This makes YAML much more human readable. * Because YAML does use white space for the structure, YAML is extremely picky about the exactness of spaces. If you have just one extra space somewhere, it can cause the whole file to be invalid. * For each new level in YAML, you indent two spaces. Each level provides a different access point for the content. You use dot notation to access each new level. * Because tabs are not universally implemented the same way in editors, a tab might not equate to two spaces. In general, it's best to manually type two spaces to create a new level in YAML. @@ -387,3 +387,5 @@ And here is the result: ## More resources For more examples and explanations, see this helpful post on tournemille.com: [How to create data-driven navigation in Jekyll](http://www.tournemille.com/blog/How-to-create-data-driven-navigation-in-Jekyll/). + +{% include links.html %} diff --git a/news/news.html b/_pages/news/news.html similarity index 98% rename from news/news.html rename to _pages/news/news.html index 281fd3a..cea494d 100644 --- a/news/news.html +++ b/_pages/news/news.html @@ -2,7 +2,7 @@ title: News sidebar: home_sidebar keywords: news, blog, updates, release notes, announcements -permalink: /news/ +permalink: news toc: false folder: news --- diff --git a/news/news_archive.html b/_pages/news/news_archive.html similarity index 97% rename from news/news_archive.html rename to _pages/news/news_archive.html index 2d1bcc1..0ef4b2e 100644 --- a/news/news_archive.html +++ b/_pages/news/news_archive.html @@ -2,7 +2,7 @@ title: News sidebar: tags_sidebar keywords: news, blog, updates, release notes, announcements -permalink: /news_archive/ +permalink: news_archive toc: false folder: news --- diff --git a/product1/p1_landing_page.html b/_pages/product1/p1_landing_page.html similarity index 99% rename from product1/p1_landing_page.html rename to _pages/product1/p1_landing_page.html index 8ce1e56..bd7702d 100644 --- a/product1/p1_landing_page.html +++ b/_pages/product1/p1_landing_page.html @@ -3,7 +3,7 @@ title: Product 1 keywords: mydoc sidebar: product1_sidebar toc: false -permalink: /p1_landing_page/ +permalink: p1_landing_page folder: product1 ---diff --git a/product1/p1_sample1.md b/_pages/product1/p1_sample1.md similarity index 98% rename from product1/p1_sample1.md rename to _pages/product1/p1_sample1.md index a22d2a2..19b94ab 100644 --- a/product1/p1_sample1.md +++ b/_pages/product1/p1_sample1.md @@ -3,7 +3,7 @@ title: Sample 1 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample1/ +permalink: p1_sample1 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample2.md b/_pages/product1/p1_sample2.md similarity index 98% rename from product1/p1_sample2.md rename to _pages/product1/p1_sample2.md index d15448f..de12a6b 100644 --- a/product1/p1_sample2.md +++ b/_pages/product1/p1_sample2.md @@ -3,7 +3,7 @@ title: Sample 2 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample2/ +permalink: p1_sample2 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample3.md b/_pages/product1/p1_sample3.md similarity index 98% rename from product1/p1_sample3.md rename to _pages/product1/p1_sample3.md index f54b457..85cf602 100644 --- a/product1/p1_sample3.md +++ b/_pages/product1/p1_sample3.md @@ -3,7 +3,7 @@ title: Sample 3 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample3/ +permalink: p1_sample3 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample4.md b/_pages/product1/p1_sample4.md similarity index 98% rename from product1/p1_sample4.md rename to _pages/product1/p1_sample4.md index 9495388..a900c8f 100644 --- a/product1/p1_sample4.md +++ b/_pages/product1/p1_sample4.md @@ -3,7 +3,7 @@ title: Sample 4 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample4/ +permalink: p1_sample4 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample5.md b/_pages/product1/p1_sample5.md similarity index 98% rename from product1/p1_sample5.md rename to _pages/product1/p1_sample5.md index 81b8d6e..ccec465 100644 --- a/product1/p1_sample5.md +++ b/_pages/product1/p1_sample5.md @@ -3,7 +3,7 @@ title: Sample 5 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample5/ +permalink: p1_sample5 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample6.md b/_pages/product1/p1_sample6.md similarity index 98% rename from product1/p1_sample6.md rename to _pages/product1/p1_sample6.md index 58918c2..60a6202 100644 --- a/product1/p1_sample6.md +++ b/_pages/product1/p1_sample6.md @@ -3,7 +3,7 @@ title: Sample 6 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample6/ +permalink: p1_sample6 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product1/p1_sample7.md b/_pages/product1/p1_sample7.md similarity index 98% rename from product1/p1_sample7.md rename to _pages/product1/p1_sample7.md index 9bd9675..70d26b1 100644 --- a/product1/p1_sample7.md +++ b/_pages/product1/p1_sample7.md @@ -3,7 +3,7 @@ title: Sample 7 Topic (Product 1) keywords: sample summary: "This is just a sample topic..." sidebar: product1_sidebar -permalink: /p1_sample7/ +permalink: p1_sample7 folder: product1 --- @@ -21,3 +21,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_landing_page.html b/_pages/product2/p2_landing_page.html similarity index 99% rename from product2/p2_landing_page.html rename to _pages/product2/p2_landing_page.html index 9b111b3..d54b473 100644 --- a/product2/p2_landing_page.html +++ b/_pages/product2/p2_landing_page.html @@ -3,7 +3,7 @@ title: Product 2 keywords: mydoc sidebar: product2_sidebar toc: false -permalink: /p2_landing_page/ +permalink: p2_landing_page folder: product2 ---diff --git a/product2/p2_sample1.md b/_pages/product2/p2_sample1.md similarity index 98% rename from product2/p2_sample1.md rename to _pages/product2/p2_sample1.md index ab6074f..6668cc5 100644 --- a/product2/p2_sample1.md +++ b/_pages/product2/p2_sample1.md @@ -3,8 +3,8 @@ title: Sample 1 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample1/ -map: true +permalink: p2_sample1 +simple_map: true map_name: usermap box_number: 1 folder: product2 @@ -25,3 +25,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample10.md b/_pages/product2/p2_sample10.md similarity index 97% rename from product2/p2_sample10.md rename to _pages/product2/p2_sample10.md index ffe7e93..0534f6c 100644 --- a/product2/p2_sample10.md +++ b/_pages/product2/p2_sample10.md @@ -3,8 +3,8 @@ title: Sample 10 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample10/ -map: true +permalink: p2_sample10 +complex_map: true map_name: usermapcomplex box_number: 2 toc: false @@ -25,3 +25,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample11.md b/_pages/product2/p2_sample11.md similarity index 97% rename from product2/p2_sample11.md rename to _pages/product2/p2_sample11.md index e769d41..2235ae0 100644 --- a/product2/p2_sample11.md +++ b/_pages/product2/p2_sample11.md @@ -3,8 +3,8 @@ title: Sample 11 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample11/ -map: true +permalink: p2_sample11 +complex_map: true map_name: usermapcomplex box_number: 2 toc: false @@ -25,3 +25,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample12.md b/_pages/product2/p2_sample12.md similarity index 97% rename from product2/p2_sample12.md rename to _pages/product2/p2_sample12.md index 5d4c3a3..5f78b39 100644 --- a/product2/p2_sample12.md +++ b/_pages/product2/p2_sample12.md @@ -3,8 +3,8 @@ title: Sample 12 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample12/ -map: true +permalink: p2_sample12 +complex_map: true map_name: usermapcomplex box_number: 3 toc: false @@ -25,3 +25,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample13.md b/_pages/product2/p2_sample13.md similarity index 97% rename from product2/p2_sample13.md rename to _pages/product2/p2_sample13.md index 2e01e1b..6345daf 100644 --- a/product2/p2_sample13.md +++ b/_pages/product2/p2_sample13.md @@ -3,8 +3,8 @@ title: Sample 13 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample13/ -map: true +permalink: p2_sample13 +complex_map: true map_name: usermapcomplex box_number: 3 toc: false @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample14.md b/_pages/product2/p2_sample14.md similarity index 97% rename from product2/p2_sample14.md rename to _pages/product2/p2_sample14.md index 11f7f36..b1a7db4 100644 --- a/product2/p2_sample14.md +++ b/_pages/product2/p2_sample14.md @@ -3,8 +3,8 @@ title: Sample 14 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample14/ -map: true +permalink: p2_sample14 +complex_map: true map_name: usermapcomplex box_number: 3 toc: false @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample2.md b/_pages/product2/p2_sample2.md similarity index 98% rename from product2/p2_sample2.md rename to _pages/product2/p2_sample2.md index b1db786..4737e40 100644 --- a/product2/p2_sample2.md +++ b/_pages/product2/p2_sample2.md @@ -3,8 +3,8 @@ title: Sample 2 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample2/ -map: true +permalink: p2_sample2 +simple_map: true map_name: usermap box_number: 2 folder: product2 @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample3.md b/_pages/product2/p2_sample3.md similarity index 98% rename from product2/p2_sample3.md rename to _pages/product2/p2_sample3.md index 9d7075d..ca5c842 100644 --- a/product2/p2_sample3.md +++ b/_pages/product2/p2_sample3.md @@ -3,8 +3,8 @@ title: Sample 3 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample3/ -map: true +permalink: p2_sample3 +simple_map: true map_name: usermap box_number: 3 folder: product2 @@ -24,3 +24,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample4.md b/_pages/product2/p2_sample4.md similarity index 98% rename from product2/p2_sample4.md rename to _pages/product2/p2_sample4.md index 473a5f8..582ff66 100644 --- a/product2/p2_sample4.md +++ b/_pages/product2/p2_sample4.md @@ -3,8 +3,8 @@ title: Sample 4 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample4/ -map: true +permalink: p2_sample4 +simple_map: true map_name: usermap box_number: 4 folder: product2 @@ -24,3 +24,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample5.md b/_pages/product2/p2_sample5.md similarity index 98% rename from product2/p2_sample5.md rename to _pages/product2/p2_sample5.md index 746002c..b38a641 100644 --- a/product2/p2_sample5.md +++ b/_pages/product2/p2_sample5.md @@ -3,8 +3,8 @@ title: Sample 5 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample5/ -map: true +permalink: p2_sample5 +simple_map: true map_name: usermap box_number: 5 folder: product2 @@ -24,3 +24,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample6.md b/_pages/product2/p2_sample6.md similarity index 98% rename from product2/p2_sample6.md rename to _pages/product2/p2_sample6.md index 7ae4b50..47b7060 100644 --- a/product2/p2_sample6.md +++ b/_pages/product2/p2_sample6.md @@ -3,8 +3,8 @@ title: Sample 6 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample6/ -map: true +permalink: p2_sample6 +simple_map: true map_name: usermapcomplex box_number: 1 toc: false @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample7.md b/_pages/product2/p2_sample7.md similarity index 97% rename from product2/p2_sample7.md rename to _pages/product2/p2_sample7.md index b671329..8ebd1f3 100644 --- a/product2/p2_sample7.md +++ b/_pages/product2/p2_sample7.md @@ -3,8 +3,8 @@ title: Sample 7 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample7/ -map: true +permalink: p2_sample7 +complex_map: true map_name: usermapcomplex box_number: 1 toc: false @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample8.md b/_pages/product2/p2_sample8.md similarity index 97% rename from product2/p2_sample8.md rename to _pages/product2/p2_sample8.md index dab58b6..81b65b1 100644 --- a/product2/p2_sample8.md +++ b/_pages/product2/p2_sample8.md @@ -3,8 +3,8 @@ title: Sample 8 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample8/ -map: true +permalink: p2_sample8 +complex_map: true map_name: usermapcomplex box_number: 1 toc: false @@ -26,3 +26,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/product2/p2_sample9.md b/_pages/product2/p2_sample9.md similarity index 97% rename from product2/p2_sample9.md rename to _pages/product2/p2_sample9.md index 2f9c7b5..eec691c 100644 --- a/product2/p2_sample9.md +++ b/_pages/product2/p2_sample9.md @@ -3,8 +3,8 @@ title: Sample 9 Topic keywords: sample summary: "This is just a sample topic..." sidebar: product2_sidebar -permalink: /p2_sample9/ -map: true +permalink: p2_sample9 +complex_map: true map_name: usermapcomplex box_number: 2 toc: false @@ -27,3 +27,5 @@ Contrary to popular belief, Lorem Ipsum is not simply random text. It has roots The standard chunk of Lorem Ipsum used since the 1500s is reproduced below for those interested. Sections 1.10.32 and 1.10.33 from "de Finibus Bonorum et Malorum" by Cicero are also reproduced in their exact original form, accompanied by English versions from the 1914 translation by H. Rackham. There are many variations of passages of Lorem Ipsum available, but the majority have suffered alteration in some form, by injected humour, or randomised words which don't look even slightly believable. If you are going to use a passage of Lorem Ipsum, you need to be sure there isn't anything embarrassing hidden in the middle of text. All the Lorem Ipsum generators on the Internet tend to repeat predefined chunks as necessary, making this the first true generator on the Internet. It uses a dictionary of over 200 Latin words, combined with a handful of model sentence structures, to generate Lorem Ipsum which looks reasonable. The generated Lorem Ipsum is therefore always free from repetition, injected humour, or non-characteristic words etc. + +{% include links.html %} diff --git a/tags/tag_collaboration.html b/_pages/tags/tag_collaboration.html similarity index 71% rename from tags/tag_collaboration.html rename to _pages/tags/tag_collaboration.html index 8ccbe61..9b10ae1 100644 --- a/tags/tag_collaboration.html +++ b/_pages/tags/tag_collaboration.html @@ -2,8 +2,10 @@ title: "Collaboration pages" tagName: collaboration search: exclude -permalink: /tag_collaboration/ +permalink: tag_collaboration sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_content_types.html b/_pages/tags/tag_content_types.html similarity index 71% rename from tags/tag_content_types.html rename to _pages/tags/tag_content_types.html index a5437e1..112b178 100644 --- a/tags/tag_content_types.html +++ b/_pages/tags/tag_content_types.html @@ -2,8 +2,10 @@ title: "Content types pages" tagName: content_types search: exclude -permalink: /tag_content_types/ +permalink: tag_content_types sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_formatting.html b/_pages/tags/tag_formatting.html similarity index 71% rename from tags/tag_formatting.html rename to _pages/tags/tag_formatting.html index c5ef9e6..9957bdc 100644 --- a/tags/tag_formatting.html +++ b/_pages/tags/tag_formatting.html @@ -2,8 +2,10 @@ title: "Formatting pages" tagName: formatting search: exclude -permalink: /tag_formatting/ +permalink: tag_formatting sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_getting_started.html b/_pages/tags/tag_getting_started.html similarity index 71% rename from tags/tag_getting_started.html rename to _pages/tags/tag_getting_started.html index ade764c..e0c220f 100644 --- a/tags/tag_getting_started.html +++ b/_pages/tags/tag_getting_started.html @@ -2,8 +2,10 @@ title: "Getting started pages" tagName: getting_started search: exclude -permalink: /tag_getting_started/ +permalink: tag_getting_started sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_mobile.html b/_pages/tags/tag_mobile.html similarity index 75% rename from tags/tag_mobile.html rename to _pages/tags/tag_mobile.html index 6522952..049759c 100644 --- a/tags/tag_mobile.html +++ b/_pages/tags/tag_mobile.html @@ -2,9 +2,11 @@ title: "Mobile Pages" search: exclude tagName: mobile -permalink: /tag_mobile/ +permalink: tag_mobile sidebar: tags_sidebar sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_navigation.html b/_pages/tags/tag_navigation.html similarity index 71% rename from tags/tag_navigation.html rename to _pages/tags/tag_navigation.html index e367eeb..13277fa 100644 --- a/tags/tag_navigation.html +++ b/_pages/tags/tag_navigation.html @@ -2,8 +2,10 @@ title: "Navigation pages" tagName: navigation search: exclude -permalink: /tag_navigation/ +permalink: tag_navigation sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_news.html b/_pages/tags/tag_news.html similarity index 71% rename from tags/tag_news.html rename to _pages/tags/tag_news.html index e77c134..32db9ad 100644 --- a/tags/tag_news.html +++ b/_pages/tags/tag_news.html @@ -2,8 +2,10 @@ title: "News" tagName: news search: exclude -permalink: /tag_news/ +permalink: tag_news sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_publishing.html b/_pages/tags/tag_publishing.html similarity index 71% rename from tags/tag_publishing.html rename to _pages/tags/tag_publishing.html index 1fe113d..2234b96 100644 --- a/tags/tag_publishing.html +++ b/_pages/tags/tag_publishing.html @@ -2,8 +2,10 @@ title: "Publishing pages" tagName: publishing search: exclude -permalink: /tag_publishing/ +permalink: tag_publishing sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_single_sourcing.html b/_pages/tags/tag_single_sourcing.html similarity index 71% rename from tags/tag_single_sourcing.html rename to _pages/tags/tag_single_sourcing.html index 9d3cfe5..ae73507 100644 --- a/tags/tag_single_sourcing.html +++ b/_pages/tags/tag_single_sourcing.html @@ -2,8 +2,10 @@ title: "Single sourcing pages" tagName: single_sourcing search: exclude -permalink: /tag_single_sourcing/ +permalink: tag_single_sourcing sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_special_layouts.html b/_pages/tags/tag_special_layouts.html similarity index 71% rename from tags/tag_special_layouts.html rename to _pages/tags/tag_special_layouts.html index f676878..afae74c 100644 --- a/tags/tag_special_layouts.html +++ b/_pages/tags/tag_special_layouts.html @@ -2,8 +2,11 @@ title: "Special layout pages" tagName: special_layouts search: exclude -permalink: /tag_special_layouts/ +permalink: tag_special_layouts sidebar: tags_sidebar folder: tags --- + {% include taglogic.html %} + +{% include links.html %} diff --git a/tags/tag_troubleshooting.html b/_pages/tags/tag_troubleshooting.html similarity index 71% rename from tags/tag_troubleshooting.html rename to _pages/tags/tag_troubleshooting.html index d4f164c..9f6456a 100644 --- a/tags/tag_troubleshooting.html +++ b/_pages/tags/tag_troubleshooting.html @@ -2,8 +2,10 @@ title: "Troubleshooting pages" tagName: troubleshooting search: exclude -permalink: /tag_troubleshooting/ +permalink: tag_troubleshooting sidebar: tags_sidebar folder: tags --- {% include taglogic.html %} + +{% include links.html %} diff --git a/_posts/2015-04-12-test-post-last-year.md b/_posts/2015-04-12-test-post-last-year.md index 5f5e994..8462ae2 100644 --- a/_posts/2015-04-12-test-post-last-year.md +++ b/_posts/2015-04-12-test-post-last-year.md @@ -1,8 +1,10 @@ --- title: "Test post from last year" categories: jekyll update -permalink: /test-post-from-last-year/ +permalink: test-post-from-last-year/ tags: [news] --- -This is just a test post from the previous year. +This is just a test post from the previous year. + +{% include links.html %} diff --git a/_posts/2016-02-24-first-post.md b/_posts/2016-02-24-first-post.md index 1817ecb..025230f 100644 --- a/_posts/2016-02-24-first-post.md +++ b/_posts/2016-02-24-first-post.md @@ -1,7 +1,7 @@ --- title: "Welcome to Jekyll!" categories: jekyll update -permalink: /myupdate/ +permalink: myupdate/ tags: [news] --- @@ -14,4 +14,6 @@ Theme updates: - removed PDF output - removed some of the alternative layouts - added blog feature -- sidebars configurable per page \ No newline at end of file +- sidebars configurable per page + +{% include links.html %} diff --git a/_posts/2016-02-26-sample-post-jekyll.md b/_posts/2016-02-26-sample-post-jekyll.md index 1e2a8d8..d9d8975 100644 --- a/_posts/2016-02-26-sample-post-jekyll.md +++ b/_posts/2016-02-26-sample-post-jekyll.md @@ -1,7 +1,7 @@ --- title: "Sample post" published: true -permalink: /samplepost/ +permalink: samplepost/ summary: "This is some summary frontmatter for my sample post." tags: [news, getting_started] --- @@ -9,8 +9,9 @@ tags: [news, getting_started] Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries ## Heading - + but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries +{% include links.html %} diff --git a/images/androidsdkmanagericon.png b/images/androidsdkmanagericon.png new file mode 100644 index 0000000..65014a2 Binary files /dev/null and b/images/androidsdkmanagericon.png differ diff --git a/index.md b/index.md index d3b5732..bcdc923 100644 --- a/index.md +++ b/index.md @@ -1,20 +1,18 @@ --- -title: Getting started overview +title: Getting started with the Documentation Theme for Jekyll +keywords: sample homepage tags: [getting_started] sidebar: mydoc_sidebar -type: homepage +permalink: index +summary: These brief instructions will help you get started quickly with the theme. The other topics in this help provide additional information and detail about working with other aspects of this theme and Jekyll. --- -## Overview - -These brief instructions will help you get started quickly with the theme. The other topics in this help provide additional information and detail about working with other aspects of this theme and Jekyll. - ## Build this theme If you're used to running Jekyll sites, you can type the normal jekyll command, `jekyll serve`, to build the Jekyll theme. However, if you're a new Jekyll user or if you run into issues, see the following two topics: -* {{site.data.urls.mydoc_install_jekyll_on_mac.link}} -* {{site.data.urls.mydoc_install_jekyll_on_windows.link}} +* [Install Jekyll on Mac][mydoc_install_jekyll_on_mac] +* [Install Jekyll on Windows][mydoc_install_jekyll_on_windows] ## Customize the Gemfile @@ -73,9 +71,6 @@ The sidebarconfigs.html file uses simple `if elsif` logic to set a variable that {% elsif page.sidebar == "mydoc_sidebar" %} {% assign sidebar = site.data.sidebars.mydoc_sidebar.entries %} -{% elsif page.sidebar == "tags_sidebar" %} -{% assign sidebar = site.data.sidebars.tags_sidebar.entries %} - {% else %} {% assign sidebar = site.data.sidebars.home_sidebar.entries %} {% endif %} @@ -89,86 +84,110 @@ In each page's frontmatter, you must specify the sidebar you want that page to u title: Alerts tags: [formatting] keywords: notes, tips, cautions, warnings, admonitions -last_updated: March 20, 2016 +last_updated: July 3, 2016 summary: "You can insert notes, tips, warnings, and important alerts in your content. These notes are stored as shortcodes made available through the linksrefs.hmtl include." sidebar: mydoc_sidebar -permalink: /mydoc_alerts/ +permalink: mydoc_alerts --- ``` -The `sidebar: mydoc_sidebar` refers to the \_data/sidebars/mydoc_sidebar.yml file. +The `sidebar: mydoc_sidebar` refers to the \_data/sidebars/mydoc_sidebar.yml file (meaning, the mydoc_sidebar.yml file inside the sidebars subfolder inside the \data folder). If no sidebar assignment is found in the page frontmatter, the default sidebar (specified by the `else` statement) will be shown: `site.data.sidebars.home_sidebar.entries`. Note that your sidebar can only have 2 levels. Given that each product has its own sidebar, this depth should be sufficient (it's really like 3 levels). Deeper nesting goes against usability recommendations. -For more detail on the sidebar, see {{site.data.urls.mydoc_sidebar_navigation.link}}. +Additionally, each level must have at least one topic before the next level starts. You can't have a second level that contains multiple third levels without having at least one standalone topic in the second level. + +For more detail on the sidebar, see [Sidebar navigation][mydoc_sidebar_navigation]. ## Sidebar syntax -The sidebar data file uses a specific YAML syntax that you must follow. Follow the sample pattern shown. For example: +The sidebar data file uses a specific YAML syntax that you must follow. Follow the sample pattern shown in the theme. For example: ```yaml entries: - title: sidebar product: Jekyll Doc Theme - version: 5.0 + version: 6.0 folders: + - title: Overview output: web, pdf folderitems: - - title: Some page - url: /some-doc-page/ - output: web, pdf - - title: Another page - url: /another-doc-page/ + + - title: Get started + url: /index output: web, pdf - - title: Configuration - output: web - folderitems: - - title: How to configure the system - url: /configure-system/ + - title: Introduction + url: /mydoc_introduction output: web, pdf - subfolders: - - title: Config process - output: web, pdf - subfolderitems: - - title: Creating the config file - url: /config-file-how-to/ - output: web, pdf + + - title: Supported features + url: /mydoc_supported_features + output: web, pdf + + - title: About the theme author + url: /mydoc_about + output: web, pdf + + - title: Support + url: /mydoc_support + output: web, pdf + + - title: Release Notes + output: web, pdf + folderitems: + + - title: 6.0 Release notes + url: /mydoc_release_notes_60 + output: web, pdf + + - title: 5.0 Release notes + url: /mydoc_release_notes_50 + output: web, pdf + ``` -Each folder or subfolder must contain a title and output property. Each `folderitem` or `subfolderitem` must contain a `title`, `url`, and `output` property. +Each `folder` or `subfolder` must contain a `title` and `output` property. Each `folderitem` or `subfolderitem` must contain a `title`, `url`, and `output` property. -The two outputs available are `web` and `pd`f. (Even if you aren't publishing PDF, you still need to specify `output: web`). +The two outputs available are `web` and `pdf`. (Even if you aren't publishing PDF, you still need to specify `output: web`). The YAML syntax depends on exact spacing, so make sure you follow the pattern shown in the sample sidebars. See my [YAML tutorial](mydoc_yaml_tutorial) for more details about how YAML works. To accommodate the title page and table of contents in PDF outputs, each product sidebar must list these pages before any other: ```yaml +- title: + output: pdf + type: frontmatter + folderitems: - title: + url: /titlepage + output: pdf + type: frontmatter + - title: + url: /tocpage output: pdf type: frontmatter - folderitems: - - title: - url: /titlepage/ - output: pdf - type: frontmatter - - title: - url: /tocpage/ - output: pdf - type: frontmatter ``` Leave the output as `output: pdf` for these frontmatter pages so that they don't appear in the web output. -For more detail on the sidebar, see {{site.data.urls.mydoc_sidebar_navigation.link}} and {{site.data.urls.mydoc_yaml_tutorial.link}}. +For more detail on the sidebar, see [Sidebar navigation][mydoc_sidebar_navigation] and [YAML tutorial][mydoc_yaml_tutorial]. + +## Relative links and offline viewing + +This theme uses relative links throughout so that you can view the site offline and not worry about which server or directory you're hosting it. It's common with tech docs to push content to an internal server for review prior to pushing the content to an external server for publication. Because of the need for seamless transferrence from one host to another, the site has to use relative links. + +To view pages locally on your machine, they need to have the `.html` extension. However, if you prefer not to have this extension, you can simply remove the `.html` from the sidebar entries, and the pages will still work when you view content on a preview server or web server. + +The `permalink` property in the page's frontmatter combined with the `include: ['pages']` property in the configuration file is what pushes the files into the root directory when the site builds. ## Page frontmatter -When you write pages, include these same frontmatter keys with each page: +When you write pages, include these same frontmatter properties with each page: ```yaml --- @@ -178,48 +197,49 @@ keywords: keyword1, keyword2, keyword3 last_updated: Month day, year summary: "optional summary here" sidebar: sidebar name -permalink: /yoururl/ +permalink: filename --- ``` -(You will customize the values for each of these keys, of course.) - -If you're using [Webstorm]({{site.data.urls.mydoc_webstorm_text_editor.url}}), you can set up a template to auto-populate this code when you create a new file. +(You will customize the values for each of these properties, of course.) For titles, surrounding the title in quotes is optional, but if you have a colon in the title, you must surround the title with quotation marks. If you have a quotation mark within the title, escape it first with a backlash `\`. Values for `keywords` get populated into the metadata of the page for SEO. Values for `tags` must be defined in your \_data/tags.yml list. You also need a corresponding tag file inside the tags folder that follows the same pattern as the other tag files shown in the tags folder. (Jekyll wont auto-create these tag files.) -``` If you don't want the mini-TOC to show on a page (such as for the homepage or landing pages), add `toc: false` in the frontmatter. -For more detail, see {{site.data.urls.mydoc_pages.link}}. +The `permalink` value should be the same as your filename but without the file extension. + +For more detail, see [Pages][mydoc_pages]. ## Where to store your documentation topics -Store your files for each product inside subfolders following the pattern shown in the theme. For example, product1, product2, etc. You can store your topics inside sub-subfolders or sub-sub-folders to your heart's content. When Jekyll builds your site, it will pull the topics into the root directory and use the permalink for the URL. +You can store your files for each product inside subfolders following the pattern shown in the theme. For example, product1, product2, etc, can be stored in their own subfolders inside the \_pages directory. Inside \_pages, you can store your topics inside sub-subfolders or sub-sub-folders to your heart's content. When Jekyll builds your site, it will pull the topics into the root directory and use the permalink for the URL. Note that product1, product2, and mydoc are all just sample content to demonstrate how to add multiple products into the theme. You can freely delete that content. -For more information, see {{site.data.urls.mydoc_pages.link}} and {{site.data.urls.mydoc_posts.link}}. +For more information, see [Pages][mydoc_pages] and [Posts][mydoc_posts]. ## Configure the top navigation -The top navigation bar's menu items are set through the _data/topnav.yml file. Use the top navigation bar to provide links for navigating from one product to another, or to navigate to external resources. +The top navigation bar's menu items are set through the \_data/topnav.yml file. Use the top navigation bar to provide links for navigating from one product to another, or to navigate to external resources. For external URLs, use `external_url` in the item property, as shown in the example topnav.yml file. For internal links, use `url` as usual. -Note that the topnav has two sections: topnav and topnav_dropdowns. The topnav section contains single links, while the topnav_dropdowns section contains dropdown menus. The two sections are independent of each other. +Note that the topnav has two sections: `topnav` and `topnav_dropdowns`. The topnav section contains single links, while the `topnav_dropdowns` section contains dropdown menus. The two sections are independent of each other. ## Generating PDF -If you want to generate PDF, you'll need a license for [Prince XML](http://www.princexml.com/). You will also need to [install Prince](http://www.princexml.com/doc/installing/). You can generate PDFs by product (but not for every product on the site combined together into one massive PDF). Prince will work even without a license, but it will imprint a small Prince image on the first page. +If you want to generate PDF, you'll need a license for [Prince XML](http://www.princexml.com/). You will also need to [install Prince](http://www.princexml.com/doc/installing/). You can generate PDFs by product (but not for every product on the site combined together into one massive PDF). Prince will work even without a license, but it will imprint a small Prince image on the first page, and you're supposed to buy the license to use it. + +If you're on Windows, install [Git Bash client](https://git-for-windows.github.io/) rather than using the default Windows command prompt. Open up the css/printstyles.css file and customize the email address (`youremail@domain.com`) that is listed there. This email address appears in the bottom left footer of the PDF output. You'll also need to create a PDF configuration file following the examples shown in the pdfconfigs folder, and also customize some build scripts following the same pattern shown in the root: pdf-product1.sh -See the section on {{site.data.urls.mydoc_generating_pdfs.link}} for more details about setting the theme up for this output. +See the section on [Generating PDFs][mydoc_generating_pdfs] for more details about setting the theme up for this output. ## Blogs / News @@ -227,11 +247,11 @@ For blog posts, create your markdown files in the \_posts folder following the s The news/news.html file displays the posts, and the news_archive.html file shows a yearly history of posts. In documentation, you might use the news to highlight product features outside of your documentation, or to provide release notes and other updates. -See {{site.data.urls.mydoc_posts.link}} for more information. +See [Posts][mydoc_posts] for more information. ## Markdown -This theme uses Kramdown markdown. Kramdown is similar to Github-flavored Markdown, except that when you have text that intercepts list items, the spacing of the intercepting text must align with the spacing of the first character after the space of a numbered list item. Basically, with your list item numbering, use two spaces after the dot in the number, like this: +This theme uses [kramdown markdown](http://kramdown.gettalong.org/). kramdown is similar to Github-flavored Markdown, except that when you have text that intercepts list items, the spacing of the intercepting text must align with the spacing of the first character after the space of a numbered list item. Basically, with your list item numbering, use two spaces after the dot in the number, like this: ``` 1. First item @@ -239,7 +259,7 @@ This theme uses Kramdown markdown. Kramdown is similar to Github-flavored Markdo 3. Third item ``` -When you want to insert paragraphs, notes, code snippets, or other matter in between the list items, use four spaces to indent. The four spaces will line up with the first letter of the list item (the **F**irst or **S**econd or **T**hird). +When you want to insert paragraphs, notes, code snippets, or other matter in between the list items, use four spaces to indent. The four spaces will line up with the first letter of the list item (the First or Second or Third). ``` 1. First item @@ -255,13 +275,14 @@ When you want to insert paragraphs, notes, code snippets, or other matter in bet 3. Third item ``` - See the topics under "Formatting" in the sidebar for more information. -## Managing links +## Automated links -If you want to use a simple system for managing links, see the "Managed Links" section in {{site.data.urls.mydoc_hyperlinks.link | append: "#managed-links"}}. +If you want to use an automated system for managing links, see [Automated Links][mydoc_hyperlinks-automatedlinks]. This approach automatically creates a list of Markdown references to simplify linking. ## Other instructions -For other details in working with the theme, see the various sections in the sidebar. +The content here is just a getting started guide only. For other details in working with the theme, see the various sections in the sidebar. + +{% include links.html %} diff --git a/LICENSE b/licenses/LICENSE similarity index 100% rename from LICENSE rename to licenses/LICENSE diff --git a/licenses/LICENSE-BSD-NAVGOCO.txt b/licenses/LICENSE-BSD-NAVGOCO.txt index 707ee1e..7fdefc3 100644 --- a/licenses/LICENSE-BSD-NAVGOCO.txt +++ b/licenses/LICENSE-BSD-NAVGOCO.txt @@ -1,3 +1,5 @@ +/* This license pertains to the Navgoco jQuery component used for the sidebar. */ + Copyright (c) 2013, Christodoulos Tsoulloftas, http://www.komposta.net All rights reserved. diff --git a/licenses/LICENSE.txt b/licenses/LICENSE.txt deleted file mode 100644 index 4e871b6..0000000 --- a/licenses/LICENSE.txt +++ /dev/null @@ -1,21 +0,0 @@ -The MIT License (MIT) - -Copyright (c) 2014 Tom Johnson - -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all -copies or substantial portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. \ No newline at end of file diff --git a/mydoc/mydoc_hyperlinks.md b/mydoc/mydoc_hyperlinks.md deleted file mode 100644 index 34cc497..0000000 --- a/mydoc/mydoc_hyperlinks.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -title: Links -audience: writer, designer -tags: [formatting, navigation] -keywords: links, hyperlinks, cross references, related links, relationship tables -summary: "When creating links, you can use standard HTML or Markdown formatting. Note that this approach is susceptible to errors and broken links, so check your outputs for broken links." -last_updated: March 20, 2016 -sidebar: mydoc_sidebar -permalink: /mydoc_hyperlinks/ -folder: mydoc ---- - -## Create an external link - -When linking to an external site, use Markdown formatting because it's simplest: - -``` -[Google](http://google.com) -``` - -If you need to use HTML, use the normal syntax: - -```html -Google -``` - -## Linking to internal pages - -When linking to internal pages, you can use this same syntax: - -``` -[Sample]({{ "/permalink" | prepend: site.baseurl }}) -``` - -OR - -```html -page -``` - -## Managed Links - -You can also adopt an indirect-reference systems for managing links. This "managed links" approach involves storing the link text in YAML syntax. - -Look at the urls.txt file in the root directory. The urls.txt file contains more or less the same code as the table of contents (but without the conditional qualifiers). A `for` loop runs each of the product sidebars listed in the frontmatter through the url generator. - -The code iterates through every page listed in the table of contents sidebars (as well as the top navigation menus) and creates an output that looks like this for each link: - -```yaml -mydoc_introduction: - title: "Introduction" - url: "mydoc_introduction" - link: "Introduction" -``` - -In the frontmatter for urls.txt, add the name of each of your sidebars, like this: - -```yaml ---- -layout: none -search: exclude -sidebar: -- mydoc_sidebar -- product1_sidebar -- product2_sidebar ---- -``` - -From the site output folder (in \_site), open urls.txt and observe that it is properly populated (blank spaces between entries doesn't matter). Then either manually copy the contents from the urls.txt and insert it into the \_data/urls.yml file in your project folder. Or just run the urls-update.sh file: - -``` -. urls-update.sh -``` - -This will move and rename the file through a script. - -Because the urls.txt is produced from the table of contents, you ensure that the same titles and URLs used in your table of contents and top navigation will also be used in your inline links. - -To create a link in a topic, just reference the appropriate value in the urls.yml file, like this: - -{% raw %} -```html -{{site.data.urls.mydoc_introduction.link}} -``` -{% endraw %} - -This will insert the following into your topic: - -```html -Getting started -``` - -You don't need to worry whether you can use Markdown syntax when inserting a link this way, because the code that gets inserted is HTML. - -To insert a link in the context of a phrase, you can use this syntax: - -{% raw %} -```html -After downloading the theme, you can [get started in building the theme]({{site.data.urls.mydoc_getting_started.url}}). -``` -{% endraw %} - -Note that `.url` is used instead of `.link` when using customized text links like this. - -If you're in HTML and can't use Markdown, then use the following code: - -{% raw %} -```html -After downloading the theme, you can get started in building the theme.
-``` -{% endraw %} - -The `url` value accesses the URL for the page only, whereas `link` gets the title and url in a link format. - -You shouldn't have to transfer the contents from the urls.txt file into your YAML data source too often — only when you're creating new pages. - -I also added a simple script called "run.sh" that performs the urls-update.sh command prior to running Jekyll serve, so you can kill two birds with one stone. - -Note that for the index.html file, which doesn't have a permalink, this file is not included in the urls.txt generation. The frontmatter in the index.md file (`type: homepage`) triggers an exclusion from urls.txt because the empty name makes the yaml file invalid. To link to the homepage, just refer users to the root url of your site {% raw %}(`{{site.url}}` or `{{site.url}}{{site.baseurl}}`{% endraw %}). - -Overall, by using managed links, you're less likely to end up with broken links. - -## Bookmark links to sections on other pages - -Suppose you want to link to a specific section on another page. First make sure you name the section title with something table. Although Kramdown automatically adds ID tags to heading elements, if you change the heading title, the ID will likewise change. Therefore it's best to manually specify the section titles you plan to link to. - -Here's how you specify an ID for a heading in Kramdown: - -``` -## My heading {#myheading} -``` - -Link to it using this syntax: - -``` -{%raw%}[{{site.data.urls.your-page-permalink.title}}]({{site.data.urls.your-page-permalink.url | append: "#myheading"}}){%endraw%} -``` - -Or using HTML: - -``` -{%raw%}{{site.data.urls.your-page-permalink.title}}{%endraw%} -``` - -Granted, this is somewhat long, but it's the only way to continue to leverage the automated links from urls.yaml. You want to avoid manually referencing links since they are much more prone to break when you specify them that way. - -However, I'm not too worried about this lengthy syntax because I think linking to sections on pages is somewhat fragile anyway. When you're editing sections, you generally don't know what URLs you have pointing to that section. The custom ID tag on that section is the best reminder that you are linking to the section. - -## Bookmark links to sections on the same page - -If you're just linking to a section on the same page, the syntax is simple: - -``` -[My heading](#myheading) -``` - -## How to tell what links point to a page - -There's no automated way to tell what links you have pointing to a page. This is one of the shortcomings of static site generators. The only way is to search your project for the page title. This is simple in Webstorm (Cmd + Shift + F), and it's one of the reasons I like Webstorm. - -If you change a page title, you generally want to search in your project and update all references to the page to the new page name. You can do this easily through the Global Replace command (Cmd + Shift + R). - - -## Always make sure your TOC page is accurate - -You should treat your sidebar data files (in /_data/sidebars) with a lot of care. Every time you add a page to your site, make sure it's listed in your sidebar file (or in your top navigation). If you don't have pages listed in your sidebar file, they won't be included in the urls.txt file, and as your site grows, it will be harder to recognize pages that are absent from the TOC. - -Because all the pages are stored in the root directory, the list of files can grow really long. I typically find pages by navigating to the page in the preview server, copying the page name (e.g., mydoc_hyperlinks), and then pressing **Shift + Shift** in WebStorm to locate the page. - -This is the only sane way to locate your pages when you have hundreds of pages in your root directory. If the page isn't listed in your TOC, it will be difficult to navigate to it and find it. - -## Checking for broken links - -One way to ensure you don't have any broken links in your output is to [generate a PDF]({{site.data.urls.mydoc_generating_pdfs.url}}). When you generate a PDF, look for the following two problems in the output: - -* page 0 -* see . - -Both instances indicate a broken link. The "page 0" indicates that Prince XML couldn't find the page that the link points to, and so it can't create a cross reference. This may be because the page doesn't exist, or because the anchor is pointing to a missing location. - -If you see "see ." it means that the reference (for example, {% raw %}`{{mylink...}}`{% endraw %} doesn't actually refer to anything. As a result, it's simply blank in the output. - -{{site.data.alerts.note}} To keep Prince XML from trying to insert a cross reference into a link, addclass="noCrossRef"
to the link. {{site.data.alerts.end}} - -## Avoiding broken links - -In general, avoid broken links and outdated titles in links by doing the following: - -* Where possible, avoid using the exact titles in link names. For example, if you write, see the Links page, this title is likely to become more outdated than if you were to write, learn how to manage links. -* Use a broken link checker on your site output to see if links are broken. -* Generate a PDF, since the PDF tends to highlight broken links more forcefully. diff --git a/mydoc/mydoc_multibuild_pdf.sh b/mydoc/mydoc_multibuild_pdf.sh deleted file mode 100644 index ce64ca3..0000000 --- a/mydoc/mydoc_multibuild_pdf.sh +++ /dev/null @@ -1,10 +0,0 @@ -# Writers PDF -echo "Building the Writers PDF..." -prince --javascript --input-list=../mydoc_writers-pdf/prince-file-list.txt -o /Users/tjohnson/projects/documentation-theme-jekyll/mydoc_writers_pdf.pdf; - -# Designers PDF -echo "Building the Designers PDF ..." -prince --javascript --input-list=../mydoc_designers-pdf/prince-file-list.txt -o /Users/tjohnson/projects/documentation-theme-jekyll/mydoc_designers_pdf.pdf; - -echo "All done." -echo "Now run . mydoc_multibuild_web.sh" diff --git a/mydoc/mydoc_multibuild_web.sh b/mydoc/mydoc_multibuild_web.sh deleted file mode 100644 index 1ca8a31..0000000 --- a/mydoc/mydoc_multibuild_web.sh +++ /dev/null @@ -1,23 +0,0 @@ -kill -9 $(ps aux | grep '[j]ekyll' | awk '{print $2}') -clear - -# Writers -echo "Building Writers ..." -jekyll build --config configs/config_writers.yml -# jekyll serve --config configs/config_writers.yml -echo "done" - -# Designers -echo "Building Designers ..." -jekyll build --config configs/config_designers.yml -# jekyll serve --config configs/config_designers.yml -echo "done" - -echo "All finished building all the web outputs!!!" -echo "Now push the builds to the server." -echo "Run . mydoc_multiscp.sh" - -# All done. -# Now run . mydoc_multiscp.sh to push the build to your server. - - diff --git a/mydoc/mydoc_multiscp.sh b/mydoc/mydoc_multiscp.sh deleted file mode 100644 index e190c90..0000000 --- a/mydoc/mydoc_multiscp.sh +++ /dev/null @@ -1,3 +0,0 @@ -scp -r /Applications/XAMPP/xamppfiles/htdocs/documentation-theme-jekyll/writers name@domain:/var/www/html/documentation-theme-jekyll/writers -echo "All done." - diff --git a/mydoc/mydoc_multiserve_pdf.sh b/mydoc/mydoc_multiserve_pdf.sh deleted file mode 100644 index 3f76d03..0000000 --- a/mydoc/mydoc_multiserve_pdf.sh +++ /dev/null @@ -1,16 +0,0 @@ -echo 'Killing all Jekyll instances' -kill -9 $(ps aux | grep '[j]ekyll' | awk '{print $2}') -clear - -# serve all di print deliverables - -# Writers -echo "Serving Writers PDF" -jekyll serve --detach --config configs/config_writers.yml,configs/config_writers_pdf.yml - -# Designers -echo "Serving Designers PDF" -jekyll serve --detach --config configs/config_designers.yml,configs/config_designers_pdf.yml - -echo "All done." -echo "Now run . mydoc_multibuild_pdf.sh" diff --git a/mydoc/mydoc_title_checker.md b/mydoc/mydoc_title_checker.md deleted file mode 100644 index ab393ec..0000000 --- a/mydoc/mydoc_title_checker.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: Check page title consistency -tags: [navigation] -keywords: "validation, titles, page titles, inconsistency, errors" -last_updated: "November 30, 2016" -summary: "The title checker page helps ensure that the titles in your pages match the titles in your TOC." -sidebar: mydoc_sidebar -permalink: /mydoc_title_checker/ -folder: mydoc ---- - -The theme has a file called title-checker.html. This file will iterate through all the pages listed in the sidebar navigation and top navigation, and compare the navigation titles against the page titles based on matching URLs. If there are inconsistencies in the titles, they get noted on the title-checker.html page. - -To run the link checker, just build or serve your project, and go to /title-checker in your browser (such as Chrome). If there are inconsistencies, they will be noted on the page. - -Note that in order for the title-checker file to run correctly, it has to detect a match between the URL listed in the sidebar or top navigation with the URL for the page (based on the file name). If you have the wrong URL, it won’t tell you if the page titles match. Therefore you should always click through all the topics in your navigation to make sure the URLs are accurate. - -{{site.data.alerts.note}} If your page titles have your product name in parentheses, but your sidebar doesn't have the product name in parentheses, this title-checker tool is going to return a lot of mismatches. This is one limitation of the code right now. {{site.data.alerts.end}} - -Note also that you must manually configure your sidebar file in the first line of the code, and then repeat the same chunk of code for each sidebar. Right now the code doesn't automatically iterate over every sidebar file. It's somewhat of a manual configuration process there. diff --git a/pdf-mydoc.sh b/pdf-mydoc.sh index 8a94ff6..739e317 100644 --- a/pdf-mydoc.sh +++ b/pdf-mydoc.sh @@ -1,3 +1,5 @@ +# Note that .sh scripts work only on Mac. If you're on Windows, install Git Bash and use that as your client. + echo 'Killing all Jekyll instances' kill -9 $(ps aux | grep '[j]ekyll' | awk '{print $2}') clear diff --git a/pdf/mydoc.pdf b/pdf/mydoc.pdf index a885a6c..4c33d7d 100644 --- a/pdf/mydoc.pdf +++ b/pdf/mydoc.pdf @@ -4,2231 +4,2183 @@ 1 0 obj <> +/Outlines 184 0 R>> endobj -172 0 obj +185 0 obj <> +/Next 186 0 R>> endobj -173 0 obj +186 0 obj <> +/Prev 185 0 R +/Next 187 0 R>> endobj -174 0 obj +187 0 obj <> -endobj - -218 0 obj -<> -endobj - -219 0 obj -<> -endobj - -220 0 obj -<> -endobj - -221 0 obj -<> -endobj - -222 0 obj -<> -endobj - -223 0 obj -<> -endobj - -224 0 obj -<> -endobj - -225 0 obj -<> -endobj - -226 0 obj -<> -endobj - -227 0 obj -<> -endobj - -228 0 obj -<> -endobj - -229 0 obj -<> -endobj - -175 0 obj -<> +/Prev 186 0 R +/Next 188 0 R>> endobj 230 0 obj -<> endobj 231 0 obj -<> endobj 232 0 obj -<> endobj 233 0 obj -<> endobj 234 0 obj -<> endobj 235 0 obj -<> endobj 236 0 obj -<> -endobj - -176 0 obj -<> +<> endobj 237 0 obj -<> endobj 238 0 obj -<> endobj 239 0 obj -<> -endobj - -177 0 obj -<> +<> endobj 240 0 obj -<> endobj 241 0 obj -<> endobj -178 0 obj -<> -endobj - -179 0 obj -<> -endobj - -180 0 obj -<> +/Count 12>> endobj 242 0 obj -<> endobj 243 0 obj -<> endobj 244 0 obj -<> endobj 245 0 obj -<> endobj 246 0 obj -<> -endobj - -181 0 obj -<> +<> endobj 247 0 obj -<> endobj 248 0 obj -<> +<> +endobj + +189 0 obj +<> endobj 249 0 obj -<> endobj 250 0 obj -<> endobj -251 0 obj -<> +258 0 obj +<> endobj -182 0 obj -<> +251 0 obj +<> endobj 252 0 obj -<> endobj 253 0 obj -<> endobj 254 0 obj -<> endobj 255 0 obj -<> endobj 256 0 obj -<> -endobj - -183 0 obj -<> +<> endobj 257 0 obj -<> +<> endobj -258 0 obj -<> +/Dest [17 0 R /XYZ 0 725 0] +/Prev 189 0 R +/Next 191 0 R +/First 249 0 R +/Last 257 0 R +/Count 9>> endobj 259 0 obj -<> endobj 260 0 obj -<> endobj 261 0 obj -<> +endobj + +191 0 obj +<> +/Dest [34 0 R /XYZ 0 725 0] +/Prev 190 0 R +/Next 192 0 R +/First 259 0 R +/Last 261 0 R +/Count 3>> endobj 262 0 obj -<> endobj 263 0 obj -<> endobj -184 0 obj -<> +/Count 2>> +endobj + +193 0 obj +<> +endobj + +194 0 obj +<> endobj 264 0 obj -<> endobj 265 0 obj -<> -endobj - -185 0 obj -<> +<> endobj 266 0 obj -<> endobj 267 0 obj -<> endobj 268 0 obj -<> +<> +endobj + +195 0 obj +<> endobj 269 0 obj -<> endobj 270 0 obj -<> endobj 271 0 obj -<> endobj 272 0 obj -<> endobj 273 0 obj -<> endobj 274 0 obj -<> +<> +endobj + +196 0 obj +<> endobj 275 0 obj -<> endobj 276 0 obj -<> endobj 277 0 obj -<> -endobj - -186 0 obj -<> +<> endobj 278 0 obj -<> endobj 279 0 obj -<> endobj 280 0 obj -<> +<> +endobj + +197 0 obj +<> endobj 281 0 obj -<> endobj 282 0 obj -<> endobj 283 0 obj -<> endobj 284 0 obj -<> endobj 285 0 obj -<> -endobj - -187 0 obj -<> +<> endobj 286 0 obj -<> endobj 287 0 obj -<> endobj -188 0 obj -<> +/Count 7>> endobj 288 0 obj -<> endobj 289 0 obj -<> +<> +endobj + +199 0 obj +<> endobj 290 0 obj -<> endobj 291 0 obj -<> endobj 292 0 obj -<> -endobj - -189 0 obj -<> +<> endobj 293 0 obj -<> endobj 294 0 obj -<> endobj 295 0 obj -<> endobj 296 0 obj -<> endobj 297 0 obj -<> endobj -190 0 obj -<> +/Count 8>> endobj 298 0 obj -<> endobj 299 0 obj -<> +<> +endobj + +201 0 obj +<> endobj 300 0 obj -<> endobj 301 0 obj -<> endobj 302 0 obj -<> endobj 303 0 obj -<> endobj -311 0 obj -<> -endobj - 304 0 obj -<> +<> endobj -312 0 obj -<> -endobj - -313 0 obj -<> -endobj - -314 0 obj -<> +202 0 obj +<> endobj 305 0 obj -<> +<> endobj 306 0 obj -<> endobj 307 0 obj -<> endobj 308 0 obj -<> endobj 309 0 obj -<> +<> +endobj + +203 0 obj +<> endobj 310 0 obj -<> +<> endobj -191 0 obj -<> +311 0 obj +<> +endobj + +312 0 obj +<> +endobj + +313 0 obj +<> +endobj + +314 0 obj +<> endobj 315 0 obj -<> endobj -316 0 obj -<> -endobj - -317 0 obj -<> -endobj - -318 0 obj -<> -endobj - -319 0 obj -<> -endobj - -320 0 obj -<> -endobj - -321 0 obj -<> -endobj - -192 0 obj -<> -endobj - -322 0 obj -<> -endobj - 323 0 obj -<> +<> +endobj + +316 0 obj +<> endobj 324 0 obj -< -/Parent 193 0 R -/Dest [79 0 R /XYZ 0 610 0] -/Prev 323 0 R +<> endobj 325 0 obj -<> endobj 326 0 obj -<> +<> +endobj + +317 0 obj +<> +endobj + +318 0 obj +<> +endobj + +319 0 obj +<> +endobj + +320 0 obj +<> +endobj + +321 0 obj +<> +endobj + +322 0 obj +<> +endobj + +204 0 obj +<> endobj 327 0 obj -<> endobj 328 0 obj -<> -endobj - -193 0 obj -<> +<> endobj 329 0 obj -<> -endobj - -194 0 obj -<> +<> endobj 330 0 obj -<> endobj 331 0 obj -<> endobj 332 0 obj -<> endobj 333 0 obj -<> +<> +endobj + +205 0 obj +<> endobj 334 0 obj -<> endobj 335 0 obj -<> endobj 336 0 obj -<> -endobj - -195 0 obj -<> +< +/Parent 206 0 R +/Dest [95 0 R /XYZ 0 610 0] +/Prev 335 0 R +/Next 337 0 R>> endobj 337 0 obj -<> endobj 338 0 obj -<> endobj 339 0 obj -<> endobj 340 0 obj -<> +<> +endobj + +206 0 obj +<> endobj 341 0 obj -<> +<> endobj -196 0 obj -<> +/Count 1>> endobj 342 0 obj -<> endobj 343 0 obj -<> -endobj - -197 0 obj -<> +<> endobj 344 0 obj -<> -endobj - -198 0 obj -<> +<> endobj 345 0 obj -<> endobj 346 0 obj -<> endobj 347 0 obj -<> endobj 348 0 obj -<> endobj 349 0 obj -<> +<> +endobj + +208 0 obj +<> endobj 350 0 obj -<> endobj 351 0 obj -<> endobj 352 0 obj -<> endobj 353 0 obj -<> -endobj - -199 0 obj -<> +<> endobj 354 0 obj -<> +<> +endobj + +209 0 obj +<> endobj 355 0 obj -<> endobj 356 0 obj -<> +<> +endobj + +210 0 obj +<> endobj 357 0 obj -<> +<> +endobj + +211 0 obj +<> endobj 358 0 obj -<> endobj 359 0 obj -<> endobj 360 0 obj -<> +<> +endobj + +212 0 obj +<> endobj 361 0 obj -<> endobj 362 0 obj -<> endobj 363 0 obj -<> endobj 364 0 obj -<> -endobj - -200 0 obj -<> +<> endobj 365 0 obj -<> endobj 366 0 obj -<> -endobj - -201 0 obj -<> +<> endobj 367 0 obj -<> endobj 368 0 obj -<> -endobj - -202 0 obj -<> +<> endobj 369 0 obj -<> endobj 370 0 obj -<> endobj 371 0 obj -<> +<> +endobj + +213 0 obj +<> endobj 372 0 obj -<> -endobj - -203 0 obj -<> +<> endobj 373 0 obj -<> +<> +endobj + +214 0 obj +<> endobj 374 0 obj -<> endobj 375 0 obj -<> endobj -204 0 obj -<> +/Count 2>> endobj 376 0 obj -<> endobj 377 0 obj -<> -endobj - -205 0 obj -<> -endobj - -206 0 obj -<> +<> endobj 378 0 obj -<> endobj 379 0 obj -<> +<> +endobj + +216 0 obj +<> endobj 380 0 obj -<> endobj 381 0 obj -<> endobj 382 0 obj -<> +<> +endobj + +217 0 obj +<> endobj 383 0 obj -<> endobj 384 0 obj -<> +<> +endobj + +218 0 obj +<> endobj 385 0 obj -<> endobj 386 0 obj -<> endobj 387 0 obj -<> endobj 388 0 obj -<> -endobj - -207 0 obj -<> +<> endobj 389 0 obj -<> endobj 390 0 obj -<> endobj 391 0 obj -< -/Parent 208 0 R -/Dest [136 0 R /XYZ 0 310 0] +<> endobj 392 0 obj -<> endobj 393 0 obj -<> endobj 394 0 obj -<> endobj 395 0 obj -<> +<> +endobj + +219 0 obj +<> endobj 396 0 obj -<> endobj 397 0 obj -<> endobj 398 0 obj -< +/Parent 220 0 R +/Dest [147 0 R /XYZ 0 310 0] /Prev 397 0 R /Next 399 0 R>> endobj 399 0 obj -<> -endobj - -208 0 obj -<> +<> endobj 400 0 obj -<> endobj 401 0 obj -<> endobj 402 0 obj -<> endobj 403 0 obj -<> endobj 404 0 obj -<> endobj 405 0 obj -<> -endobj - -209 0 obj -<> +<> endobj 406 0 obj -<> +<> +endobj + +220 0 obj +<> endobj 407 0 obj -<> endobj 408 0 obj -<> -endobj - -210 0 obj -<> +<> endobj 409 0 obj -<> endobj 410 0 obj -<> -endobj - -211 0 obj -<> +<> endobj 411 0 obj -<> -endobj - -212 0 obj -<> +<> endobj 412 0 obj -<> +<> +endobj + +221 0 obj +<> endobj 413 0 obj -<> endobj 414 0 obj -<> endobj 415 0 obj -<> endobj -213 0 obj -<> -endobj - -418 0 obj -<> -endobj - -419 0 obj -<> -endobj - -420 0 obj -<> -endobj - -421 0 obj -<> +/Count 3>> endobj 416 0 obj -<> +<> endobj 417 0 obj -<> endobj -214 0 obj -<> endobj -422 0 obj -<> +418 0 obj +<> endobj -215 0 obj -<> endobj -423 0 obj -<> +419 0 obj +<> endobj -424 0 obj -<> +420 0 obj +<> +endobj + +421 0 obj +<> +endobj + +422 0 obj +<> +endobj + +225 0 obj +<> endobj 425 0 obj -<> endobj 426 0 obj -<> endobj 427 0 obj -<> endobj 428 0 obj -<> +<> +endobj + +423 0 obj +<> +endobj + +424 0 obj +<> +endobj + +226 0 obj +<> endobj 429 0 obj -<> +<> +endobj + +227 0 obj +<> endobj 430 0 obj -<> endobj 431 0 obj -<> +<> endobj -216 0 obj -<> +432 0 obj +<> +endobj + +433 0 obj +<> endobj 434 0 obj -<> endobj 435 0 obj -<> -endobj - -432 0 obj -<> +<> endobj 436 0 obj -< -/Parent 433 0 R -/Dest [169 0 R /XYZ 0 665 0] +<> endobj 437 0 obj -<> endobj 438 0 obj -<> +<> +endobj + +228 0 obj +<> +endobj + +441 0 obj +<> +endobj + +442 0 obj +<> endobj 439 0 obj -< -/Parent 433 0 R -/Dest [169 0 R /XYZ 0 211 0] -/Prev 438 0 R -/Next 440 0 R>> -endobj - -440 0 obj -< -/Parent 433 0 R -/Dest [170 0 R /XYZ 0 732 0] -/Prev 439 0 R>> -endobj - -433 0 obj -<> -endobj - -217 0 obj -<> endobj -171 0 obj +443 0 obj +< +/Parent 440 0 R +/Dest [182 0 R /XYZ 0 665 0] +/Next 444 0 R>> +endobj + +444 0 obj +<> +endobj + +445 0 obj +<> +endobj + +446 0 obj +< +/Parent 440 0 R +/Dest [182 0 R /XYZ 0 211 0] +/Prev 445 0 R +/Next 447 0 R>> +endobj + +447 0 obj +< +/Parent 440 0 R +/Dest [183 0 R /XYZ 0 732 0] +/Prev 446 0 R>> +endobj + +440 0 obj +<> +endobj + +229 0 obj +<> +endobj + +184 0 obj <> +/First 185 0 R +/Last 229 0 R>> endobj 2 0 obj <> +/Kids [3 0 R 4 0 R 5 0 R 6 0 R 7 0 R 8 0 R 9 0 R 10 0 R 11 0 R 12 0 R 13 0 R 14 0 R 15 0 R 16 0 R 17 0 R 18 0 R 19 0 R 20 0 R 21 0 R 22 0 R 23 0 R 24 0 R 25 0 R 26 0 R 27 0 R 28 0 R 29 0 R 30 0 R 31 0 R 32 0 R 33 0 R 34 0 R 35 0 R 36 0 R 37 0 R 38 0 R 39 0 R 40 0 R 41 0 R 42 0 R 43 0 R 44 0 R 45 0 R 46 0 R 47 0 R 48 0 R 49 0 R 50 0 R 51 0 R 52 0 R 53 0 R 54 0 R 55 0 R 56 0 R 57 0 R 58 0 R 59 0 R 60 0 R 61 0 R 62 0 R 63 0 R 64 0 R 65 0 R 66 0 R 67 0 R 68 0 R 69 0 R 70 0 R 71 0 R 72 0 R 73 0 R 74 0 R 75 0 R 76 0 R 77 0 R 78 0 R 79 0 R 80 0 R 81 0 R 82 0 R 83 0 R 84 0 R 85 0 R 86 0 R 87 0 R 88 0 R 89 0 R 90 0 R 91 0 R 92 0 R 93 0 R 94 0 R 95 0 R 96 0 R 97 0 R 98 0 R 99 0 R 100 0 R 101 0 R 102 0 R 103 0 R 104 0 R 105 0 R 106 0 R 107 0 R 108 0 R 109 0 R 110 0 R 111 0 R 112 0 R 113 0 R 114 0 R 115 0 R 116 0 R 117 0 R 118 0 R 119 0 R 120 0 R 121 0 R 122 0 R 123 0 R 124 0 R 125 0 R 126 0 R 127 0 R 128 0 R 129 0 R 130 0 R 131 0 R 132 0 R 133 0 R 134 0 R 135 0 R 136 0 R 137 0 R 138 0 R 139 0 R 140 0 R 141 0 R 142 0 R 143 0 R 144 0 R 145 0 R 146 0 R 147 0 R 148 0 R 149 0 R 150 0 R 151 0 R 152 0 R 153 0 R 154 0 R 155 0 R 156 0 R 157 0 R 158 0 R 159 0 R 160 0 R 161 0 R 162 0 R 163 0 R 164 0 R 165 0 R 166 0 R 167 0 R 168 0 R 169 0 R 170 0 R 171 0 R 172 0 R 173 0 R 174 0 R 175 0 R 176 0 R 177 0 R 178 0 R 179 0 R 180 0 R 181 0 R 182 0 R 183 0 R] +/Count 181>> endobj -459 0 obj -<> stream -xm9N@E:E5ջMX lD`=fhɍ Q~kaJəP|F #xDt>XJBjxe!P"QNG*$|DwVV[rD鈣mau_uÓoGXc.*'(Vz*|qv'U[̼UC~? ~a}'k!>OS. B15tw؏-3Ni/K#c} Jt;Xw#>EEDLLӓpvJ[(Ƽ~q endstream endobj -460 0 obj -283 +467 0 obj +285 endobj -463 0 obj -<> -/XObject <> +/Contents 466 0 R +/Resources <> +/XObject <> /ProcSet [/PDF /Text /ImageC]>> /Group <> -/Annots [461 0 R 462 0 R]>> +/Annots [468 0 R 469 0 R]>> endobj -461 0 obj +468 0 obj <> +/AP < > /BS <> @@ -2271,11 +2223,11 @@ endobj /T (www.princexml.com) /Subj (Prince - Non-commercial License) /Contents (This document was created with Prince, a great way of getting web content onto paper.) -/Popup 462 0 R +/Popup 469 0 R /Name /Note>> endobj -462 0 obj +469 0 obj <> /Subtype /Popup -/Parent 461 0 R +/Parent 468 0 R /Open false>> endobj -465 0 obj -<> stream xu0w?\KGY,,QKH}RːHԧ^Ʀ:8?~C ?7] x٥kBl9V:E+ۢPI۶/ @@ -2297,7 +2249,7 @@ x endstream endobj -466 0 obj +473 0 obj 367 endobj @@ -2305,45 +2257,44 @@ endobj <> +/Contents 472 0 R +/Resources <> /ProcSet [/PDF /Text]>> /Group <>>> endobj -467 0 obj -<> stream -x͘n6~ -S P-rOMMiEM{b S1FYEjAQ QqC]g4J[B3%r\(A͌1)J)f2JWp|=;&?::#?gRͤδ&L=t_ J*vk.MpR<<˦h'Pv(*W}pq(>'FQP)Mju,A;(O2l(,W}x&kWI^+`b]`1||\,|H֑ _|<Ӕ̦e=ac~*cTcݛAn#1s FIJqU=Jʌ+:oO\\r9qa;˕ʘlP4N-gAr&2Ir[9 -JKz&sHs=2C0lRm9/u7XtԹD]Ip Mԩ{x/D$w~R\8>&)ќ<$>fK@>0:k!cg$ںj 徨H7e\Ԙ[{%5-KPi\sIOaՓ`BM[Tkߐ_[h9l y?Nw!-zLHG:w?]qkVmpn;dgOmܶ(Vl鷑tY/ʠz +xXn6}W1KME 6.}TlƫV6TJ!wa@8C3pfx\B(-0"q6x(DsW8(Y^(YA˻ɲ=im|vߐQfRNZR= a_|P`鸒2N7BJw ~Rv&*(k_ۖ!T&`efq$:!%o(W ]Wj6e~{"K "2]r|9&f&G!ٕm>çR)4٬&B j+!NG7@B@ϹJHJ:,W]51uGU\\ p|oOɥNy߬kߝV,W`CQ?ER;AC?_ې* ][. +*'f~Nn4crF S/t_qԟ,#U!ȑ.7i"cq&ujs7^,Gs3A]H,)e[8PBc^P7Ab忮In*ƭ668FX"uhrHOʵAfEKRfPj]}Yeϲα }Y--vqS +~)͋ٝs[h4rTk[vA'x[Gҷ$ NLBb>a_5rw5_ax"L#גgӼ>A>@HWa?&8!j%* rʣi+-u`HQ,C:c@_⮰N9$m[>qs+͎u GGc,*x}:T0pbB\(ͭs?X7<@oFۼVWgSBq!1]lS8k2~OЍ/7wmGƢo}_jG~\13qBc:?^ߑw}H8%2aǶmkU&*.ӆ%63oi endstream endobj -468 0 obj -1051 +475 0 obj +1046 endobj 5 0 obj <> +/Contents 474 0 R +/Resources <> /ProcSet [/PDF /Text]>> /Group <> -/Annots [469 0 R 470 0 R 471 0 R 472 0 R 473 0 R 474 0 R 475 0 R 476 0 R 477 0 R 478 0 R 479 0 R 480 0 R 481 0 R 482 0 R 483 0 R 484 0 R 485 0 R 486 0 R 487 0 R 488 0 R 489 0 R 490 0 R 491 0 R]>> +/Annots [476 0 R 477 0 R 478 0 R 479 0 R 480 0 R 481 0 R 482 0 R 483 0 R 484 0 R 485 0 R 486 0 R 487 0 R 488 0 R 489 0 R 490 0 R 491 0 R 492 0 R 493 0 R 494 0 R 495 0 R 496 0 R 497 0 R 498 0 R]>> endobj -469 0 obj +476 0 obj <> endobj -470 0 obj +477 0 obj <> +/Dest [15 0 R /XYZ 0 732 0]>> endobj -471 0 obj +478 0 obj <> -endobj - -472 0 obj -<> endobj -473 0 obj +479 0 obj +<> +endobj + +480 0 obj <> -endobj - -474 0 obj -<> -endobj - -475 0 obj -<> -endobj - -476 0 obj -<> -endobj - -477 0 obj -<> endobj -478 0 obj -<> -endobj - -479 0 obj -<> -endobj - -480 0 obj -<> -endobj - 481 0 obj <> +/Dest [40 0 R /XYZ 0 732 0]>> endobj 482 0 obj <> +/Dest [41 0 R /XYZ 0 732 0]>> endobj 483 0 obj <> +/Dest [42 0 R /XYZ 0 732 0]>> endobj 484 0 obj <> +/Dest [49 0 R /XYZ 0 732 0]>> endobj 485 0 obj <> +endobj + +486 0 obj +<> +endobj + +487 0 obj +<> endobj -486 0 obj +488 0 obj <> +endobj + +489 0 obj +<> +endobj + +490 0 obj +<> endobj -487 0 obj +491 0 obj <> +/Dest [74 0 R /XYZ 0 732 0]>> endobj -488 0 obj +492 0 obj <> +/Dest [77 0 R /XYZ 0 732 0]>> endobj -489 0 obj +493 0 obj <> -endobj - -490 0 obj -<> endobj -491 0 obj +494 0 obj <> endobj -492 0 obj -<> +endobj + +496 0 obj +<> +endobj + +497 0 obj +<> +endobj + +498 0 obj +<> +endobj + +499 0 obj +<> stream -x͘mo6SetO"jME [F=$7ɉ#Xbw;uh d5FI`Brɉy[?lv@jjtRhHaF Ow2eԤWӨbub,eB%t/5U:p(*5j|Qh6OdfMh4УzWu?dV:W|Z6/},=' Z#=M^%9{FDy֑wQo6Eܸi01F-2 LXHab!ҵ AR'ZrweAf1Zczzj}ҊkR:jL;İPv=H]ޒms]iɲZvZRi@Ƨ T+[&ߗɲPw 0V-mK#oIWe經~ST'cx+k77nZWv=1: -s3 xRzU2lȶRS:c8oEYW~Ű͝mU< /Mtn~6~۶uS˼v-q{̐Q? HcFw"u~A渋L FJL8 M\D)bC.]^2}39N T"29U-VELJLr;|*;/J\nۼ} 㛊@,o^>QsCR 99V9P%iܥN|rKnrڏ13ΰ!#q#$W+)`B=r1=ێ_[J;+(_Ӛ==ܕ5eL$+Ml;( J - +x͘n6LITv6. +>l17::$cvɲ1qxh! ~IgwOJW$5[\fI$t.,y"T)G jsc:k>ޥHK=չQ % JgÐb!XPOaxVYJsّ5\G$լ5C')ͦo0ƶI]I5p gjsR(SâcϛBV`bIT]u)Xmȝq3X)uW8iԂ!B!(悧-UeKCPMUیS̜P+LD(P 5gMV*|!4K鬹*l&*Mmӛ~zgK" 3>1BTz>AĘϊ.kgcS+_ ;i,9Ey-y2m50r2/p +2J|ouޭ)Gf6mB 1: K3 VݚLw5v A|RyS}v +2|("p1gIٻ +{bd4@þ];bmƎmWL\o^-&3$[1/ !&J{c4:ݘWdo0Rg0g@"461FR446n];A˄fߚF{'`lG@+1>knnw8P߄{S} +pꃜ5@ʩ7ҳ@j; UUx^)&BUaeWCh52P/XnkA8>Ab_c ~^K?04>$Q_krvh~!zO!MC/T{=8bz< |Bco@qӎ]`bwMh_2",sP|?J endstream endobj -493 0 obj +500 0 obj 976 endobj @@ -2545,562 +2499,542 @@ endobj <> +/Contents 499 0 R +/Resources <> /ProcSet [/PDF /Text]>> /Group <> -/Annots [494 0 R 495 0 R 496 0 R 497 0 R 498 0 R 499 0 R 500 0 R 501 0 R 502 0 R 503 0 R 504 0 R 505 0 R 506 0 R 507 0 R 508 0 R 509 0 R 510 0 R 511 0 R 512 0 R 513 0 R]>> +/Annots [501 0 R 502 0 R 503 0 R 504 0 R 505 0 R 506 0 R 507 0 R 508 0 R 509 0 R 510 0 R 511 0 R 512 0 R 513 0 R 514 0 R 515 0 R 516 0 R 517 0 R 518 0 R 519 0 R 520 0 R]>> endobj -494 0 obj +501 0 obj <> +/Dest [116 0 R /XYZ 0 732 0]>> endobj -495 0 obj +502 0 obj <> +/Dest [117 0 R /XYZ 0 732 0]>> endobj -496 0 obj +503 0 obj <> -endobj - -497 0 obj -<> -endobj - -498 0 obj -<> -endobj - -499 0 obj -<> -endobj - -500 0 obj -<> endobj -501 0 obj +504 0 obj <> endobj -502 0 obj -<> -endobj - -503 0 obj -<> -endobj - -504 0 obj -<> -endobj - 505 0 obj <> +/Dest [125 0 R /XYZ 0 732 0]>> endobj 506 0 obj <> +/Dest [127 0 R /XYZ 0 732 0]>> endobj 507 0 obj <> +/Dest [130 0 R /XYZ 0 732 0]>> endobj 508 0 obj <> +/Dest [133 0 R /XYZ 0 732 0]>> endobj 509 0 obj <>>> +endobj + +510 0 obj +<> +endobj + +511 0 obj +<> +endobj + +512 0 obj +<> endobj -510 0 obj +513 0 obj <> +/Dest [162 0 R /XYZ 0 732 0]>> endobj -511 0 obj +514 0 obj <> endobj -512 0 obj -<> -endobj - -513 0 obj -<> -endobj - -514 0 obj -<> -stream -xWn6}ẈphIu uC@hITP:$rb`ر5gN7,! "(0 </oVD! ۛ{alv o(A=I|f<