Looking for contributions, developers and maintainers #1290
Comments
|
However, this doesn't mean that Mark Text is unmaintained but @Jocs and I are currently a little bit busy. Big changes and features cannot be expected during the next month and following month and also issues processing may take some time. |
1 thing that would also help easy customisation is a user css file. Every user can then customise MT to his own taste, within limits of course. Certain browsers have this (e.g. Firefox), and apps too (e.g. Typora). The latter also has a themes folder where the user can add downloaded themes or insert themes he/she made himself. VNote has an ini file that can be edited by the user. |
|
@DutchPete Maybe we might do better, we can download the theme and plugin you want directly in the app, similar to VSCode, uninstall it when you don't need it, you don't need to manually copy and paste it. |
|
Hi @fxha , I would like to contribute to your project. I'm a software developer and I have frontend and backend skills. Where should I start? :) |
|
@KancerEzeroglu Thank you very much for your willingness to contribute code to Mark Text. You can look at the issues labeled as bug, try to solve them, and submit the PR. If you encounter any problems in the process, you can discuss them in issue or PR. |
|
Hello Guys, I have good Frontend skills and would like to contribute to the project by solving issues. Thank you |
|
I offered to donate but have not heard back. I do not want to use PayPal or a credit card, but if you have a European bank account I'll be happy to make a transfer, provided you give the exact name of the account and the IBAN. |
|
Mark Text is very impressive. I want to contribute to this project. |
|
@piaoyidage You can start with these documents https://github.com/marktext/marktext/wiki |
|
@Jocs OK，thanks for your response. |
|
@Jocs Do you have further documentation on themes? I'd be interested in creating my own. I know user-defined themes are planned for v0.17.0. I don't mind compiling MarkText myself afterwards to include that theme in my build. I'd even share it if it turned out well. I'm just not sure if you're planning on changing how themes are made to allow for users to create them. Let me know if you have more information. I didn't see any on this in the Wiki. |
Sorry, we currently do not have any document about theme/custom theme, there even no clear plan how to implement the custom theme. I think you can refer the files in the folder with path |
|
Thank you, @Jocs I'll check out those files. Could you also let me know how to add another font as an option for the editor? (I'll keep in mind that these things may change in v.0.17.0, thank you for the warning.) Just an idea, but if the theme colors were consolidated, that would make it easier to write a GUI for. For example, you could ask the user what colors they want for the foreground, background, and highlight colors for the sidebar, then for the editor area. This is just six colors total. Based on the colors chosen, the code could evaluate whether the user picked a light or dark theme for the sidebar and the editor area. Then, other colors can be extrapolated from that. For example, the background color when hovering the mouse over a link in the sidebar is darker than the background in a light theme, but lighter if the theme is dark. The rest of the colors for the theme can be extrapolated like this, simplifying the process until either a more complex GUI is made to handle all the aspects of the theming, or code is written to take in themes in a form that users can easily write themselves (i.e. a simple .css file). Alternatively, you could create a base light, medium (gray), and dark theme (either for the whole app or for the sidebar and editor each individually), then allow the user to choose what color they want the highlights to be (e.g. Cadmium Light has green highlights). This would the users to feel like they can make choices on how it looks while keeping the coding and GUI changes to a minimum, compared to the previous idea. Those are just some thoughts. I hope you find them helpful. You've done a great job on the app! Thank you for sharing it with us. 😄 |
|
wow, it's the perfect markdown editor that I'm have being searched for long time. thanks for everybody |
|
A truly terrific piece of software. I can't wait to see what it looks like in 2 years and plan to sink time into contributing over the coming months. |
|
I am interested in contributing. Back-end is more my forte, but I have been looking for an opportunity to get involved with Electron app development. Is there a contributor agreement that needs to be signed before I can start taking on issues? I look forward to helping out with this awesome program! |
|
Thank you for your interest in Mark Text. Any contribution is very much appreciated!
@xinpingwang Unfortunately, Mark Text is currently not maintained and we currently haven't time for it. We welcome all contributors and try to answer issues and review PR's from time to time.
@ssimontis No, there's no CLA but you need to provide your code under the MIT license and have the right to do so. |
|
I'd love to help, i can do some light coding and other things necessary. I will go trough the issues and see where i can be useful. |
|
recently I see no active contributor, maybe some developer need help. (sorry I write c# and c++ and I never write javascript) |
|
Now I'm implementing i18n support. Everything is working in progress. I'd love to help. Here's my repo: https://github.com/anclark/marktext/tree/i18n-alpha-support |
|
I am also really impressed by this project. I'd like to contribute! Thank you for maintaining this project. |
|
So, is this still being maintained? Just wondering... |
|
Mark Text is simply awesome, I would like to be part of the community to contrinute to development and PR reviewing. |
@meanMonk PR is welcomed and also hope for helping review issues and improve documentation. |
|
I'm interested. Happy to help with bug fixes or develop new features as I have time. Let me know what I can do! |
|
I am primarily a server-side engineer. |
|
I'd like to get involved. I am a 2yr+ front-end engineer with Vue.js background. I think I can do tiny things for this project. |
|
I would like to contribute to development and PR reviewing, I'm working on i18n |
|
Is this project still alive? Surely there is a beautiful opportunity to fill the void left by Typora going commercial and not having a free version anymore. |
|
MarkText has no active maintainers and @Jocs (the owner) took a break. Unfortunately, I cannot coordinate with @Jocs about the future and his plans because I cannot reach out to him for the last months. I can only speculate cautiously about the future of MarkText, but I guess that no further releases are planned for the near future. At the same time, I very much hope this project will be continued. We had planned and started internal changes on the core engine to improve the overall performance and extensibility. For the time being, I'm thankful for all contributors and users which use, built and improved MarkText and wish you all the best. |
|
@fxha: thank you so much for responding. I had a feeling this is what was happening. |
|
@fxha: thank you for this update. I am sorry to hear that the future for MarkText is unclear and want to thank you for all the effort you put into building and maintaining this app! I wish you all the best👍 |
|
I want to do something. I try to make the resource package Chinese, fix a bug that picgo can't find under the Mac, and package and publish it on my own GitHub. The effect is OK, but it would be better to modify and implement it from the source code, but I don't have permission. |
|
Can you share your plans and completed tasks on refractoring the core engine, as I have already had some rough ideas about it, and want to get involved. P.S. Have you ever considered continuing this project on a forked repository if the project have been stalled for a long time? |
|
@fxha Any reason why not just fork and continue this project (can always be merged back to this if original dev returns later)? To wait a few months until the original dev replies is ok and pays respect, but it has been like a year really by now or even more? Many pull requests and issues have piled up as well. I personally (and many others) need the collapsible content and there's no reason not to have it, also the issue has been open for like 2 years now. Add deeper nesting than 1-level later if it's hard to implement, 1-level collapsible content would much better than nothing. |
|
@hCKbJf6MCesgWSPH Mark Text is dead: fact. Suggestion: try Obsidian, you won't regret it, you'll be blown away by the features and customizability, it is unrivaled, and it is free. |
|
Is there an active fork around somewhere? |
|
@DutchPete Just for clarification: According to its EULA, Obsidian is free for personal use. If you use it for commercial activity, you actually need to get a commercial license (except if you are a sole proprietorship). |
|
Ah... It's a shame to see this happen to MarkText. I have pretty much no skills in what's required to try make and maintain my own fork of the project, but I think I'll try see what I can learn about this cool app in my spare time, and try to fix any bugs I find/seen from other people. Like with everything else I'm trying out, this will be a great opportunity for me to learn a thing or two! Thank you to the original developers and maintainers for making this fantastic app, I've been using it for a very small amount of time and have completely fallen in love with it!
|
|
@NoDocCat I think it was fxha who would respond more often as Jocs has gone MIA from what I recall (don't quote me on that, all I know is that one of the developers stopped communicating some time ago now). You've already pinged them, so hopefully you'll get a response from one of them soon! On an unrelated note, I realised that I have too much going on to try help out significantly, which is a shame. :(
|
@axelrindle I'm intermittently maintaining a fork here, merging in PRs from the main repository that look good to me. If anyone would like to collaborate on this with me, please reach out! One of the most common things I see in PR comments are requests for builds for MacOS and Windows with bugs patched. I only have experience building for Linux, but if we could do multiplatform builds with GitHub Actions for each release, that would meet a real demand. |
|
@jacobwhall Sounds awesome, I'd like to help! electron-builder should be able to handle all the hard stuff. |
@axelrindle sweet, yeah it looks like electron-builder is already integrated into the build process, so targeting other platforms might be easier than I thought! I just opened jacobwhall#2 to track this issue. |
I've had a look around, Zettlr seems to have similar functionality and is open source :) |
|
Zettlr sadly has one issue that I consider to be a major design flaw. The HTML exports will look very different from the Markdown document, unless one always keeps the Markdown newline rules in mind. |
|
I wonder how to become a contributor. I am not superb, but it would be an interesting task. And I really like MarkText, so it would be great to improve it. |
It is a nice and clear editor. I hope it will continue developing. |
|
It seems that the focus has been placed on the Muya project. |
|
A link to Muya: https://github.com/marktext/muya |
|
I'm currently contributing code and gaining experience for another similar project. In contrast to Marktext, this one is solely browser-based without a dedicated client (akin to Muya). However, I still use MarkText in my daily routine simply because I only need a '.exe' for writing MD. I prefer not to go through the process of installing via a package manager, configuring JSON preferences, and writing HTML code to import JS files as one does for a project. I believe many others share this sentiment. The MarkText development team has shifted focus from MarkText to Muya, hinting at a potential future release of MarkText 2.0 through a client code overhaul. It appears to be a lengthy process, and before that happens, some bugs in MarkText might force me to abandon using the software. |
and others
We recently hit 11k stars after almost two years and more than 1000 commits. We are looking for further contributions to continuous improve Mark Text. Mark Text is a hobby project created by @Jocs and later I (@fxha) joined this awesome project. We both love this project but our time is also limited to maintain and develop Mark Text. There are a lot of thing to do that Mark Text becomes a stable but also a fast and more performant editor.
If you are interested let us know and please comment on this issue. We are happy to invite active contributions that are working on this project, whether developing new features or help with issues. You should have JS knowledge and need an enabled two-factor authentication account. To summarize, we are looking for:
There are other things that you can do to improve Mark Text:
Upcoming and necessary changes:
In the next time we need to make some necessary changes on Mark Text's core and refactor even more files.
You can find all planned "core" features here and a lot more via the issue tracker.
Many thanks (in advance) to everyone who giving their time to contribute to Mark Text and help this project!
Mark Text is still in development, many thing will change and feature will be added but our philosophy is to keep things clean, simple and minimal. For example our side bar and tabs: these two panels provide a lot of functionality but don't disturb the user if it's not needed. We'll add more and more feature, maybe extended by plugins, that can be activated via settings to improve Mark Text. So we allow everyone to customize Mark Text for it needs and provide a minimal default interface.
The text was updated successfully, but these errors were encountered: