Created integration page, and pre-fill registration article

[spirosikmd]

The introductory text in the Integration page will be written later today.

[larsderidder]

I think it is nicer to start a bit more commercially relevant, as it is written also for merchants/third parties. So something like this: "Paylogic offers a feature to allow the pre-filling of the personal data of a consumer during the sales process via a personalized URL. This can be used whenever a merchant already has the data of the consumers and wants to offer these consumers a more personalized and smooth ticketing process, or when a pre-registration step is used. The following sections...".

[cyberco]

'the pre-filling' => 'prefilling'
'the personal data' => 'personal data'

[tarmack]

Encoding does in no way protect the privacy of the data. Implying that Paylogic thinks it does is, in my opinion, potentially damaging to the company.

[xolox]

Thanks for the article Spyros! Your pull request has been merged and the article has been published: developer.paylogic.com/articles/prefill-registration.html.

I mentioned previously (after a local preview of the merge result) that something strange was going on with the code snippet in the first section ("JSON data format"). Now that the article is live I still see the same problem: The first code snippet simply disappears off the page (although it's still visible in the DOM tree through the inspector). This only happens in Chromium for me; in Firefox it looks fine.

Also, I made some minor changes, please refer to the merge diff for the details (I didn't change any content, just RST format details).

[bubenkoff]

could we update homepage with last articles?
to have it like blog

On 6 January 2014 17:31, Peter Odding notifications@github.com wrote:

Thanks for the article Spyros! Your pull request has been merged and the
article has been published:
developer.paylogic.com/articles/prefill-registration.html.

I mentioned previously (after a local preview of the merge result) that
something strange was going on with the code snippet in the first section
("JSON data format"). Now that the article is live I still see the same
problem: The first code snippet simply disappears off the page (although
it's still visible in the DOM tree through the inspector). This only
happens in Chromium for me; in Firefox it looks fine.

Also, I made some minor changes, please refer to the merge diff for the
details (I didn't change any content, just RST format details).

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/4#issuecomment-31662274
.

Anatoly Bubenkov

[xolox]

@bubenkoff You mean that /index.html contains the latest article instead of linking to it? This can probably be done by customizing Pelican, although I'm not sure how to approach it.

[bubenkoff]

yes, to look more like blog, because it should be a blog, right?

On 6 January 2014 17:36, Peter Odding notifications@github.com wrote:

@bubenkoff https://github.com/bubenkoff You mean that /index.htmlcontains the latest article instead of linking to it? This can probably be
done by customizing Pelican, although I'm not sure how to approach it.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/4#issuecomment-31662780
.

Anatoly Bubenkov

[maikelwever]

Something like this @xolox and @bubenkoff: #5?

[maikelwever]

And about those code highlights: on Chrome on Linux it works fine (v31), but with older firefox (only one I have installed right now: v23) the code dissapears.

[xolox]

I mentioned previously (after a local preview of the merge result) that something strange was going on with the code snippet in the first section ("JSON data format"). Now that the article is live I still see the same problem: The first code snippet simply disappears off the page (although it's still visible in the DOM tree through the inspector). This only happens in Chromium for me; in Firefox it looks fine.

The mystery on my end was solved when I merged and previewed #5: the Chrome extension JSON Prettifier was to blame. I noticed this when I previewed the result of #5 and saw that the JSON block jumped to the bottom of the page, outside the normal page flow, and included some funky nonstandard bits of layout. When I disabled the extension everything went back to normal :-)