Page MenuHomePhabricator

Introduce EFL legacy API to third party developers
Closed, ResolvedPublic

Description

We do not really have a clean introduction to the legacy EFL API and history in our documentation, which doesn't really help figuring things out. Taking inspiration from https://developer.tizen.org/development/guides/native-application/user-interface/efl/introduction , it would be good to add this to our documentation.

cedric added a comment.Aug 3 2017, 3:35 PM

It might be good to break down https://www.enlightenment.org/docs/efl/start or use that to as material.

zmike added a project: efl.Aug 22 2017, 3:43 PM
cedric raised the priority of this task from Wishlist to High.Oct 2 2017, 3:20 PM

@cedric: Do you mean that https://www.enlightenment.org/docs/efl/start should be moved to https://www.enlightenment.org/develop/legacy/start.md - and, if so, what should be in /docs/efl/start in its place?

cedric added a comment.Dec 1 2017, 6:33 AM

Hum, when I click on the first link https://www.enlightenment.org/docs/efl/start, I end up in https://www.enlightenment.org/develop/efl/start. Which I think should become https://www.enlightenment.org/develop/legacy/start as the other one should for the new API with maybe a small paragraph to direct people that want legacy documentation. There is no need to convert it to .md actually as the page is already good enough in its current form.

@cedric: So, move the current /develop/efl/start to /develop/legacy/start, then create a new landing page for /develop/efl/start - do I have that right?

Looking at the ticket, it seems to be calling for the same as T5831 - i.e. an overview of EFL, its history, and so forth. Should the new /develop/efl/start and /contrib/devs/start have the same introductory information in them - an overview of the project, its status, features, and so forth? Or is that better left out of both and put in /about-efl instead?

Hi, what is the status on this ticket? I had it in my mind that the legacy intro was done but I remember now it was just a portion of the page.
Should I try picking up this ticket instead?