I would like to create my own design for Octopress. Until now i figured out how Jekyll and Liquid are working and I think I'm ready to start. When looking in the classic theme I can see everywhere variables like paginator.posts and I was wondering if there is an overview of all available variables. But I wasn't able to find one. Can you giv me any resource?
Octopress is based on jekyll, so you can refer to the Template Data entry on the Jekyll Wiki.
Related
I just got access to the new Stencil beta and I have no idea what to do. I have reviewed all of the documentation on the BC developer website, but I don't know how to proceed. I am also not sure if I will even be able to create designs in Stencil since I don't know Handlbars or json - are those programming skills required or can we still rely on CSS and HTML for most design customization? BC told me there is no support for getting set up and to ask in this forum instead.
Normally I would look under the hood of an existing theme to see how it's built and try "learning on the job" but since I can't even get access to the files, I am at a loss. I created an account on GitHub but I have never used it so I don't know where to look for the files (I did a search but there are thousands of files there and I again couldn't figure out where to start). Can anyone point me in the right direction so I can determine if using Stencil is even feasible for my projects?
Handlebars compiles serverside as HTML. You do still have stylesheets, but we are using some SASS custom functions (documented in Stencil docs).
I'd recommend taking a look here: http://blog.teamtreehouse.com/getting-started-with-handlebars-js
I'm a beginner in dojo. First of all is everything javascript based? For example to create a form I have to use JavaScript or HTML tags?
Also I cannot understand their documentation and tutorials. It's very confusing.
Is there a proper website (other then dojo itself) that has good tutorials?
You can use Dojo's components's (widgets) in two ways. Programmatic and declaritive. The programmatic way (what you are talking about) is by defining widgets through the use of javascript. With declaritive you can define them using HTML markup. David Walsh has a nice short writeup and if you search for "declaritive programmatic dojo" you'll find some questions and answers on the matter:
https://davidwalsh.name/dojo-widget
Difference between programmatically vs declaratively created widgets in dojo?
Declarative coding or programmatic coding in Dojo Projects?
Declarative or programatic approach in DOJO?
If you're having trouble with the tutorials on the Dojo website, i suspect you're better off, first diving into some basic beginner javascript tutorials before trying to learn a framework like Dojo. I concur with the comment Ferry made on your question, there are no better resources than the actual Dojo website. I recommend following every tutorial, starting with the Hello Dojo tutorial and working your way up so that you don't miss out on the basic concepts which you'll need when you read the harder tutorials. Good luck!
For your first question: dojo is javascript-based platform that provide you with a basic javascript library and a bunch of basic widgets (UI controls like button, dialogue, layouts,...), and some extra things. However, you don't really have to use dojo all the time: you still can use dojo to manipulate a html form button; it's just dojo button comes with extra functionalities and might save you some time.
For the second question, I agree with iH8 that dojo website is the best place to start. There are three different ways dojo websites can help you:
Look at the tutorial: Basic steps on how to set it up and use provided functionalities as-is
Look at thetoolkit api: This provides a very detailed view of dojo javascript object (See what extra things you can do with dojo objects)
Look at the nightlytest: I found this very helpful in term of showing me what can be done outside of the tutorial (i.e. how to use things you found in the api)
Other than these, you can look at existing implementation to learn about the toolkit.
Basically, this is how I am learning Dojo. Without more-specific questions, it's hard to tell what is confusing about the tutorial. I would recommend you give it a try and post a question: everyone here will be willing to help you.
I recommend starting with some video tutorial like this.
When you understand the concept, you can try to copy and paste some code from Dojo documentation tutorials or Reference Guide, because all books are out-of-date.
Also you may find some useful information on IBM-related sites like http://www.ibm.com/developerworks because IBM invested in Dojo and uses it for its products.
If you have enough resources ($) you can take participation in Workshops (sitepen.com/workshops)
Later i worked with symfony framework. In this framework we can easily build a multi language project by using FOSUserBundle. But i do'nt know what to do in phalcon! In the Phalcon documentation (multi-lingual-support) explained a way for it! But if i have many languages this way is too difficult!
Do yo know about any provided library for multi language projects?
You can either use the Phalcon\Translate to translate all your strings in respective arrays - one file per language. The reference in the documentation as you correctly posted is here and it refers to the native array adapter.
There are additional adapters in the incubator repo, for PO files or database driven.
You might also want to see the internationalization area in the documentation.
take a look at this piece of code
https://bitbucket.org/moderndeveloperllc/phalconlocale/src
I'm used to Wikipedia's Wiki, and now that I'm using TWiki at work I really miss the ability to discuss a page outside the page but still on TWiki.
Have I missed a button or link somewhere? Is this possible?
In MediaWiki (Wikipedia and the like), every page has a discussion page associated with it. This is not the case in TWiki, at least not by default. The administrator can built something similar, but as a user, all you can do is manually create and link discussion topics.
I think you can reuse the template code in http://foswiki.org/Extensions/TalkContrib on foswiki - I've not used TWiki in years, but foswiki is a compatible fork.
Sven
I downloaded and started playing with CEF, but there doesn't seem to be any docs for it. Not even a working wiki… Am I missing something?
Most of the documentation is in CEF's header files. The binary distribution comes with docs generated from those files. It's well documented in terms of amount of content written, but I had a lot of trouble while learning to use it. The project's Wiki page contains a lot of useful content as does the cefclient sample program.
The CEF3 API documentation can be found at http://magpcss.org/ceforum/apidocs3/
and CEF1 API docuemntation can be found at http://magpcss.org/ceforum/apidocs/. These two links can be found on the Chromium Embedded framework (CEF) wiki home page: https://bitbucket.org/chromiumembedded/cef/wiki/Home
You didn't provide a link to CEF, so I Googled it, and found the project's Web site, which features a prominent link to their wiki.
The wiki has several pages, but the first one that jumped out at me is the General Usage page that shows how to create a "fully functional embedded browser window using CEF".
So I'm not sure where you were looking, but yes, it looks like you were missing something (grin). The wiki documentation is right there.