Editor push content to Contentful - contentful

I am making my own editor in Vue.js. I can change text and add images etc. I want that content to be pushed to Contentful when I save the changes I made in my editor app. I have checked out the Content Management API and this seems feasible but I don't really know how to start. The extentions for Contentful only focus on creating new stuff for the Contentful webapp and not on creating an editor. Can anyone push me in the right direction?

Contentful's value proposition is to be your content editor in the cloud. It offers you an editor-friendly interface that you don't have to maintain. Non-technical people can create/edit/update content. Usually, there shouldn't be a need to build your own editor interface on top of Contentful.
If you want to use Contentful as a "storage-layer" the CMA is the way to go. That said, theoretically, you could put any interface on top of the CMA API. The question is, though, if you should?
Why you want to use Contentful in the first place because you'd be throwing away one of its core-features (the editor). If you're not planning on using the Contentful editor you could also go with a cloud database instead. :)
The extensions for Contentful only focus on creating new stuff for the Contentful webapp and not on creating an editor
👆 This is correct. Contentful UI-extensions are there to enrich the existing experience. Their use cases range from custom selects to fancy third-party integrations.
Hope that helps. :)

Related

How can I allow users to change their Liferay portrait from a velocity template?

I´m coding a template for a customize theme and would like to let users change their Liferay portrait from there. In addition, it would be nice to add the functionality provided in the "official" window that gives the possibility to select a part of the uploaded image.
The simplest way I can imagine to do this is "building" a link that directly brings the user to that window without having to pass through his profile. Right now, I´m trying to do this with the JS function "Liferay.Portlet.openWindow" but still I haven't been able to find the correct arguments (including the large URL) to accomplish it.
Is what I´m trying to do possible? if so, could you help me?
I think that the best solution to that would be to build a custom liferay MVC or Vaadin protlet to do just that.
This is because the friendlyURL (large URL as you called it) to take a user to that place is usually generated on the fly within the portal instance so you may not have the correct redirection.
Also you would have to use the method ImageLocalServiceUtil which is used to upload images to do the actually portrait change.

web based wysiwyg mail editor component

I'm working on a web based application that needs to send email. I want my users to be able to create html templates with an easy editor. I don't want to build this component myself. Are there any components available that can do this which I can integrate in my application?
There's lots of both free and licenced components out there. My favorite is TinyMCE.
https://www.tinymce.com/
A simple Google search will give you heaps of other choices.
I also used this one in my latest project, and it is also great:
https://www.froala.com/wysiwyg-editor

Embeddable Web UI Designer

Is there are web framework that allows creating of custom Web UI designers that can be embedded into a webpage/webapp?
What I am looking for is to create a web UI that allows users to edit the UI in a drag and drop style editor. It should be possible to select some widgets (like these: http://scaffy.railsware.com/futurico/#pagination) and to select a data source (will be provided by back-end, nodejs).
Background: I am not a web designer and have no previous web experience. I just want to know if it possible to create what I am looking for and how much effort it would be. My background is in embedded Linux development and I would like to create an easy way for people to create machines with single board computers. The embedded stuff is pretty much complete and I am exploring ways to create nice and user editable user interfaces.
I think what you want is possible.
However... as far I know nothing exists which will do exactly what you require.
There are thousands of UI widgets on the Web to choose from but you would need a custom built backend cms developed especially for your needs
There plenty of Web agencies who could provide a bespoke solution. They could also assist with updates and adding new widgets.
So it can be done (and may encounter some browser incompatability issues), but you'll just have to be prepared to spend money.

Customizing the front end of maximo anywhere apps

I have been working on maximo anywhere apps recently and have a requirement to completely change the look and feel of the work execution app, the oslc layer which talks to maximo in the backend remains the same and all the functionalities are the same but there are some new buttons, notification messages and all sorts of UX aspects to be added to the app, I have just started looking at the architecture and code of the app but does anyone know how can I make changes to the front-end or is it even possible? I could find very few documents available online and all of them spoke of customizing features and functionalities but I coudlnot find any document for adding UX aspects.
It would be great someone could point out any documents or kick-off points which I can start looking into.
Thanks.
Thanks for asking, if you're just talking about adding new fields, layouts, screens to the UI, you can do that all through the app.xml, and there are lots of examples on our knowledge center, for example this one:
http://www-01.ibm.com/support/knowledgecenter/SSPJLC_7.5.2/com.ibm.si.mpl.doc_7.5.2/config_apps/t_add_rw_fields.html?lang=en
If you're talking about changing the "look" of the existing widgets, this can all be done through css, by overriding our out of the box css classes. Use Chrome inspector to figure out which css class is being used for each element type, and just override it through standard css approaches.
If you're talking about more advanced customization, for example adding your own new widget types to our screens, it is possible to programmatically instantiate/destroy your own widgets through javascript and add them to our standard application views. This code is usually hooked on the initialize and back event of our views. But you'll be responsible for writing the code to synchronize the data layer with your custom widget. We unfortunately don't have a published example of this customization usecase yet.
We always adding new widget capabilities to our Anywhere UI framework, so I'd love to hear feedback on the new widget types you're interested in.

Orchard CMS - code or UI when doing custom extensions?

I have a question for professional Orchard developers?
Given that I can create new ContentTypes and ContentParts using the UI, when should you use the UI to create new Content Types/Parts versus creating a custom module and coding everything. What are the tradeoffs? Is there a time to combine the approaches and create some of your content types/parts in the UI and then extend them further using code?
What are the advantages of each method? (For example, it seems to me that deploying changes is easier using code...but still possible using the UI using the Import/Export module?
UI it seems you get things done pretty quickly, but is less flexible and portable than writing code?
What are the things you HAVE to do in code?
I tend to start by using the UI to test ideas and just adding templates to my theme to display these new parts. I also use the UI when I just want to add a new part to an existing type.
Where I find making a very simple module with my types specified in migrations useful is where I have a site in production that I know will need upgrading in the future. I have a dev version of the site that I play about with and then when ready to go live I create a migration that will upgrade the site.
This also means I can test the migration before going live and I don't need to have a list of manual changes required to make to the live site that is prone to mistakes.

Resources