Go to file
Kyle Gordy 9b1b245e2f Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
_category Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
_data I'm going to visit a school for kids that can't write good 2019-12-02 18:55:07 -08:00
_includes Make scroll to posts id a global site variable, apply id to featured hero / pagination 2019-12-05 10:59:28 -05:00
_layouts Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
_posts Too much future 2019-12-03 07:57:34 -08:00
assets Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
blog Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
.gitignore Add support for author metadata to be included in the post page 2019-11-22 06:37:18 -08:00
404.html Fix 404 return home link 2019-11-23 00:59:15 -05:00
CNAME Create CNAME 2019-10-22 16:56:15 -07:00
CONTRIBUTING.adoc Add some documentation for contributing. 2019-11-27 12:56:49 -08:00
Gemfile Configure proper syntax highlighting to support new backdated blog posts 2019-11-22 07:07:13 -08:00
Gemfile.lock Configure proper syntax highlighting to support new backdated blog posts 2019-11-22 07:07:13 -08:00
LICENSE Initial commit 2019-09-09 15:48:17 -07:00
README.md Add some documentation for contributing. 2019-11-27 12:56:49 -08:00
_config.yml Add blog category navigation / index page support 2019-12-05 11:33:01 -05:00
careers.html Move benefits info into a data file to keep things DRY 2019-12-02 14:47:28 -05:00
favicon.ico Add favicon 2019-11-12 11:14:21 -05:00
index.markdown Base Jekyll install 2019-10-22 10:36:16 -04:00
projects.html Split project list into a partial to use on multiple pages 2019-11-21 20:34:01 -05:00

README.md

Scribd's tech blog

Our tech blog is published to tech.scribd.com. The goal of the site is to share what we're up to as we build, design, and deploy the technology that powers scribd.com.

Content Guidelines

The CONTRIBUTING document has some details on how to contribute to this repository, but if you've contributed to a Jekyll-based site before, this should all be fairly straight-forward.

The types of content published should generally be technology oriented, but discussions about organization culture, collaboration, and process are welcome so long as they pass the bar of: "would this be interesting to somebody we would want to work with us?"