- Gold Partner | 1030
We love Nette Framework and we also love beer. It's a great start for something new ;-) Isn't it?
As You know, in Nette Framework documentation is section Quick Start. This section is helpfull when You are beginner, but what is the next step? There are more code examples https://github.com/planette at github and You can find some next steps in the nette forum as well. But sometimes is to hard to do this next steps. Stop using simple database access, use more components and do simpler Presenters, and more…
At Nette Camp 2019 we discussed how to change it. Our solusion is: to bring new step by step tutorial about how to build bigger project then blog only.
Base idea is our new Fictional browery – Skynette:
- we build simple presentation website
- we refactore some code in every new episode and bring new functionality
- we are opened for new ideas
I Want to help You…
We are looking for You, who want to help us, with corrections, ideas, testing and more…
write email to: email@example.com
subject: “Skynette – i want to help you”
text: write me which part you can help us
- Member | 30
- A lot of the new applications will have to run in the cloud somewhere so creating this project on docker and dealing with the ins and outs of running a Nette application in a container would be helpful, I think.
- Dealing with tasks that can run in the background (queues) – e.g. include a solution where sending an email won't happen during the clients request. (Maybe I'm getting to much into the specifics here, but sooner or later everyone bumps into this and it'd be cool to build applications with this in mind from the start).
- Also having migrations (and a way to execute them) is a must. However I think you might've covered this in the Doctrine bullet point.
- Member | 6
How deep are you going to dig into the modules? Do you plan to examine the DI's compiler extensions?
Recently I fell in love with those because they provide a simple and clean way to setup each part of system without bloating the config.neon (or some other included) file.
Last edited by Toanir (2019-09-02 10:58)
- Member | 6
Also it might be worth noting that testing is/should be a thing. Maybe dip in testing across the application layers – which kinds of tests make sense for which components…
I perceive development that it consists of persistent testing and when
developer uses classic combo dump-exit to achieve their goal, they essentially
write and execute a manual test.. and then delete it.
That, I consider a minor shame because the test has been written, the code passed it and only because the test was written in ineffective way / wrong place, it could not be automatized and had to be removed.
Imho guiding developers to an easy and effective way of testing would be hella rad.