I've been looking around at some CSS frameworks and I really like the look of the Groundwork CSS framework because it has a nice responsive layout. However I downloaded the source code and I'm a bit lost. I'm used to using Twitter Bootstrap and and I really love it's documentation (the instructions on scaffolding are helpful to beginners), bit I don't really know how to use Groundwork.
How do I get started with using the Groundwork CSS framework?
Groundwork, like Bootstrap, is a web-development framework, not just a set of CSS docs. They both include a set of style-sheets, java-script files, misc icons etc, and one or more HTML docs to bring it all together.Installation is simple; download the framework, rename the folder to "MyCoolNewSite", start editing.
As Michal stated, the "index/html" doc that comes with the framework has lots to look at to help you get started. They also have what looks to be pretty solid documentation on their site, starting here: http://groundwork.sidereel.com/?url=grid
The site has now changed to: http://groundworkcss.github.io/
Related
I'm a graphic designer who just started learning Laravel this week, recently I've been searching how to install the latest bootstrap version in my project correctly, which is all I need to be honest and I'm not too comfortable with other options like Tailwind.
As some tutorials and answers have suggested I ended up compiling and using a famous project named laravel/ui, sadly the resulting version comes with a few changes, that just doesn't look as good in my opinion (different fonts like Nonito, colors and margins)
So now I'm wondering...
Why is it not recommended to just add the CDN links in my master template?
Is it possible to update this compiled CSS somehow to make it look as the CDN?
Sorry if this questions might be opinion based, but I'm really out of places to ask, seems like the documentation for Laravel 8.x has removed everything related to Frontend, which are making thing even more confusing for me with all these options Laravel offers.
I recently started using SASS and right now I need Font Awesome for one of my project but I want to use it offline. I know that I could simply use CDN (as I did) but I just don't know how to use it offline so it's pretty annoying :D
Well, basically you just download the resources, add the .js/css-links to your .html and use the icons ;-)
It's all described on their website - but the choice of options (CSS or SVG) might make it look more difficult than it is...
I wrote a Javascript (jQuery) plugin. Now I want to write a documentation site for it. Is there a good tool to create such a site out of some offline file formats or works like a CMS?
I know this answer has been asked before, but the last answers are from 2011. Is there anything new that does an awesome job in writing documentation?
There are a few new tools for generating websites or blogs from code/directory.
Bootstrap v3 just switched to jekyll for documentation. jekyll knows how to process Markdown or Liquid (markdown flavours)
Grunt.js is also used for all sorts of automated task. One of these being documentation generation. Search their plugin list for doc
assemble.io is another tool for generating documentation pages
I'll extend if I bump into others. I am not sure if this is exactly what you need, but they are general purpose so I am sure a jQuery plugin can fit in.
I am making a fairly big website. Mostly on culture of a particular place.
Are static sites a good idea?
How do I integrate nanoc and some framework? There are a couple of github repos on this, but I wanted to this from scratch in order to learn. Otherwise, I am afraid I might not be able to fix something that goes wrong later.
PLease help~
I've recently decided to make a reasonably sized site using nanoc and Zurb Foundation myself, so I can tell you my thoughts on this:
A static site is a good idea in many situations, but they do have obvious limitations (with everything being static!). The typical use of a static generator like nanoc is for a blog, for which most of the limitations aren't a problem (especially with services like Disqus for comments). I personally decided to use nanoc to save hosting/maintenance costs initially (using Amazon S3 to host a static site is cheap and scalable compared to a VPS), because I don't need any of the dynamic stuff yet, and to learn something new!
I've written a few posts on my blog (link in my profile) about how I've integrated foundation from scratch with nanoc. I can't comment for bootstrap, but my steps were:
Use the nanoc tutorial to create a site
Use compass to integrate foundation into your site, by creating a compass.rb that has a require "zurb-foundation" line as well as config for your asset paths (mine is here)
Run a compass install foundation -c compass.rb to populate the foundation stylesheets, images and javascripts into your asset directories
Update your Rules file to include compass, and process the stylesheets accordingly
That is a high-level overview - there's step-by-step detail on my blog if you're interested in going the foundation route.
I bought the O'Reilly Dojo book by Matthew Russell. It says "in your toolkit checkout, you can find a theme tester at dijit/themes/themeTester.html.
I downloaded 1.3.2 from here: http://dojotoolkit.com/downloads
and cannot find such a file. I would like to see each of the three themes in action.
How can I do that?
Thanks,
Neal Walters
themeTester isn't in the release (minified) version. You need to download the *-src ones. For example this one: http://download.dojotoolkit.org/release-1.3.2/dojo-release-1.3.2-src.tar.gz. These are available off of the 'More downloads' link on the downloads page.
Besides what Wahnfireden said, you can also check out Dojocampus docs. It has examples embedded where you can dynamically change the theme applied to individual widgets (as well as change the version of dojo that is used). For example, dijit.form.Button has a bunch of examples to look at.
Dijit Theme Tester
Another great place to test out Dijit and DojoX widgets is to look at their tests. Dijit tests are here, and DojoX tests are within each individual folder here.
Note that these links are to the nightly build, not 1.3.2, so there may be small differences. I'd suggest using the Dojo nightly though, personally.