Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our community
ResponsiveDuberdicus's Experience
ConsiderateNinurta's Experience
sharklas's Experience
Top Pro
•••
Top Pro
•••
Top Con
•••Top Pro
•••
Darren Dub's Experience
Top Con
•••
Top Pro
•••
Very flexible without being stupid complicated. It's Python. See More
Hugo is a lightweight install compared to others. At about 38mb it's just one file: hugo.exe. You can put it anywhere then just add this to your path to use from anywhere. no dependencies. It's very fast which is great if when learning since you can quickly set up multiple sites to experiment with. It's well documented though I don't think the docs are as precise as Jekyll. Adding themes can be tricky, certainly at first. I found the blank theme for developers pretty good though. Just add some content: hugo new posts/first-blog-post.md and launch in draft mode hugo server -D to view your site. I like the speed and generally found it a joy to use. See More
we are currently switching our site to Hugo and so far it's been a great experience. See More
We are using Hugo as the base-framework for a full blown knowledge management system, idea-management and inhouse brainstorming tool. Hugo source-code is well structures and comes with top components out of the box, that makes every solution built on this framework incredible fast and scalable accross platforms and corporate silos! Hugo - when being used as a framework is a game-changer that puts Sharepoint, Wordpress and Co. back to the shelf. See More
Octopress is designed to remove all the time-consuming and frustrating tasks you usually have to deal with when using Jekyll. You don't have to write your own HTML templates or do any configuration to get started. The default template also takes care of any basic CSS/JS you need to write to get going. See More
Handlebars' philosophy of "no logic in templates" makes some things difficult: DocPad built-in template helpers aren't available by default - they have to be manually added/exposed DocPad's example template code often includes logic, which makes it impossible to use within Handlebars templates -- it has to be abstracted into custom helper functions. Can't pass objects to function calls from within HB templates. See More
DocPad's has a large amount of plug-ins available to extend its functionality and compatibility with other language preprocessors and markup languages. Javascript preprocessors include: Coffescript, TypeScript, and LiveScript. CSS preprocessors include: LESS, SASS, Stylus, and Roole HTML markups include: Markdown, and Textile Templating engines include: Eco, Handlebars, Moustache, HAML, CoffeeKup, Jade, and Teacup JSON converters include: YAML and CSON See More
You have a lot of power when you have React and GraphQL at your disposal. Not only do you have the growing Gatsby plugin ecosystem, but you also can use the enormous selection React libraries available. By using the GraphQL Data Layer, you can easily pull in data from other pages or data sources. See More
According to the spec on API chaining, the API request/response need to associate an API object to an corresponding controller/action/uri to be able to validate and handle the request/response and the datasets. Without that, the consuming client service cannot properly validate or relate the datasets from one to the other. Links have no relational value and the api object creates the relationship between the datasets while maintaining an api/dataset relationship with the corresponding controller/action/uri As such, the current methodology supported would not be able to be called by the client not supported by the client in a RESTFUL manner See More
Roots is currently in the process examining how to leverage newer technologies to make Roots even better. You can see the new project on github: https://github.com/carrot/roots-mini Here is the blog post explaining the next phase of Roots: https://medium.com/@jescalan/eaa10c75eb22#.uacjziaej Here is the stack they're experimenting with: - jade - for markup
- babel - for JS and JS transforms
- postcss - for CSS transforms
- webpack - as the core compiler As this is a work in process, it just means the future of Roots continues to look great. See More