At its core, procedural engines are built on generating different kinds of noise and then filtering and combining them to produce the types of values that you want.
The values you are looking for depend on how you model the different elements of your world.
As an example, in my game I wanted to generate regions consisting of different types of terrain. I ended up using voronoi noise (http://en.wikipedia.org/wiki/Voronoi_diagram) to split the terrain into regions and then used the cell value as a multiplier for how bumpy the terrain was. The bumpy terrain was generated from smoothing regular white noise. The amount of smoothing was random too so you could have smooth hills or jagged mountains.
As you can see, you can kinda go wild with it.
http://procworld.blogspot.com/
A couple of quick hints to get you going in the right direction is that there are ( I believe ) a couple of generalized tricks involved to pull this off well. The first is using the 'correct' method to tesselate your voxel geometry. Minecraft literally uses cubes and you are familiar with the result. Another 'classic' method is the application of marching cubes/tetrahedra. This gives you fairly good organic-ish shapes but suffers from the inability to render sharp edges. Everything looks blobby. I believe the method used by EQN makes use dual-contouring, or a variant, which allows you to create organic shapes and also preserve sharp edges. A second factor is the ability to use different levels of resolution or scale for your voxels situationally. This allows you to craft human-scale things like cups and swords and whatnot, with human-scale details, and still craft houses and mountains and trees, without the need for storing extreme resolution in those items as well. It can be very tricky to patch together various bits of geometry tessellated from different voxel resolutions like this, and not end up with ugly visual artifacts. There is also the thorny issue of applying textures or materials to everything I have mentioned previously, which I have never investigated :)
It isn't that different, the only real change is how you handle edge conditions, as you can have finer detail so need to filter less.
Minecraft doesn't use blocks to simplify world generation, it uses blocks to simplify world modification by the user. The blocks restrict you making it easier (oddly enough) to create things.
A bit (but just a little) more information can be found here: http://www.thesixthaxis.com/2014/06/25/crafting-the-endless-...
Are there any articles about how an engine like this is built? It is an extreme level of procedural generation (apparently), but the graphics aren't blocky and as abstract, but rather pretty impressive.
In a similar vein is Eskil Steenberg's Love [1], but this is on another level entirely.
[1] http://www.quelsolaar.com/love/index.html