accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mikewalch <...@git.apache.org>
Subject [GitHub] accumulo issue #170: ACCUMULO-4503 Added blog to project website
Date Wed, 26 Oct 2016 14:15:41 GMT
Github user mikewalch commented on the issue:

    https://github.com/apache/accumulo/pull/170
  
    @joshelser, with this pull request, I am trying to mimic what has been done on the Apache
Fluo website.  The Fluo website has two kinds of Jekyll posts (blog and release). Blog posts
are self-explanatory. Release posts contain the release notes for the release and links to
resources (binary tarball, docs, javadocs, etc) for that release. Below are examples each
post type:
    
    https://fluo.apache.org/blog/2016/06/02/fluo-moving-to-apache/
    https://fluo.apache.org/release/fluo-1.0.0-incubating/
    
    When you go to https://fluo.apache.org/news/, you see all posts (blog & release).
 This was done to avoid creating two posts (a release post and a blog post announcing the
release).  When you go https://fluo.apache.org/release/, you only see releases (the pre-apache
releases have been excluded).  Currently, the page https://fluo.apache.org/blog/ redirects
to /news/ but it could show only blog posts.  This system has made releases easier to Fluo.
 You just need to create one markdown document and the release will show up in 3 locations
automatically ( 'latest news' on main page, the news archive '/news/', and release archive
'/release/').  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message