Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
It seems that Indexhibit (www.indexhibit.org) is a sort of standard when it comes to building portfolio websites for artists. I just received a mail from an artist asking me whether I use Indexhibit. Beside the issues of the customer poking their nose into technical stuff, I need to know what's so special about Indexhibit?
I took a look at it and saw nothing more then a somewhat original CMS. I have my own system/libraries that I use to build simple websites and prefer sticking to these, but would like to know first... why does Indexhibit have this place among artists... and why do they say "an Indexhibit site" and not "a website built on Indexhibit"... what's the difference between an Indexhibit website and a plain website? Is there any advantage when using Indexhibit?
That's it, you got it, it's just a blank slate that makes it easy to pump out a small portfolio in a short amount of time. It's the helvetica of portfolio web design. Nothing fancy, but it's classic, the art can breath.
I come from a ASP.NET MVC and Django Background, and I've actually been having a bit of fun about working with Indexhibit. I got over my fear of PHP and there is some thing refreshing about just firing a query off, and building html straight out of it. Would never use it for a really custom job, but for things that fit the model, it gets quite out of your way for getting things done.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What are some ways including machine learning that I can use in my projects to generate things related to another. Like related apps, related websites, related products, etc.
I've been brainstorming these are strategies...
one way i can think of is show items from same category. But that would be too broad.
2nd way improves upon previous step, it's to keep track of what people click next and promote that item. Meanwhile keep bottom list randomized to let other relevant items show up and get clicked.
3rd way is to use machine learning and provide training data somehow and use that.
I want something simple but smart, as it gets better with time.
Collaborative filtering is designed for solving exactly this problem. The problem with this approach is that produces good results having a lot of data only. I mean... A LOT. And it's not a really simple thing to use. However, any machine learning technique is not simple. There are some node.js packages for CF available, but I have no idea how good are they.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
Is there any rationale why HapiJS endorses using 4-space indentations?
Source: http://hapijs.com/styleguide
Short answer: No better reason than anyone else - styleguides are typically only rules for project maintainers. They had to adopt some convention and that was the choice. As a user, you don't really need to care.
Long answer: Hapi is a great framework, built by the folks at Walmart. and specifically a person named Eran Hammer who was unhappy about some architectural choices made by Express, another server framework for Node. It is somewhat opinionated in general, it was effectively created in an environment of opinion, not to mention a large company (which means it desperately needed a convention). That said, you can safely use the Hapi API with any indentation you want, including tabs, though. Likewise, the Hapi internals could have been written the same way. Their specific choice likely comes down to established tools or conventions already in use at the company. Many different projects make different choices for a variety of reasons. In my experience, many large JavaScript applications go with 2 spaces and the Node.js core itself is written with 2. But there's nothing wrong with those that do otherwise.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Can you give several indications (pro and cons) concerning the fact to put the menus of a web application inside the database?
Mainly it depends upon your requirement of your application. Its not always a good approach to bring a drill machine to make hole in sand. Every approach has some limitations and need more efforts if you do apply some alternate approaches.
In cons you can consider
Performance ( to prepare dynamic menu every time you load the master page also the static text less time to process in compare to dynamic)
Configuration will be always an issue while adding or modifying the menu
(Always need a database guy at the time of any change)
Pros
Highly configurable and completely dynamic
Can add/remove the attribute and change the text without affecting anything in code.
We have some solutions also to overcome from the cons
In case of performance we can use caching but everytime the menu change you need to recycle the application pool.
For configuration you can provide a page to control the menu content. (No Sql guy needed)
So as I said earlier you can go either way as your application adopt easily and in much better way.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
My aim is to build an aggregrator of news feeds and blog feeds so as to make
searching/tracking of entitites in it easy. I have been looking at many solutions out there like Terrier, Lucene, SWISH-E, etc.
Basically, I could find only 2 sources of comparison studies done on these engines and one of them is kinda outdated. Basically I want a search engine which would be used in a case in which the data size is not too large, but the indexing will be frequent, every 30 minutes or so. I feel Terrier is not a good tool to be used in this case. It works better when the data size is large and updation frequency is low. Can somebody who has worked in the Information Retrieval field offer some advice ?
Lucene is well known and supported, so personally, that would be my first choice.
If you find a ready-to-use search engine, check out fastcatsearch.
It has been developed for commercial search, and applied to a lot of various sites.
Faster than lucene, and has web-based web manager to use easily.
Hosted in github, and check it out. https://github.com/fastcatgroup/fastcatsearch
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I am about to embark on a jquery journey I have not ever done. I will be developing a site that has one objective : to display over 300 uncategorized images (artwork). I'm just trying to think about the best way to go about displaying all these images in an easy to navigate, elegant way. I could use thumbnails and lightbox, but that's boring. I want to get inventive! Any cool ideas?
What's the objective of the people coming to view the images? Is it just browsing, or will they be looking for particular images? Are the images grouped into themes or artist or something? You have to build a navigation system that makes it easy for your users to achieve their goal!
Perhaps, if its more browsing some creative theme of images I wonder if you could come up with a scheme that lets users find their way between images naturally. Perhaps have several paths through the images, that when you view one you have a couple of options for where to 'go' next. Almost mimic the kind of browsing you might experience in an art gallery?
I wouldn't say that 300 images is a "ton" by any stretch.
Go visit photo sites like Flickr, SmugMug, and Picasa. Find the websites for wedding and journalist photographers. See what they're doing. If you can't figure out how to navigate their site in 10 seconds, stay away from similar site designs.