This is your weekly friendly reminder that AlloyCI is always looking for contributors. If you are a beginner in Elixir, I'd be willing to mentor you on getting up to speed so you can start contributing.
I've been getting my feet wet with Elixir/Phoenix over the past month or two. I will check out your project and see if there are any issues I feel comfortable tackling.
Hi @wiz_ar
, we really don't use React. In fact we don't use any frontend framework at all. We only use Javascript when absolutely necessary, and when we do need it, we use StimulusJS.
If you want to learn Elixir, then sure I can give you hand. The best way to get started is to follow the tutorials for beginners online. Once you have the basics down, go through the source code of AlloyCI, and let me know in the issues if there is anything unclear, hard to follow, or that you don't understand. We can then go over it, and I can help you through the refactor process.
Looking through out of curiosity, since I started learning Elixir in February, but is the reason for not using a frontend framework because you're using phoenix_html? I tried porting an app to Phoenix, and it was possible, but not particularly enjoyable using a frontend framework if you're using HTML views with Phoenix.
Not really. The main reason for not using a frontend framework is that I really dislike Javascript. Unfortunately you cannot have a good looking application without it, so I use it sparingly.
And yes, HTML is rendered in the backend, so I use EEX views, and regular controllers. If AlloyCI were a Rails app, the same approach would have been taken.
In my opinion, the less Javascript code needed, the better. This is also the reason that we use Phoenix Channels to send pre-rendered HTML when needed (this is used when loading your repositories from GitHub, for example). This way I don't need an AJAX call. When the /projects/new page is called, the controller starts a background job to fetch your repositories from GitHub. Once the job has that data, it renders it as HTML and sends it to the "frontend" via a websocket. The JS code needed for this to work is minimal, so 👍
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is your weekly friendly reminder that AlloyCI is always looking for contributors. If you are a beginner in Elixir, I'd be willing to mentor you on getting up to speed so you can start contributing.
Don't be shy! Get in touch 🎉
I've been getting my feet wet with Elixir/Phoenix over the past month or two. I will check out your project and see if there are any issues I feel comfortable tackling.
I don't know much Elixir, but interested in what you guys are developing.
I am a reactjs dev I want to contribute too how can I please guide me through since I am new to open source
Hi @wiz_ar , we really don't use React. In fact we don't use any frontend framework at all. We only use Javascript when absolutely necessary, and when we do need it, we use StimulusJS.
If you want to learn Elixir, then sure I can give you hand. The best way to get started is to follow the tutorials for beginners online. Once you have the basics down, go through the source code of AlloyCI, and let me know in the issues if there is anything unclear, hard to follow, or that you don't understand. We can then go over it, and I can help you through the refactor process.
Looking through out of curiosity, since I started learning Elixir in February, but is the reason for not using a frontend framework because you're using
phoenix_html
? I tried porting an app to Phoenix, and it was possible, but not particularly enjoyable using a frontend framework if you're using HTML views with Phoenix.Not really. The main reason for not using a frontend framework is that I really dislike Javascript. Unfortunately you cannot have a good looking application without it, so I use it sparingly.
And yes, HTML is rendered in the backend, so I use EEX views, and regular controllers. If AlloyCI were a Rails app, the same approach would have been taken.
In my opinion, the less Javascript code needed, the better. This is also the reason that we use Phoenix Channels to send pre-rendered HTML when needed (this is used when loading your repositories from GitHub, for example). This way I don't need an AJAX call. When the
/projects/new
page is called, the controller starts a background job to fetch your repositories from GitHub. Once the job has that data, it renders it as HTML and sends it to the "frontend" via a websocket. The JS code needed for this to work is minimal, so 👍