TinyMCE has Ephox Enterprise which gives content authoring solutions.
I want to know which are the other content authoring solutions available which may also be supported by TinyMCE.
Content Authoring Solutions in the sense which helps in tracking the changes and also which provides approvals based on roles/entitlements
Thanks
Related
My company is looking to streamline User Story documentation in DevOps's Agile workflow. Is there a way to use markdown formatting in Description / Acceptance Criteria fields in DevOps? It is far more flexible and powerful than the WYSIWYG editor available in DevOps.
You may have known that in Azure Devops, we haven't directly provide such feature in WIT. So, to achieve what you want, just consider to develop an extension.
For VSTS, there has an existing one Markdown. But I saw you tagged this question with a azure-devops-server-2019 tag. If your server type is TFS, please check this extension source code, and then made some customized changes into it to let it available for your server.
See how to develop extension for TFS work item.
The working logic of this extension is adding a custom control which expand Markdown edit into work item layout.
Since what you are using is Azure Devops server 2019, below operation and its action logic also suitable for you.
With more details, in your requirement, you want the fields Description / Acceptance Criteria can support to use Markdown. This extension would let you add a custom control to User story.
Step1: In its custom control, choosing Markdown as control type which can let this field control under Markdown.
Step2: Choose which field you want to show Markdown editor for, here is Description
Step3: Choosing corresponding layout location, store it in to a new group.
Step4: You should not want there has two same editors on the work item form. So, hiding the default one:
After the above steps, now, the Description fields can support Markdown language.
Is there a way to add a .github/release_template.md similar to pull requests, so that when you are drafting a new release, it uses the template?
I've seen https://github.com/apps/release-drafter and alike that you can add to your GitHub, but was wondering if this is natively supported.
No. Templates are only supported for issues and pull requests.
As of October 2021, you can now add a .github/release.yml file to do some autopopulation of the release notes:
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuring-automatically-generated-release-notes
Right now it is a bit limited, and needs a bit of extra functionality to become a full template, but I think moving forward that will be the file you'd be looking for in this situation.
It's not quite what you (and I) want but you can use query parameters to pre-populate the create release form:
https://docs.github.com/en/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters
which may be useful if for example you add a "Create Release" link in your documentation.
The same approach could be used to create a "custom tab" that uses the link I think (settings > custom tabs)
I am starting an app with material ui .18. I see that 1.0 is around the corner. I wanted to know what are there plans to support the current api?
Version 1.0, which is maintained on the next branch, is going to introduce breaking changes. The effort appears to include consideration for all of the components that are currently offered, but the API will and overall approach to styles will not be the same.
You can get an idea of the ways it has already deviated by reviewing the docs for the next branch. Also, take a look at the github project for some insight on the roadmap.
The most obvious change is the way styles are handled. They're using CSS in JS rather than inline styles. You can read more about that here.
I find Jekyll to be very easy and useful to maintain static html sites and blogs, especially along with GitHub pages. Wanted to know if there are any Static site generators or CMS which helps in maintaining Jekyll sites with live preview, inline editing, layout management, file management etc.
There's an emerging market of "headless CMS" services that let you (or other writers) edit content through a web interface, and then access this content via an API. Most have webhooks that could be used to trigger regeneration of the static site when the content stored in the CMS is changed. Libraries for jekyll integrations already exist for these platforms.
List of headless CMSes:
Prismic (jekyll library)
Contentful (jekyll library)
Osmek
Storyblok (jekyll integration)
others
A few cool products fit the bill here:
CloudCannon
Siteleaf
Forestry.io
DatoCMS
Netlify CMS
jekyll-admin
Most of them sync directly with Git so devs can push directly on the repo, and non-techie users indirectly do the same by saving content (which trigger builds) in simpler UIs.
I personally like CloudCannon for its easy, more "visual" approach to editing stuff for non-technical folks (one of our dev wrote a full tuts on using CC + Jekyll for a multilingual site, should it be helpful).
Netlify CMS' open source approach is pretty neat too. The CMS is basically a react app you inject in any project.
Happy coding.
I have found these solutions:
http://www.siteleaf.com/
http://cloudcannon.com/
The second seems to be more promising to me. We basically want to develop the jekyll templates on our side, but want to have the possiblity for non-coders to edit the content online.
If you don't want to pay and you are okay with hosting a solution or do the editing offline, then you could try out this one: https://github.com/jekyll/jekyll-admin (Although I haven't tried it, but if you do, please share your experiences with me.)
I just finished with a simple editor for the same. You can find it on github here. It is still in initial release stage but it does come with live preview for editing posts on jekyll and managing them.
I'm searching for the same, as all Static site generators I found require Markdown knowledge which isn't suitable at all for my clients.
I found this great CMS (Kinda!) https://sitecake.com/
Still don't know how to manage collections with it, say listing of few products with lightbox details, but I believe it is possible.
What are the main functionality differences between Github Wiki and Readme,
Asking those that have used both readme and wikis extensively. So that we can better decide which to use for the purpose of outputing verbal information. This would be based on your answer. Thanks.
As examples, some have used wikis --
http://github.com/mbostock/d3/wiki
http://github.com/ParticleCore/Particle/wiki/Features
and some people have used readmes --
http://gist.github.com/atcuno/3425484ac5cce5298932
no better place to ask? -- meta.stackexchange.com/questions/157888/what-site-is-good-for-github-questions
Talking about a project repository :
Readme.md is the packaging
wiki pages is made for development/contributors documentation
gh-pages branch hosts user documentation
Both readme & wiki have no function, except for providing information. Github recommends you to create a README.md to display a short summary & usage of your repository, while the Wiki is totally optional.
I have to cross this bridge today, and in addition to this helpful thread I also found reading up the following helpful
https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
A key excerpt from there that I found useful and to the point
A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis.
Based on those and the other answers here, it makes sense to be high level in the readme along with all the getting started information (i.e. local setup), and leave the long form information such as application features, design principles, etc. in the wiki.
Another major difference of course is that the readme will get versioned whereas the wiki will not. Versioning of this doc is not a major concern for us, but it could be for you!