Blogs

We recently used OneAll to develop a feature that allows user generated content to be created, submitted for review, published, and then automatically posted to the creator's social media channels without additional effort on their part. Here's how we accomplished this.

Ever since we started with the new stack (roughly 5 years ago) we shared our knowledge and our code to help others in the community to do the same. 

Facebook's solution to speed up mobile web page loading is called Facebook Instant Articles (FBIA), and it's only available to Facebook app users. Here's a look at how to integrate FBIA into eZ Publish / eZ Platform.

After another successful summer camp in 2017, we decided to stay in a charming town of Rovinj once again, with Lone Hotel being our venue. We are not changing the dates of the conference either – from August 29 to September 1, 2018, we will welcome you once again to our conference.

Read on: netgenlabs.com/Blog/Save-the-date-for-Web-Summer-Camp-2018 

On content heavy sites, it can be useful to inject snippets of code into CMS data before display (for example, into the body copy of an article). These snippets could be automatically generated glossaries, tables of contents, or ad units, placed mid-content.

Let's explore a general approach to getting such snippets into place.

Giving association members the ability to submit insurance claims online saves time and money for the Alberta Gymnastics Federation. Here we'll take a look at the insurance claims submission web app we built in eZ Publish / eZ Platform.

In an effort to engage its audience, our client, FindaTopDoc, wanted to integrate a custom Q&A platform into its site. They chose Oracle + Bronto as the accompanying marketing automation tool. Here we outline how we integrated Bronto with eZ Platform to build a robust Q&A and newsletter system with the capacity to send customized e-mails to tens of thousands of users.

Intended audience: technical managers, senior developers

Agile developers must constantly strike a balance between building solutions for a known existing case and building solutions that can scale to handle unknown future cases. On the one hand, Agile philosophy encourages us to build and iterate as necessary: Move Fast and Break Things. On the other, various programming best practices encourage us to build in an extensible and modular way from the start: Do One Thing and Do It Well. On smaller projects, these two goals can be achieved simultaneously; but on larger projects – especially given time and budget constraints – it is sometimes necessary to prioritize one over the other. 

Project managers and full-stack developers face such choices almost immediately, during the initial development, staging, and deployment phases. For instance, a project may begin with a narrow scope and require only a single developer’s time. In this case, it often makes sense to forgo provisioning a dedicated development virtual machine (VM) or staging server, and instead, to use generic or shared environments. But as the scope of the project grows, for instance with caching or proxy layers, it often makes sense to implement better development, staging, and production parity.

With recent changes such as developer doc and the new forum now centered around ezplatform.com, I will be posting future Community Board blogs on our Developer Hub.

eZ Publish allows you to develop custom REST APIs to transfer data among different platforms. This "getting started" guide will show you how to build and integrate a REST API into an eZ Publish installation by developing a custom module view that returns a JSON object.