Set up some basic information on architecture with focus on extensability

Comments

ChristianAdamski created an issue. See original summary.

christianadamski’s picture

Status: Active » Needs work
WebGreenie’s picture

I would be happy to edit any English documentation someone can produce. I'm a better writer/editor than I am a coder, so I would be pushing for user friendly. I will edit and ask for clarification of anything that is hard to understand or isn't developed enough. Hopefully, that "someone" would fix it. I would do a last quick edit, and it would be done.

christianadamski’s picture

@WebGreenie

That offer is worth its weight in gold. I'll try to add to the linked page as fast as possible. There are also other documentation pages about the geolocation when you click that link and look at the table of contents right.

What you could do right now though, and this might also help yourself in your own project, is enable the geolocation_demo module and take a look around there. I noticed that this works pretty well.

WebGreenie’s picture

Yes, the Geolocation Field module is the best I've worked with so far with 8.x. I checked out the 8.x demo which helped me set up a work around to what I wanted. In the future, though, I will be looking for a way to pass the user's geolocation to Views...ah, a way that works. I have noticed that Views doesn't want to let me pull user info in at all, but I think this may be because I'm new to it and just haven't figured it out yet? Anyway, I will look at the other documentation...

christianadamski’s picture

Status: Needs work » Closed (outdated)

Didn't do it in 2 years, guess I won't. Code is in a mostly readable state though.