Giter Club home page Giter Club logo

awesome-scientific-writing's People

Contributors

ashwinvis avatar finnoh avatar johannesbuchner avatar maehr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

awesome-scientific-writing's Issues

Maybe consider obsidian

This is a great list thank you for your work.

Obsidian is a fairly popular note taking app (107 000 members on reddit https://www.reddit.com/r/ObsidianMD/) and has many community plugins (that should maybe be checked as they are not from the obsidian developers) including plugins for latex. I once read on reddit a comment where someone wrote that they write their articles with obsidian, if I recall correctly, by converting the markdown to latex using a pandoc plugin if I remember correctly.

Personally, I found the experience of writing latex on obsidian a bit limiting (no good support for labels, limited amount of latex package support if I recall) but the automatic latex rendering while writing was nice (at the moment I prefer neovim with snippets and code I wrote for viewing rendered formulas in a pdf popup but that took a very long time to setup so I cannot recommend it)

Update contributing guidelines

And pull request template

Criteria:

  • Number of entries per PR
  • What kind of entries are welcome in this list.
  • Only open-source stuff / free as in beer stuff too?

Merge with awesome-academic-writing

We now need to merge the contents of https://github.com/maehr/awesome-academic-writing here

What headings should we can structure so that we get best of both worlds?

  • Converters / Word Processors / ... ?
  • Extras / ...? should be split up or discarded
  • How To / Demos / Tips and Tricks / Templates and Guides / ..?
  • Spell checking / Linters ?

Unique headings which should be kept!

  • Bibliography
  • Illustrations

Knowledge base management

Editors can also serve as a collection of notes. Various software similar to Zettlr are mentioned in this HN thread. I personally use Vimwiki plugin for Vim.

Add to main awesome list

i.e. https://github.com/sindresorhus/awesome
Here is a copypasta of the and old version of the checklist, but I think most of the tasks are still valid.

I have read and understood the contribution guidelines and the instructions for creating a list.

  • This pull request has a descriptive title.
  • For example, Add Name of List, not Update readme.md or Add awesome list.
  • The entry in the Awesome list should:
    • Include a short description about the list project/theme. It should not describe the list itself.
    • Example: - Fish - User-friendly shell.
    • Be added at the bottom of the appropriate category.
  • The list I'm submitting complies with these requirements:
    • Has been around for at least 30 days.
    • That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
    • It's the result of hard work and the best I could possibly produce.
    • Non-generated Markdown file in a GitHub repo.
    • The repo should have the following GitHub topics set: awesome-list, awesome, list. I encourage you to add more relevant topics.
    • Not a duplicate.
    • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • Only has awesome items. Awesome lists are curations of the best, not everything.
    • Includes a project logo/illustration whenever possible.
      • Placed at the top-right of the readme. (Example)
      • The image should link to the project website or any relevant website.
      • The image should be high-DPI. Set it to maximum half the width of the original image.
    • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
    • Has the Awesome badge on the right side of the list heading,
    • Has a Table of Contents section.
      • Should be named Contents, not Table of Contents.
      • Should be the first section in the list.
    • Has an appropriate license.
      • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
      • If you use a license badge, it should be SVG, not PNG.
    • Has contribution guidelines.
      • The file should be named contributing.md. Casing is up to you.
    • Has consistent formatting and proper spelling/grammar.
      • Each link description starts with an uppercase character and ends with a period.
      • Example: - AVA - JavaScript test runner.
      • Drop all the A / An prefixes in the descriptions.
      • Consistent naming. For example, Node.js, not NodeJS or node.js.
    • Doesn't include a Travis badge. You can still use Travis for list linting, but the badge has no value in the readme.
  • Go to the top and read it again.

Logo

Let us collect some options go here, and anyone can vote on the comments below.

Add a link to the pandoc-convert-plus package ?

Hello there !

I just wanted to propose to add a link to the pandoc-convert-plus package for Atom I've just created, as a fork of pandoc-convert.

It makes converting markdown files (and others) to different format very easy, and it's especially useful because it allows the user to use the citeproc plugin of pandoc with a .bib file for every conversion. This lessens the need to add YAML headers in every markdown files, and makes using pandoc easier and quicker in my experience.

It's just a proposal though, and I won't be vexed if you don't find it as useful as I do : ).

Thank you for your awesome page that inspired me a lot to equip myself with Atom, and have a nice day !

Add Zettlr

Hello,

I would just like to suggest to add Zettlr, a great opensource alternative to Evernote, which supports bibliography, footnotes and import/export to and from LaTeX (and other formats like Word DOC, etc).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.