Thanks heaps! Curation of such features is a huge gift to the community.
It would be even better, for me at least, if the curation included clarity around two open questions:
Ease of applying a given template to an existing Django website. Oft times I find there are heaps of tips and good guides on starting from scratch, and little to no help on grafting onto an existing site.
The nuances of cost. There are four distinct cost models out there:
Free: no strings attached.
Freemium: A free tier and a higher paid tiers, pr,o enterprise whatever.
Purchase: One off price
Lease: A regular fee, monthly as a rule.
Here I concern myself with the distinction between 1 and 2, Free and Freemium. Primarily because Freemium implies by its nature that there are features we may well want in future that have a paywall. Which is only an issue with me (and my ilk) because the only Django sites I develop, maintain, and host are all community services, produce a revue of precisely $0 and hence have a capital budget of about $0 too. Small fees are not out of the question if they are Purchase fees, but Leases lose appeal fast. Either way the nuance of pricing here is a huge decision influence.
And I raise that primarily because when I click the links you provided they all go to appseed.us which sports a Pro Version link in the top menu and when I click them I'm rapidly lost in reading lots of stuff. To wit, even better curation covers this ground for me up front I guess.
Anyhow, not a complaint, far from it. Top work, and great list, thank you immensely. Just musings on how to make it even better if you care to.
Thanks! I'm on Discord. And I'm still a ways off skinning the site I'm developing (still working on backend data integrity) but in time, I hope to skin it elegantly and offer different themes (which is not too hard to with Django - for exmaple the vanilla skin (the crass simple developers default skin) a default skin and possibly different contrast skins (dark and red/green colorblind are common targets).
I wonder though if you can clarify "The PRO version is something that we provide extra based on the superior UI" ...
PRO version comes with a premium UI Kit (more pages & components).
Let me know the precise UI requirements for your project(s).
We have also a Jinja version for all themes that probably are easier to integrate.
🚀🚀
But what are pages? I''m curious. How could they be limited? Django provides routes (urls) mapped to views which load templates. To an end users each unique route resembles a page. But I'm not sure what you mean by "more pages".
More pre-built pages and components. I mean the UI kit provided with a PRO version comes with more pages & components.
There is no limitation in the Django codebase regarding this.
🚀🚀
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.
Thanks heaps! Curation of such features is a huge gift to the community.
It would be even better, for me at least, if the curation included clarity around two open questions:
Ease of applying a given template to an existing Django website. Oft times I find there are heaps of tips and good guides on starting from scratch, and little to no help on grafting onto an existing site.
The nuances of cost. There are four distinct cost models out there:
Here I concern myself with the distinction between 1 and 2, Free and Freemium. Primarily because Freemium implies by its nature that there are features we may well want in future that have a paywall. Which is only an issue with me (and my ilk) because the only Django sites I develop, maintain, and host are all community services, produce a revue of precisely $0 and hence have a capital budget of about $0 too. Small fees are not out of the question if they are Purchase fees, but Leases lose appeal fast. Either way the nuance of pricing here is a huge decision influence.
And I raise that primarily because when I click the links you provided they all go to appseed.us which sports a Pro Version link in the top menu and when I click them I'm rapidly lost in reading lots of stuff. To wit, even better curation covers this ground for me up front I guess.
Anyhow, not a complaint, far from it. Top work, and great list, thank you immensely. Just musings on how to make it even better if you care to.
Hello @thumbone !
Ty for your feedback. With your permission I will say a few words regarding your remarks.
All free versions provided by AppSeed are released under the MIT License. Basically anyone can use the code for unlimited hobby & commercial products.
Regarding Q1: we are working to provide a
theme-able
installation on legacy products. We have a pilot project over a Django Admin Theme: Django BlackOther aspects free products:
The PRO version is something that we provide extra based on the superior UI & priority on support.
In case you like what we provide, feel free to join Discord and chat with the support team.
We are there 24/7 to assist the community.
Thanks again for your time!
🚀🚀
Thanks! I'm on Discord. And I'm still a ways off skinning the site I'm developing (still working on backend data integrity) but in time, I hope to skin it elegantly and offer different themes (which is not too hard to with Django - for exmaple the vanilla skin (the crass simple developers default skin) a default skin and possibly different contrast skins (dark and red/green colorblind are common targets).
I wonder though if you can clarify "The PRO version is something that we provide extra based on the superior UI" ...
PRO version comes with a premium UI Kit (more pages & components).
Let me know the precise UI requirements for your project(s).
We have also a
Jinja
version for all themes that probably are easier to integrate.🚀🚀
But what are pages? I''m curious. How could they be limited? Django provides routes (urls) mapped to views which load templates. To an end users each unique route resembles a page. But I'm not sure what you mean by "more pages".
More
pre-built
pages and components. I mean the UI kit provided with aPRO
version comes with more pages & components.There is no limitation in the Django codebase regarding this.
🚀🚀