How hard would it be to create a website that lets people create their own pages on them?
Like a company creating a custom page on my site only with a drag and drop system provided by my website (of course they would need to create an account).
What frameworks would I need to use?
I tried searching the web but didn't find anything. I found craft.js but I don't know if I can implement it like that.
Thank you all in advance.
Such a project would be very complex and cannot simply be "coded down". Here are the main reasons:
You need an infrastructure where and how your users can save their websites. Does every user just have one page or several (limited or unlimited)?
Drag and Drop requires some JavaScript interactions and a set of predefined web components like buttons, input fields, labels or images. You would have to define abstract components that could be individually filled with user content.
If you ask your users to register before creating websites, you must respect the "General Data Protection Regulation" (applies for the European Union).
If you want to make money with your project you'll have to consider several legal aspects depending on the country where you live.
In short, there are many reasons why homepage kits are not an easy thing to program.
Related
I need to modify a web application's interface based on user behavior. For example, new users will see the interface in a simplified way and expert users will see all the features of the application. How can I distinguish between the two types of users? The web application is built on Flask. How should I approach and is there any constructive tutorial that I can follow?
You could use Cookies/Local Storage to count and save how many times they have visited, or if they have visited before. This can be done through Flask, see here for how it's done: link.
Alternatively, give the user the option to toggle between the views, and use a cookie to save their option.
is there anyway to create two homepages for moodle or someway of doing something similar to having a two homepage effect.
At my work (educational) we offer qualifications and we also offer online (e-learning) courses.
Ideally I want to create one area just for the qualifications where users will get a login and ONLY see the qualifications side of things.
Then I want to make another area JUST for the e-learning side of things. Both sets of users would not be able to see the other areas (ie. e-learning cannot see qualifications etc)
Does anybody know if this is possible?
Hopefully this makes sense.
Kind regards,
What you can do is to have a single front page and then restrict access to individual courses based on their enrollment status.
You can add an additional plugin to allow for self-enrollment with administrative approval.
Additionally, you can do things like hide specific courses or categories of courses and then configure permissions to view these hidden courses or hidden categories.
If you want to create completely unique landing pages, you may need to manage more than one instance of Moodle.
I need to find a CMS like, set of modules/module which does the following:
give users different logins and access to add their own products.
other users cannot see products which are not added by themselves.
so user A can enter his login and add a set of 5 products. user B can enter his login and add 2 products. user A can never see the 2 products added by B and vice versa.
Any suggestion in already existing modules?
both free and with a price
You can do this with Forms and Lists. Setup the fields you want to collect and then you can use it to only render the logged in users results to them. Also could use XMLdb module or even reports module to query the data out of the database after saved with forms and lists
So no one can see each others products? They are just going to buy from themselves? ;)
Tricky part about users adding their own products is payment. That's why this is not a common store feature. If you allow people to add products, you usually need to allow them to setup their own payment provider to collect the money. And in some cases you (the site owner) would want to take a percentage. Which makes it even more complicated.
I'm not aware of any GOOD DotNetNuke e-commerce module that can do this.
It's very possible Catalook has some feature to do this. They have somehow tried to add every feature ever imagined into their product. But, overall I find it terrible to work with. That is your best bet for trying to get something like that out of the box.
Or try and get one of the open source solutions like NBstore and modify it.
I'm developing a site in Symfony, and I'm not sure what the best way is to handle this scenario.
I'm creating a party bookings system. Anyone can go to my frontend app and submit a new booking. Once they're finished, they'll just get a confirmation screen, they can't edit it. Easy.
Only certain users will be able to get to the admin app (it might be secured simply by being on an intranet, but that's not important, just assume it will be only accessible by admin users). They'll be able to view the list of submitted bookings. Easy.
My problem is around code re-use when allowing admin users to edit existing bookings. When you do generate-module in Symfony, the generated module (which as a newbie I'm assuming is a good example of structuring things) creates the form as a partial. I've had to customize this form a lot for my usage (lots of Javascript, etc), so of course I want to re-use this code, to be able to load an existing booking into this form. But there doesn't seem to be a way to share this partial between the apps (I've seen people mention making a plugin...but this seems complicated for this use).
I considered using an IFrame to load the form from the frontend and just passing an "id" parameter to load it in edit mode, but this would mean that the edit mode is not secure - anyone could go to the form on the frontend and pass this parameter to edit a booking.
I also considered putting all of the form display code (HTML, Javascript, etc) in a method on the form object, but this doesn't seem very MVC - all of the display code is then in the form. But this is only because I'm thinking of the form in the same way as a model - is that right?
I feel like this should be a common situation. You can share models and forms between apps, why can't you share this common form display code too?
Thanks!
You should reconsider having 2 applications in the first place. Not only you run into the code reuse problem, but also i18n, testings and other issues. I find it much easier to have 1 application with different bunch of modules for frontend and backend users. You can configure security per module. You can have one sign in form for all users and redirect them to appropriate module based on their credentials.
You can reuse partials between modules inside the same application, but you seem to be talking about two different applications (frontend and backend) so as far as i know the only way is to copy & paste the partial from one application to the other...
I'm creating a site for a local retail shop using Drupal. Everything's been going very smoothly up until this current bit.
It's a comic shop, and I want to make a place where people can manage their own subscriptions. Since the number of different titles a customer subscribes to can vary pretty widely, I want a way to make a completely dynamic form, with people able to add as many new lines as they need and I'm really struggling with Drupal's documentation.
Essentially, I'd like the final version of the page to look something like this: http://www.monksp.org/foo.html
Anyone have any experience building a drupal form like this?
Could you not achieve something similar using Taxonomy and free tagging? Take a look at http://drupal.org/handbook/modules/taxonomy
So in theory you would have a content type called "Subscription", each user would only be able to create one node of this type, it would have the taxonomy applied to it. The user can then edit the node and add more subscriptions. The great thing about this is that you can also use auto-complete. So say a user is already subscribed to X-Men another user can edit their subscription and start typing "X" this would then auto populate with suggested terms already in the taxonomy. e.g:
X-men: Origins
X-men: Apocalypse Saga
X-men: Noir
I think this is the functionality you've described.