tree: 6c8512ffa3197189c4becb17686eaa383f2920af [path history] [tgz]
  1. 1_million_commits_and_still.md
  2. 2022_Infra_Survey_Results.md
  3. another-oar-in-the-water.md
  4. apache-and-github-a-friendly.md
  5. apache_cms_and_external_build.md
  6. apache_cms_latest_new_feature.md
  7. apache_cms_new_features_for.md
  8. apache_gains_additional_travis_ci.md
  9. apache_org_04_09_2010.md
  10. apache_org_downtime_initial_report.md
  11. apache_org_downtime_report.md
  12. apache_org_incident_report_for.md
  13. apache_services_and_sha_1.md
  14. appveyor_ci_now_available_for.md
  15. asf_buildbot_svn_setup.md
  16. asf_comments_system_live.md
  17. Blogs has a new home.md
  18. blogs-a-o-moved-upgraded.md
  19. brand-new-selfserve-page.md
  20. bringing-gitpubsub-to-the-apache.md
  21. buildbot_master_currently_off_line.md
  22. changes_to_email_service_for.md
  23. code_signing_service_now_available.md
  24. committer_shell_access_to_people.md
  25. committers_mail_relay_service.md
  26. confluence_2_10_migration_for.md
  27. confluence_wiki_service_to_be.md
  28. continued_outages_for_the_asf.md
  29. controlling_your_spamassassin_threshold1.md
  30. ddos_mystery_involving_linux_and.md
  31. dear_apache.md
  32. dmarc_filtering_on_lists_that.md
  33. downtime_notice_for_the_r.md
  34. email-service-interruption-and-restoration.md
  35. email_from_apache_org_committer.md
  36. even-more-github-features-added.md
  37. git_at_apache.md
  38. git_based_websites_available.md
  39. github_pull_request_builds_now.md
  40. heartbleed_fallout_for_apache.md
  41. https_id_apache_org_new.md
  42. improved_integration_between_apache_and.md
  43. improving_our_subversion_services.md
  44. index.md
  45. infrastructure_team_adopting_an_on.md
  46. introducing_jira_service_desk.md
  47. it_s_official_we_now.md
  48. jira-public-signup-disabled.md
  49. ldap_and_password_policy.md
  50. ldap_it_s_getting_closer.md
  51. ldap_svn_coupled_together.md
  52. mail_outage.md
  53. mail_outage_post_mortem.md
  54. mail_service_architecture_changes.md
  55. mirroring_to_github_issues.md
  56. moinmoin_service_user_account_tidy.md
  57. more-secure-and-robust-downloads.md
  58. new-and-enhanced-gitbox-platform.md
  59. new-jenkins-nodes-running-windows.md
  60. new-notification-scheme-features-for.md
  61. new_faces_in_infrastructure.md
  62. new_hardware_for_apache_org.md
  63. new_infra_team_members.md
  64. new_mailing_list_for_ci.md
  65. new_monitoring_system_nagios_is.md
  66. new_slaves_for_asf_builbot.md
  67. new_status_page_for_the.md
  68. nexus_reduced_performance_issues_resolved.md
  69. on_demand_slaves_from_rackspace.md
  70. paste_apache_org_sees_the.md
  71. pear_package_hosting_available1.md
  72. planned_downtime_for_jira.md
  73. planned_downtime_for_jira1.md
  74. planned_downtime_for_reviewboard.md
  75. position-available-infrastructure-systems-administrator.md
  76. position_available_infrastructure_systems_administrator.md
  77. promoting-podlings.md
  78. public_preview_of_drafts_feature.md
  79. rate-limiting-on-apache-services.md
  80. README.md
  81. relaying_mail_from_apache_org.md
  82. relocation-of-apache-git-repositories.md
  83. reviewboard_instance_running_at_the.md
  84. roller-updated-to-5-2.md
  85. roller_installed_for_use_by.md
  86. s_apache_org_uri_shortening.md
  87. scaling_down_the_cms_to.md
  88. slow_svn_service_this_week.md
  89. strengthening-the-infra-team.md
  90. subversion-to-git-service-git.md
  91. subversion_master_undergoing_emergency_maintenance.md
  92. subversion_on_the_fly_replication.md
  93. svn_performance_enhancements.md
  94. svn_service_outage_postmortem.md
  95. the_asf_cms.md
  96. the_asf_ldap_system.md
  97. the_joy_of_feedback.md
  98. the_value_of_taint_checks.md
  99. towards_a_redeployable_future_or.md
  100. translate_service_now_open.md
  101. welcome-to-roller-6-0.md
  102. welcome_new_members_of_the.md
  103. what_can_the_asf_buildbot.md
content/blog/README.md

The Infra Blog

  • index.md is the wheelhouse for the blog. There you define the general title and which template the blog is using.
  • The blog's template defines the look and feel of the blog page, and also calls the blog articles for display.

Blog entry metadata

Metadata includes the title of the entry and the date it was published. Pelican supports a large number of metadata fields, some of which support searching and filtering when you are looking for specific information.

Required metadata: For each blog entry, make sure you provide the following metadata at the top of the file:

  • layout: post
  • title: the article's title
  • date: the date the post first appeared (yyyy-mm-dd)
  • permalink: a short phrase identifying the post
  • category: content category. Only provide ONE for each blog post. Current options are event, general, infra, policy, projects, security, service, tools. note: filtering is not enabled yet.

These metadata fields are available, but are currently optional for the Infra blog:

  • author: content author, when there is just one
  • authors: separate the names of multiple content authors with commas
  • keywords: content keywords, separated by commas (HTML content only)
  • modified: the most recent date of changes to the post (yyyy-mm-dd)
  • slug: identifier used in URLs and translations
  • status: options are draft, hidden, or published
  • summary: brief description for use on index pages
  • tags: content tags, separated by commas
  • url: url to use for this article

Pelican supports these tags, which the Infra blog does not use:

  • lang: content language ID
  • save_as: save content to this relative file path
  • template: template to use to generate content
  • translation (true or false)

The first line of the file should have this metadata, at a minimum:

  layout: post title: THE ENTRY'S TITLE date: 2010-01-01 permalink: KEY WORDS FROM THE TITLE category CATEGORY

Note that the title does not need a period at its end.

For better readability as you are editing, you can lay out the metadata using multiple lines:

layout: post
title: THE ENTRY'S TITLE
date: 2010-01-01
permalink: KEY WORDS FROM THE TITLE
category CATEGORY

Creating a blog entry

To create an entry, create an .md file in this folder. The file's name should probably be like the permalink for the entry.

  • give the file a meaningful title that does not duplicate one we have used already.

  • Starting at the first line of the file, add metadata for the entry, as described above.

  • Write your entry using Markdown.

  • If you do not want to publish the blog post as soon as you commit it to the repository, set the metadata status: draft. When you are ready to publish the post, change the status to published or remove the status metadata altogether. Then commit the file.

  • You can edit the entry at any time. Updating an older entry does not move it to the top of the blog's display.

Making use of the search feature

The search feature is not currently enabled for the ASF blog. As soon as it available, information on preparing your blog post to be searchable will appear here.