Hi jdd, On 04/10/2016 11:18 AM, jdd wrote:

1) do you have a link to a way of knowing how one can really *use* jekyll to write a blog or web site? (I want to write, what do I have to do)

I'm running Jekyll on openSUSE Leap 42.1. You'll need gcc & make. Then fire up: gem install jekyll It does not put the symbolic link, let's do it manually: ln -s /usr/bin/jekyll.ruby2.1 /usr/local/bin/jekyll To create a "project", do: jekyll create my-web-project jekyll serve & The output should look like: Configuration file: /home/ish/my-web-project/_config.yml Source: /home/ish/my-web-project Destination: /home/ish/my-web-project/_site Incremental build: disabled. Enable with --incremental Generating... done in 17.329 seconds. Auto-regeneration: enabled for '/home/ish/my-web-project' Configuration file: /home/ish/my-web-project/_config.yml Server address: http://127.0.0.1:4000/ Server running... press ctrl-c to stop. I also tried a WP migration and it appeared to be straight-forward with "jekyll-import". You'll also need the following "sequel", "unidecode", "mysql". gem install sequel unidecode mysql jekyll-import The following snippet will import the WordPress posts into the Jekyll project: ruby -rubygems -e 'require "jekyll-import"; JekyllImport::Importers::WordPress.run({ "dbname" => "wordpress", "user" => "wpadmin", "password" => "xxxxxx", "host" => "localhost", "socket" => "", "table_prefix" => "wp_", "site_prefix" => "", "clean_entities" => true, "comments" => true, "categories" => true, "tags" => true, "more_excerpt" => true, "more_anchor" => true, "extension" => "html", "status" => ["publish"] })' Cheers, -- Ish Sookun - Advocating openSUSE since 2010 :) - I blog at HACKLOG.mu Try openSUSE, https://www.opensuse.org -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org

Le 10/04/2016 14:44, Bruno Friedmann a écrit :

Now for me my main concern will be how to migrate lizards wp where I can't have mysql db connection :-)

I use pmwiki, that don't need any database http://www.pmwiki.org/ I could move my previous wordpress account texts, but manually (copy and paste) http://dodin.info/wiki/pmwiki.php?n=Bavardages.Bavardages there are blog-like plugins, but I don't see any reason for the fuss jdd -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org

On dimanche, 10 avril 2016 15.42:22 h CEST Richard Brown wrote:

On 10 April 2016 at 14:44, Bruno Friedmann wrote:

...

On dimanche, 10 avril 2016 14.13:00 h CEST Ish Sookun wrote:

...

Hi jdd,

On 04/10/2016 11:18 AM, jdd wrote:

...

1) do you have a link to a way of knowing how one can really *use* jekyll to write a blog or web site? (I want to write, what do I have to do)

I'm running Jekyll on openSUSE Leap 42.1. You'll need gcc & make. Then fire up: gem install jekyll

It does not put the symbolic link, let's do it manually:

ln -s /usr/bin/jekyll.ruby2.1 /usr/local/bin/jekyll

To create a "project", do:

jekyll create my-web-project jekyll serve &

The output should look like:

Configuration file: /home/ish/my-web-project/_config.yml Source: /home/ish/my-web-project Destination: /home/ish/my-web-project/_site Incremental build: disabled. Enable with --incremental Generating... done in 17.329 seconds. Auto-regeneration: enabled for '/home/ish/my-web-project' Configuration file: /home/ish/my-web-project/_config.yml Server address: http://127.0.0.1:4000/ Server running... press ctrl-c to stop.

I also tried a WP migration and it appeared to be straight-forward with "jekyll-import". You'll also need the following "sequel", "unidecode", "mysql".

gem install sequel unidecode mysql jekyll-import

The following snippet will import the WordPress posts into the Jekyll project:

ruby -rubygems -e 'require "jekyll-import"; JekyllImport::Importers::WordPress.run({ "dbname" => "wordpress", "user" => "wpadmin", "password" => "xxxxxx", "host" => "localhost", "socket" => "", "table_prefix" => "wp_", "site_prefix" => "", "clean_entities" => true, "comments" => true, "categories" => true, "tags" => true, "more_excerpt" => true, "more_anchor" => true, "extension" => "html", "status" => ["publish"] })'

Cheers,

Thanks Ish for the information.

Now for me my main concern will be how to migrate lizards wp where I can't have mysql db connection :-) On board report, I'm seeing that lizards will close (unfortunately, but understable). And contact will be made with author to help on migration. I certainly have to wait until this happen.

Don't worry, Lizards' wont be going anywhere until everyone currently on it has found a new home

But if you want to get ahead of things by moving now, awesome :)

Do lizards users have access to the Wordpress > Tools > Export tool?

If so, you can use that and this variation on what Ish posted above to import from one of those wordpress.xml exports

https://import.jekyllrb.com/docs/wordpressdotcom/

Nope unfortunately we don't have this export tools as normal user on lizards.o.o Perhaps we can have them, or some volunteers to export on request ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org

On 10 April 2016 at 14:46, jdd wrote:

your instructions are not totally exact, there is no "create" but "build", but it's not important.

