Open railsagainstignorance opened 9 years ago
This has been requested by Martin Sivorn as he is currently using the layout generator
can we kill the layout generator?
The time for killing features is probably now. I'd suggest having a chat with the soon-to-be new project owners about things you want to shut down
Need analytics to gather insights into which generators are being used. #117
the layout generator is still usefull
On 30 March 2017 at 15:36, Jake Champion notifications@github.com wrote:
Need analytics to gather insights into which generators are being used.
117 https://github.com/ftlabs/screens/issues/117
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ftlabs/screens/issues/4#issuecomment-290430739, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPRxvczX9KknmiLrK4k8ejS39lk9esQks5rq73xgaJpZM4GbzcD .
--
This email was sent by a company owned by Financial Times Group Limited
("FT Group http://aboutus.ft.com/corporate-information/#axzz3rajCSIAt"),
registered office at Number One Southwark Bridge, London SE1 9HL.
Registered in England and Wales with company number 879531. This e-mail may
contain confidential information. If you are not the intended recipient,
please notify the sender immediately, delete all copies and do not
distribute it further. It could also contain personal views which are not
necessarily those of the FT Group. We may monitor outgoing or
incoming emails as permitted by law.
Useful maybe, but should this be all things to all people?
If people want a specific layout of content, they could instead build a webpage with that layout...
Less things to go wrong on our end, more control for things to behave the way users would like
this (ability to unpack an existing generator instance into the fields on the generator generator) is jolly useful on the carousel, and will become similarly jolly useful if not more so for the layout generator.