If I create a file "file.txt" in the source folder, it's simply copied in the target folder. It's not what I call a "generator"]

This isn't how Jekyll works at all..

https://jekyllrb.com/docs/posts/

This is a correct link that describes the actual behaviour of Jekyll, I'm confused how you make the above statement when the documentation clearly says the opposite "All posts must have YAML Front Matter, and they will be converted from their source format into an HTML page that is part of your static site." To give an example using my blog You can see the source of my entire blog, it's theme, it's config, and it's posts, on [Github](https://github.com/sysrich/rootco.de-web) I have copies of this git repo on all of my machines, which I synchronise using `git pull` When I want to write a new blog post, I create a file called `$date-$title.md` eg. 2016-04-04-opensuse-and-you.md I then write the post using the simple Markdown language https://daringfireball.net/projects/markdown/basics This language is pretty wonderful. It's easy to learn, it's easy to use, there are lots of editors that understand the language and can help you (automatic syntax highlighting in gedit and vim for example). Unlike many other markup languages (eg. HTML) it is also very easy to read even before it has been converted into something else. To prove this point, I have written this entire email using the Markdown format ;) The post needs to have a few lines of information at the start, this is what the Jekyll docs call the YAML Front Matter. Taking the example from my recent 'Why You Should Use Tumbleweed' post, this is basically two or three lines (the `date:` is optional) in between two lines with 3 dashes `---` That tells Jekyll the title of the blog post and what kind of layout to use (normally `layout: post`)

--- layout: post title: Why You Should Use Tumbleweed date: '2016-03-28 19:05:02' ---

Then you write the blog post. You can see the full markdown used for the 'Why You Should Use Tumbleweed' post here: https://raw.githubusercontent.com/sysrich/rootco.de-web/master/_posts/2016-0... When `jekyll build` runs in my `rootco.de-web` folder on my machine, it takes the markdown file in `_posts` and creates a totally new html file in `_site` It is this `_site` folder which I upload to my website, where you can see the nice generated output http://rootco.de/2016-03-28-why-use-tumbleweed/ I actually automate the whole thing using git, so I work on my laptop/desktop, `git commit` it there, `git push` it back to GitHub, then my server actually as a cron job which automatically does a `git pull` from GitHub, runs Jekyll, and puts the `_site` folder in the `/srv/www/htdocs` folder of my Apache2 server. But that is an advanced topic I wouldn't worry about if you just want to get started with Jekyll, because GitHub can do all of that for you All you need to do to get started is have a Github account - https://github.com/join Whatever you pick as your username will end up being part of your blogs URL * Then login. * Go to https://github.com/sysrich/beautiful-jekyll-opensuse * Click on 'Fork' in the top right hand corner * Then go to 'Settings' and rename the Repository Name to "yourusername.github.io" * Then, using the Text Editor available in the GitHub WebUI, you can edit the _config.yml file for your blog to change it's settings and set it up the way you like * Then, using the buttons available in the GitHub WebUI, you can make your `_posts` folder and make your first `$date-$title.md` file like I described above * Then, using the text editor in the GitHub WebUI you can start writing your blog post You don't need to run this on an openSUSE machine to get started. You don't need to do fancy stuff like me and Ish. Github will automatically do all the Jekyll build and blah for you.. you don't need to install anything, you don't need to configure much..it really couldn't be much easier to get started All of this is documented, including an animated video of the steps I list above, in the original link to the beautiful-jekyll-openSUSE theme https://github.com/sysrich/beautiful-jekyll-opensuse/blob/master/README.md Does this help? -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org

On 10 April 2016 at 16:20, jdd wrote:

Le 10/04/2016 15:37, Richard Brown a écrit :

...

This isn't how Jekyll works at all..

well I wished what you explain (pretty well) in your mail be explained on the jekyll site. This would have prevented me from using it :-)

I think a simple wiki like pmwiki much easier. No database, no git account, any web site accessible with ftp

http://www.pmwiki.org/wiki/PmWiki/Installation

untar the archive and you are done.

the markup is a variant of markdown, simpler than mediawiki one that you need to know for our wiki, and like for our wiki, the only markup one really need is than one have to let a blank line between two paragraphs...

this is even simpler than reading your mail (or mine, by the way :-)

that is why I tested jekyll with an empty text file. a "generator" should have done better than a copy.

When you feed Jekyll something other than markdown files, Jekyll just copies That's a good thing - that's exactly what you want it to do when you want your site generator to deal with other file formats I use that feature for uploading images and presentations to my server. Your wiki might make sense for your own personal use cases, but for me it would be greatly deficient Compared to Jekyll pmwiki has the following missing features - Solid Themeing - Blog post handling (I don't want to have to micro-manage 'articles' in a wiki) - Handling of different filetypes (Copying is good) - Simple blog-like RSS Feeds - Essential if I want my blog to be listed on planet.opensuse.org Each to their own, but the reason I'm sharing this is that it is a nice, relatively simple, reusable, pretty, openSUSE themed blogging option -- To unsubscribe, e-mail: opensuse-marketing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-marketing+owner@opensuse.org